Not able to boot cuImage for the target board with MPC8270 processor

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

Re: Not able to boot cuImage for the target board with MPC8270 processor

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

Re: Not able to boot cuImage for the target board with MPC8270 processor

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

Re: Not able to boot cuImage for the target board with MPC8270 processor

> 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

Re: Not able to boot cuImage for the target board with MPC8270 processor

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

Kernel panic when loading the IDE controller driver

Hi All, I have been working on porting Linux-4.15.13 kernel on our existing MPC8270 processor board. For this exercise, I have used pq2fads as a reference board, its associated device tree and used cuImage for building the kernel. I am facing an issue with the generic IDE flash controller driver i

Re: Kernel panic when loading the IDE controller driver

> What it the last linux version known to work properly? We have used it successfully in the Linux-2.6.17.6 version. Thanks, Sachin. -- Sent from: http://linuxppc.10917.n7.nabble.com/linuxppc-dev-f3.html

Re: Kernel panic when loading the IDE controller driver

> Why using 4.15.13 which is obsolete instead of using one of the Long > Term Support versions which are still maintained, like 4.14 or 4.19 ? > (see the complete list at https://www.kernel.org/category/releases.html) Well, when I started this task 4.15.13 was probably the latest stable release

Re: Kernel panic when loading the IDE controller driver

> Maybe look around > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/? > id=9a0e77f28b50128df0c9e26ae489e44e29a7270a >Also look at ide_platform.c. I imagine there must be some way to set it >up in your device tree. I have gone through this before and also tried the pata

Re: Kernel panic when loading the IDE controller driver

Hi, > Hopefully there are examples of passing these values through ACPI. Are you suggesting here to look at the ide-acpi.c sourc file available as part of the driver code? In my original post I mentioned that I have modified the ide-generic.c source file to use the IO port addresses and IRQ numb

Re: Kernel panic when loading the IDE controller driver

Hi All, I finally got the FLASH controller driver working and it is now successfully reporting the presence of 2GB Flash in the board. I used the new "libata" driver code present in the new kernel source under drivers/ata/. Also did the required additions in the device tree to provide the IO port