Booting Linux on one core of P1022

Booting Linux on one core of P1022

[Arshad, Farrukh]

[-- Attachment #1: Type: text/plain, Size: 3528 bytes --]

Greetings All,

I am working on P1022RDK (P1022 Processor). I am trying to bring up LTIB Linux only on Core1 of the processor. I have configured the "cpus" node in the device tree file as following way

Cpus {
     #address-cells = <1>;
     #size-cells = <0>;
     PowerPC,P1022@1 {
           Device_type = "cpu";
          Ret = <0x1>;
           Next-level-cache = <&L2>;
     };
};

Mpic: pic@40000 {
     Interrupt-controller;
     #address-cells = <0>;
     #interrupt-cells = <2>;
     Reg = <0x40000 0x40000>;
     Compatible = "chrp,open-pic";
     Device_type = "open-pic";
     Pic-no-reset;
     Protected-sources = <
           16         // l2-cache-controller@20000
     >;
};

I am loading the kernel from Uboot as following way

Setenv bootm_low 0x10000000
Setenv bootm_size 0x10000000
Setenv bootm boot=/dev/mmcblk0p3 ro debug rootdelay=5
Interrupts off
Bootm start $load1addr - $fdt1addr
Bootm loados
Bootm fdt
Fdt boardsetup
Fdt chosen
Bootm prep
Bootm go

Using above configuration when the kernel boots it fails giving following message

[    2.057448] WM8960 I2C Codec 1-001a: No platform data supplied
[    3.062314] WM8960 I2C Codec 1-001a: Failed to issue reset
[    3.067816] WM8960 I2C Codec: probe of 1-001a failed with error -110
[    3.074528] No device for DAI WM8990 ADC/DAC Primary
[    3.079834] ALSA device list:
[    3.082821]   No soundcards found.
[    3.087561] IPv4 over IPv4 tunneling driver
[    3.092757] GRE over IPv4 tunneling driver
[    3.097871] TCP cubic registered
[    3.101124] Initializing XFRM netlink socket
[    3.105405] NET: Registered protocol family 17
[    3.109869] NET: Registered protocol family 15
[    3.114734] SCTP: Hash tables configured (established 8192 bind 8192)
[    3.122984] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    3.129329] Waiting 5sec before mounting root device...
[    8.138471] Root-NFS: No NFS server available, giving up.
[    8.143896] VFS: Unable to mount root fs via NFS, trying floppy.
[    8.150150] VFS: Cannot open root device "mmcblk0p3" or unknown-block(2,0)
[    8.157038] Please append a correct "root=" boot option; here are the available partitions:
[    8.165410] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
[    8.173681] Rebooting in 180 seconds..
[   11.994301] mmc0: Timeout waiting for hardware interrupt.
[   11.999870] sdhci: ============== REGISTER DUMP ==============
[   12.005697] sdhci: Sys addr: 0x00000000 | Version:  0x00001201
[   12.011523] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000001
[   12.017349] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[   12.023175] sdhci: Present:  0xff8d0008 | Host ctl: 0x00000020
[   12.029001] sdhci: Power:    0x00000003 | Blk gap:  0x00000000
[   12.034828] sdhci: Wake-up:  0x00000000 | Clock:    0x000010ff
[   12.040654] sdhci: Timeout:  0x00000000 | Int stat: 0x00000001
[   12.046479] sdhci: Int enab: 0x007f0003 | Sig enab: 0x007f0003
[   12.052305] sdhci: AC12 err: 0x00000000 | Slot int: 0x00001201
[   12.058130] sdhci: Caps:     0x05f30000 | Max curr: 0x00000000
[   12.063955] sdhci: ===========================================

When I boot the same kernel using 2 CPUs in the device tree file, it boots successfully. Any thoughts on what I am missing.


Best Regards

Farrukh Arshad
Sr. Software Development Engineer
Mentor Graphics Pakistan
Ph:   +92 - 423 - 609 - 92 - 09
Cell: +92 - 303 - 444 - 77 - 05


[-- Attachment #2: Type: text/html, Size: 13920 bytes --]

Re: Booting Linux on one core of P1022

[Scott Wood]

On 11/29/2011 02:36 AM, Arshad, Farrukh wrote:
> I am loading the kernel from Uboot as following way
> 
>  
> 
> Setenv bootm_low 0x10000000
> 
> Setenv bootm_size 0x10000000
> 
> Setenv bootm boot=/dev/mmcblk0p3 ro debug rootdelay=5
> 
> Interrupts off
> 
> Bootm start $load1addr - $fdt1addr
> 
> Bootm loados
> 
> Bootm fdt
> 
> Fdt boardsetup
> 
> Fdt chosen
> 
> Bootm prep
> 
> Bootm go

You set up the device tree to reflect a core 1 boot, but I don't see
where you told U-Boot to use core 1.  You need to use a command like
"cpu 1 release 0x10000000 - $fdt1addr 0x45504150" instead of "bootm go".

Also make sure that you pass -b1 to dtc.

BTW, your e-mail client appears to be inappropriately adding
capitalization to pasted text.

-Scott