stuckd: Bringing up secondary CPUs

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

stuckd: Bringing up secondary CPUs

Jump to solution
2,061 Views
muaxi8
Contributor V

my custome board is lx2080。

The kernel is stuck during boot smp, location is  Bringing up secondary CPUs ...

 Can you offer some ideas to solve this problem。

...........

[ 0.000000] ITS: using cache flushing for cmd queue
[ 0.000000] GICv3: Using preallocated redistributor tables
[ 0.000000] val: 207fe0008f
[ 0.000000]
[ 0.000000] 11111 gic_rdists->prop_table_pa 207fe00000
[ 0.000000] 22222 gic_rdists->prop_table_pa 207fe00000
[ 0.000000] prop_table_va (____ptrval____)
[ 0.000000] LPI_PROPBASE_SZ 10000
[ 0.000000] GICv3: using LPI property table @0x000000207fe00000
[ 0.000000] GICv3: CPU0: using reserved LPI pending table @0x000000207fe10000
[ 0.000000] random: get_random_bytes called from start_kernel+0x2b8/0x450 with crng_init=0
[ 0.000000] arch_timer: cp15 timer(s) running at 25.00MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x5c409fb33, max_idle_ns: 440795203156 ns
[ 0.000002] sched_clock: 56 bits at 25MHz, resolution 39ns, wraps every 4398046511103ns
[ 0.008378] Console: colour dummy device 80x25
[ 0.012915] Calibrating delay loop (skipped), value calculated using timer frequency.. 50.00 BogoMIPS (lpj=100000)
[ 0.023386] pid_max: default: 32768 minimum: 301
[ 0.028144] LSM: Security Framework initializing
[ 0.032872] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 0.040361] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 0.072334] ASID allocator initialised with 32768 entries
[ 0.085810] rcu: Hierarchical SRCU implementation.
[ 0.098700] Platform MSI: gic-its@6020000 domain created
[ 0.104124] PCI/MSI: /interrupt-controller@6000000/gic-its@6020000 domain created
[ 0.111729] fsl-mc MSI: gic-its@6020000 domain created
[ 0.124938] smp: Bringing up secondary CPUs ...

0 Kudos
1 Solution
2,055 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please download image lsdk2012_yocto_tiny_LS_arm64.itb to do verification on your target board.

wget https://www.nxp.com/lgfiles/sdk/lsdk2012/lsdk2012_yocto_tiny_LS_arm64.itb

You also could get it 

链接: https://pan.baidu.com/s/1IyuUe0PHXbYiIb1RVHdSzw 提取码: 9n7z

Then run the following command on the target board.

=> pri bootargs
bootargs=console=ttyAMA0,115200 root=/dev/ram0 earlycon=pl011,mmio32,0x21c0000 ramdisk_size=0x2000000
=> tftp 0xa0000000 lsdk2012_yocto_tiny_LS_arm64.itb

=> bootm 0xa0000000#lx2160ardb

If this problem remains, please create a bareboard project in CodeWarrior, then run and debug the program on the second core. Please refer to the section "3.2 Working with bareboard application" in C:\Freescale\CW4NET_v2020.06\CW_ARMv8\ARMv8\Help\Getting_Started_for_CW_ARMv8.pdf.

yipingwang_0-1627631411801.png

 

View solution in original post

0 Kudos
4 Replies
2,056 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please download image lsdk2012_yocto_tiny_LS_arm64.itb to do verification on your target board.

wget https://www.nxp.com/lgfiles/sdk/lsdk2012/lsdk2012_yocto_tiny_LS_arm64.itb

You also could get it 

链接: https://pan.baidu.com/s/1IyuUe0PHXbYiIb1RVHdSzw 提取码: 9n7z

Then run the following command on the target board.

=> pri bootargs
bootargs=console=ttyAMA0,115200 root=/dev/ram0 earlycon=pl011,mmio32,0x21c0000 ramdisk_size=0x2000000
=> tftp 0xa0000000 lsdk2012_yocto_tiny_LS_arm64.itb

=> bootm 0xa0000000#lx2160ardb

If this problem remains, please create a bareboard project in CodeWarrior, then run and debug the program on the second core. Please refer to the section "3.2 Working with bareboard application" in C:\Freescale\CW4NET_v2020.06\CW_ARMv8\ARMv8\Help\Getting_Started_for_CW_ARMv8.pdf.

yipingwang_0-1627631411801.png

 

0 Kudos
2,033 Views
muaxi8
Contributor V

i download image lsdk2012_yocto_tiny_LS_arm64.itb to do verification on your target board, it is still can not Boot the second cpu. The log is attached。

then i create a bareboard project in CodeWarrior, then  debug the program on the second core, There seems to be a mistake。

muaxi8_0-1628577079004.png

 

0 Kudos
2,028 Views
yipingwang
NXP TechSupport
NXP TechSupport

In your attached log, it seems that you still used your own image created on 2021-08-10.

Please download the pre-built image lsdk2012_yocto_tiny_LS_arm64.itb and run the following command.

=> tftp 0xa0000000 lsdk2012_yocto_tiny_LS_arm64.itb

=> bootm 0xa0000000#lx2160ardb

 

0 Kudos
2,022 Views
muaxi8
Contributor V

it is  Uboot problem , has been resolved

0 Kudos