how to upgrade the kernel in LTIB

[aurelihein]

I am currently working on mpc8349 board.
LTIB is given with a 2.6.13.4 kernel but it's obsolete, i would like to upgrade it with a new kernel like 2.6.21.
How can i do that?
I tried to choose a new kernel in my local linux directory, the new kernel has compiled but when I uploaded it on the board and try uname -r i got the kernel 2.6.13.4 . . . .
Please HELP
Thanks,

[steverino2]

We are working with the MPC8348E-MITX board.
The in-box LTIB is linux kernel 2.6.13.4. 
we are attempting to upgrade to 2.6.22

Whats the point? Having encountered a PCI enumeration problem with a PLX 6152 bridge,
we are attempting to upgrade the kernel.

based on this thread in freescale forums, it looks like 2.6.22 upgrade has been done
before.  not too extensively documented, but a good start. so I will add a bit of color here:

we completed changes to the ltib files
config/platform/mpc8349itx/main.lkc, created linux-2.6.22-mpc8349itx.config,
along with dist/lfs-5.1/kernel/kernel-2.6.22-mpc8349itx.spec.in

so far so good.  after ltib --configure starts the 2.6.22 build,
it downloads the kernel from bitshrine
but in www.bitshrine.org/gpp, no suitable
patch file exists for kernel-2.6.22-mpc8349itx
in fact the patches die off after 2.6.13 and 2.6.16

well, after booting linux 2.6.22 and loading the ramdisk, the system hangs :-o

now that we've come this far, we'd like to confirm that this upgrade is
feasible, and perhaps some advice on how to locate and incorporate patch file(s).

we are trying to figure out...

1.  will this work ?

2. is there any way to know what patches exist in PPP?

3. assuming 2.6.22 can be built for the mpc8349e, what became of the earlier patches from 2.6.1x?  Were they propagated upstream to kernel.org?

thanks,
/steverino2

[aurelihein]

I downloaded the new Uboot 1.2.0 from http://opensource.freescale.com .I am now able to boot my kernel 2.6.13.4 from it, what i changed is the main.lkc in [config/platform/MPC8349ITX]
The changement I did are as fallow :

config PLATFORM
    string
    default mpc8349emitx
config LINTARCH
    string
    default powerpc

Everything is ok till the dtb compilation, apparently on new kernels a flat tree is given to uboot but I'm not able to generate it the error is this one :

DTC: dts->dtb  on file "mpc8349emitx.dts"
Warning: physical boot CPU not set.  Use -b option to set
ERROR: Missing /chosen node
Input tree has errors

and if i try to set a CPU to 0 or to 1  i still have the missing chosen node error

thank you for your help,

[aurelihein]

I found out that the dtc was obsolete so i upgraded my dtc, now it's working . . .
I have a new kernel 2.6.21 on my mpc8349emitx board...

[fmf]

I have the same problem with cdt. Could you give me a good version?

Thanks

[aurelihein]

you probably meant dtc which mean by the way : device tree compiler
I am not working anymore on this board, but as far as i remenber i downloaded dtc sources and compile it, and it worked afterward.
you should look at this website : http://www.jdl.com/software/
I can't really help you more
let me know how things are going
good luck

[fmf]

I use the latest version of this software:

dtc -I dts -O dtb -f mpc8349emitx.dts -o mpc834emitx.dtb
DTC: dts->dtb  on file "mpc8349emitx.dts"
Warning: physical boot CPU not set.  Use -b option to set

[aurelihein]

I did it in may, maybe you can try with the version of may
Else you should try to see inside the C code of the dtc sources
I am sorry that i can't really help you more, it's another proof that we should publish every single things that we do to help people being faster afterwards...
let us know though how things are going
good luck !

[fmf]

Searching in the code you can see that physical boot cpu is only a cdt option. You can pass -b 0 to set 0 address or -f to force compiling. Now is working. 

[aurelihein]

such a good news !
you were upgrading to 2.6.22 i guess ?
good luck . . .

[fmf]

I am using 2.6.22.6 kernel verision

[olivier_o]

Hi,

I achieved also to run the board with the kernel 2.6.26.
Every thing seems working well, except the SATA.
I've got the following log at boot-up, then the kernel seems to be freezed here :

Code:

Driver 'sd' needs updating - please use bus_type methodssata_sil 0000:00:10.0: enabling device (0000 -> 0003)sata_sil 0000:00:10.0: cache line size not set.  Driver may not functionsata_sil 0000:00:10.0: Applying R_ERR on DMA activate FIS errata fixscsi0 : sata_silscsi1 : sata_silscsi2 : sata_silscsi3 : sata_silata1: SATA max UDMA/100 mmio m1024@0x90000000 tf 0x90000080 irq 22ata2: SATA max UDMA/100 mmio m1024@0x90000000 tf 0x900000c0 irq 22ata3: SATA max UDMA/100 mmio m1024@0x90000000 tf 0x90000280 irq 22ata4: SATA max UDMA/100 mmio m1024@0x90000000 tf 0x900002c0 irq 22ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)ata1.00: ATA-7: HDT722516DLA380, V43OA96A, max UDMA/133ata1.00: 321672960 sectors, multi 0: LBA48 NCQ (depth 0/32)ata1.00: configured for UDMA/100ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)ata2.00: ATA-7: HDT722516DLA380, V43OA96A, max UDMA/133ata2.00: 321672960 sectors, multi 0: LBA48 NCQ (depth 0/32)ata2.00: configured for UDMA/100ata3: SATA link down (SStatus 0 SControl 310)ata4: SATA link down (SStatus 0 SControl 310)scsi 0:0:0:0: Direct-Access     ATA      HDT722516DLA380  V43O PQ: 0 ANSI: 5sd 0:0:0:0: [sda] 321672960 512-byte hardware sectors (164697 MB)sd 0:0:0:0: [sda] Write Protect is offsd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUAsd 0:0:0:0: [sda] 321672960 512-byte hardware sectors (164697 MB)sd 0:0:0:0: [sda] Write Protect is offsd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda:<3>ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error)ata1.00: status: { DRDY }ata1.00: qc timeout (cmd 0xec)ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)ata1.00: revalidation failed (errno=-5)ata1: failed to recover some devices, retrying in 5 secsata1: hard resetting linkata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)ata1.00: configured for UDMA/100ata1: EH completeata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error)ata1.00: status: { DRDY }

 

any ideas ?

regards
Olivier

[Alban]

Salut Aurelihein,

Thanks for keeping the board updated with you progress !
That could be very useful to someone else.

Cheers,
Alban.