Hi All,
I debugged the bootwrapper code by printing messages in RAM using memcpy.
The bootwrapper code appears to be executing correctly. I ensured that the
"serial_console_init" function has executed successfully. But I am still not
able to get any of the "printf" output in the wrapper code on th
> Are you sure the device tree you're using is correct for your board,
including
> all addresses being where your U-Boot configured them?
I actually created one for the target board I am using but had similar
problem. So I decided to take the pq2fads.dts tree as a reference since it
is based o
On Wed, 2018-08-29 at 04:14 -0700, sgosavi1 wrote:
> Press to STOP AUTOBOOT!:autoboot in 2 seconds
> ## Booting image at ffc0 ...
>Image Name: Linux-4.15.13
>Created: 2018-08-29 10:45:39 UTC
>Image Type: PowerPC Linux Kernel Image (gzip compressed)
>Data Size:1166
Thanks for your reply. Yes, both the options are enabled in the kernel
configuration for my board as seen below.
CONFIG_PPC_EARLY_DEBUG=y
CONFIG_PPC_EARLY_DEBUG_CPM=y
# CONFIG_PPC_EARLY_DEBUG_MEMCONS is not set
CONFIG_PPC_EARLY_DEBUG_CPM_ADDR=0x11a80
--
Sent from: http://linuxppc.10917.n7.nabbl
Yes, both these config options are enabled as you can see from the below
details from my .config file.
CONFIG_PPC_EARLY_DEBUG=y
CONFIG_PPC_EARLY_DEBUG_CPM=y
# CONFIG_PPC_EARLY_DEBUG_MEMCONS is not set
CONFIG_PPC_EARLY_DEBUG_CPM_ADDR=0x11a80
--
Sent from: http://linuxppc.10917.n7.nabble.com/linu
Le 29/08/2018 à 13:14, sgosavi1 a écrit :
Hi Everyone,
Recently I took up the activity of switching from Linux kernel version
2.16.17.6 to version 4.15.13 for our target board that supports MPC8270
PowerPC processor. As I understand the new kernel version mandates the use
of a device tree in
Hi Everyone,
Recently I took up the activity of switching from Linux kernel version
2.16.17.6 to version 4.15.13 for our target board that supports MPC8270
PowerPC processor. As I understand the new kernel version mandates the use
of a device tree in the kernel source to describe the target board
