Re: [U-Boot] Regarding MPC8640D second core initialization
Dear "Thirumalai", In message <37ef3a462afe4b5090e87f6b7f3f3...@itd210> you wrote: > Hi denx, > I am using 2009-06 u-boot for MPC8640D based board. i just want to > know whether the second core of MPC8640D is kicked off automatically or will > it required by the user to kick. Also if am enabling the CONFIG_MP macro and > CONFIG_NUM_CPUS as 2, then the reset command of the target is not > working(means board is getting hanged). I have mentioned the value of > CONFIG_SYS_SCRATCH_VA as 0xf500. > > Kindly suggest me what might be the error. Which "MPC8640D based board" is this exactly? At the moment we have 3 MPC86xx boards in mainline, and the MAINTAINERS file will tell you who is responsible for these. If you have a custom board with an out-of-tree port you will have to ask those who provided the port to you. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de Alles Gescheite ist schon gedacht worden, man muß nur versuchen, es noch einmal zu denken. -- Goethe, Maximen und Reflexionen ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Regarding MPC8640D second core initialization
Thank you denx. Hi Jon, I am using 2009-06 u-boot for MPC8640D based custom board. i just want to know whether the second core of MPC8640D is kicked off automatically or will it required by the user to kick using cpu command like mpc85xx/mp.c. Also if am enabling the CONFIG_MP macro and CONFIG_NUM_CPUS as 2, then the reset command of the target is not working(means board is getting hanged). I have mentioned the value of CONFIG_SYS_SCRATCH_VA as 0xf500. Thank you T. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Regarding MPC8640D second core initialization
On Dec 2, 2009, at 3:55 AM, Thirumalai wrote: > Thank you denx. > > Hi Jon, The email address you used for Jon is invalid (we need to update the maintainers file - Jon should weigh in here). > > I am using 2009-06 u-boot for MPC8640D based custom board. i just > want to know whether the second core of MPC8640D is kicked off > automatically or will it required by the user to kick using cpu > command If you have U-boot configured as you say below, and an SMP linux, then the second CPU will automatically come up. You don't need to do anything special. > like mpc85xx/mp.c. Also if am enabling the CONFIG_MP macro and > CONFIG_NUM_CPUS as 2, then the reset command of the target is not > working(means board is getting hanged). I have mentioned the value of > CONFIG_SYS_SCRATCH_VA as 0xf500. As far as your reset problem, I'm running a MPC8641D board using the latest u-boot, and I am able to reset it just fine when booted SMP. You're going to have to provide more information or look into this yourself. I can't tell you if your SCRATCH_VA is valid without knowing the entire memory map of your system... Cheers, Becky ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Regarding MPC8640D second core initialization
>
> On Dec 2, 2009, at 3:55 AM, Thirumalai wrote:
>
>> Thank you denx.
>>
>> Hi Jon,
>
> The email address you used for Jon is invalid (we need to update the
> maintainers file - Jon should weigh in here).
>
>>
>> I am using 2009-06 u-boot for MPC8640D based custom board. i just
>> want to know whether the second core of MPC8640D is kicked off
>> automatically or will it required by the user to kick using cpu command
>
> If you have U-boot configured as you say below, and an SMP linux, then
> the second CPU will automatically come up. You don't need to do anything
> special.
>
>> like mpc85xx/mp.c. Also if am enabling the CONFIG_MP macro and
>> CONFIG_NUM_CPUS as 2, then the reset command of the target is not
>> working(means board is getting hanged). I have mentioned the value of
>> CONFIG_SYS_SCRATCH_VA as 0xf500.
>
> As far as your reset problem, I'm running a MPC8641D board using the
> latest u-boot, and I am able to reset it just fine when booted SMP.
> You're going to have to provide more information or look into this
> yourself.
>
> I can't tell you if your SCRATCH_VA is valid without knowing the entire
> memory map of your system...
Thank you. I will just check and tell you.
>
> Cheers,
> Becky
>
Hi Becky,
Thank you for your reply. But when i boot smp-linux on this
configuration i got into kernel panic. The log is attached with this mail. I
am using linux-2.6.30 downloaded from kernel.org and my dts entry for cpu is
like this.
cpus {
#address-cells = <1>;
#size-cells = <0>;
PowerPC,8...@0 {
device_type = "cpu";
reg = <0>;
d-cache-line-size = <32>;
i-cache-line-size = <32>;
d-cache-size = <32768>; // L1
i-cache-size = <32768>; // L1
timebase-frequency = <0>; // From uboot
bus-frequency = <0>;// From uboot
clock-frequency = <0>; // From uboot
};
PowerPC,8...@1 {
device_type = "cpu";
reg = <1>;
d-cache-line-size = <32>;
i-cache-line-size = <32>;
d-cache-size = <32768>;
i-cache-size = <32768>;
timebase-frequency = <0>; // From uboot
bus-frequency = <0>;// From uboot
clock-frequency = <0>; // From uboot
};
};
--
Kernel Log
--
## Current stack ends at 0x3fa91a08
## Booting kernel from Legacy Image at 0040 ...
Image Name: Linux-2.6.30-dpvpx0689
Created: 2009-12-01 4:45:09 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size:2307361 Bytes = 2.2 MB
Load Address:
Entry Point:
Verifying Checksum ... OK
## Flattened Device Tree blob at 0400
Booting using the fdt blob at 0x400
Uncompressing Kernel Image ... OK
Loading Device Tree to 007fa000, end 007ff150 ... OK
## Transferring control to Linux (at address ) ...
Booting using OF flat tree...
Using DPVPX0689 machine description
Total memory = 1024MB; using 2048kB for hash table (at afe0)
Linux version 2.6.30-dpvpx0689 (r...@localhost.localdomain) (gcc version
4.0.0 (DENX ELDK 4.0 4.0.0)) #70 SMP Tue Dec 1 10:14:07 IST 2009
Found legacy serial port 0 for /s...@f600/ser...@4500
mem=f6004500, taddr=f6004500, irq=0, clk=4, speed=0
Found legacy serial port 1 for /s...@f600/ser...@4600
mem=f6004600, taddr=f6004600, irq=0, clk=4, speed=0
CPU maps initialized for 1 thread per core
(thread shift is 0)
console [udbg0] enabled
setup_arch: bootmem
dpvpx0689_setup_arch()
Found FSL PCI host bridge at 0xf6008000. Firmware bus number: 0->15
PCI host bridge /p...@f6008000 ranges:
MEM 0x8000..0x9fff -> 0x8000
IO 0xf800..0xfbff -> 0x
Single Board Computers from Data Patterns
Ported & Developed By COTS DIVISION
arch: exit
Top of RAM: 0x4000, Total RAM: 0x4000
Memory hole size: 0MB
Zone PFN ranges:
DMA 0x -> 0x0003
Normal 0x0003 -> 0x0003
HighMem 0x0003 -> 0x0004
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x -> 0x0004
On node 0 totalpages: 262144
free_area_init_node: node 0, pgdat a047d1c0, node_mem_map a07fd000
DMA zone: 1536 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 195072 pages, LIFO batch:31
HighMem zone: 512 pages used for memmap
HighMem zone: 65024 pages, LIFO batch:15
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260096
Kernel command line: root=/dev/nf
Re: [U-Boot] Regarding MPC8640D second core initialization
On Dec 2, 2009, at 10:36 PM, Thirumalai wrote: > > Thank you for your reply. But when i boot smp-linux on this > configuration i got into kernel panic. The log is attached with this > mail. I > am using linux-2.6.30 downloaded from kernel.org and my dts entry > for cpu is > like this. > > Calibrating delay loop... 199.68 BogoMIPS (lpj=99840) > Mount-cache hash table entries: 512 > mpic: requesting IPIs ... > Processor 1 found. > clockevent: decrementer mult[1999] shift[16] cpu[1] > Brought up 2 CPUs > Unable to handle kernel paging request for data at address 0x0004 > Faulting instruction address: 0xa0023e10 > Oops: Kernel access of bad area, sig: 11 [#1] > SMP NR_CPUS=2 DPVPX0689 > Modules linked in: > NIP: a0023e10 LR: a0023dd0 CTR: > REGS: cf841e90 TRAP: 0300 Not tainted (2.6.30-dpvpx0689) > MSR: 9032 CR: 24004028 XER: 2000 > DAR: 0004, DSISR: 4000 > TASK = cf83f930[1] 'swapper' THREAD: cf84 CPU: 0 > GPR00: cf841f40 cf83f930 cf841f50 > > GPR08: 0002 a10018f4 22004082 3fee6c00 > 3ff94000 > GPR16: ffbf ffbf7bff cf83a800 a10018e8 > a0491224 > GPR24: a049 a04558f8 cf801f20 a1006070 a10018e8 a10018f8 > > NIP [a0023e10] __build_sched_domains+0x354/0x464 > LR [a0023dd0] __build_sched_domains+0x314/0x464 > Call Trace: > [cf841f40] [a0023b98] __build_sched_domains+0xdc/0x464 (unreliable) > [cf841f90] [a04326ec] sched_init_smp+0x88/0x1e8 > [cf841fc0] [a0425a40] kernel_init+0x148/0x1f0 > [cf841ff0] [a00131f8] kernel_thread+0x4c/0x68 > Instruction dump: > 813e0008 2f9c 90090004 419e00d4 801e0034 70090100 40820010 > 801c0034 > 70090280 408200bc 83fc0008 83be0008 <807f0004> 801d0004 7c630214 > 907d0004 You took this panic because you tried to access 0x0004, which is probably not correct. I would also not generally expect to be seeing all these 0xaxxx addresses in your panic. Can you explain exactly what you've done to this kernel, and send a copy of the entire .dts and the .config? FYI, 2.6.30 boots SMP just fine on my 8641HPCN board. Cheers, Becky > ---[ end trace 31fd0ba7d8756001 ]--- > Kernel panic - not syncing: Attempted to kill init! > Rebooting in 180 seconds.. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
