Boot kernel stopped at "cpu_id = 0"

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

Boot kernel stopped at "cpu_id = 0"

922 Views
wenbochen
Contributor I

I tried burn image on imx6q-sabresd board, but it stopped ar "cpu_id =0" when boot kernel from mfgtool.  

The log is here:

.......
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
g_mass_storage gadget: Mass Storage Function, version: 2009/09/11
g_mass_storage gadget: Number of LUNs=1
lun0: LUN: removable file: (no medium)
g_mass_storage gadget: Mass Storage Gadget, version: 2009/09/11
g_mass_storage gadget: g_mass_storage ready
input: gpio-keys.27 as /devices/soc0/gpio-keys.27/input/input3
snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 1970-01-01 00:00:01 UTC (1)
ALSA device list:
#0: wm8962-audio
#1: imx-hdmi-soc
Freeing unused kernel memory: 296K (80bdf000 - 80c29000)
Starting UTP
mknod: /dev/tty0: File exists
ln: /etc/mtab: File exists
disable turn off display
Starting udev
udevd[158]: starting version 182
uuc 0.4 [built Apr 5 2014 08:45:57]
UTP: Waiting for device to appear
UTP: file/device node /dev/utp already exists
cpu_id is 0

How to solve it? I need your help, thanks!! :smileyhappy:

Labels (1)
0 Kudos
4 Replies

641 Views
joanxie
NXP TechSupport
NXP TechSupport

what mfgtool version and .vbs do you use when you download image? customized image or demo image?

0 Kudos

641 Views
wenbochen
Contributor I

Hi Xie:

         Mfgtool version is 3.10.17, which I download from NXP.COM, and the image is customized, version is 3.10.17. :-D

0 Kudos

641 Views
joanxie
NXP TechSupport
NXP TechSupport

which .vbs do you use? if you use demo image in the mfgtool, does it work? pls try to use default .vbs first, try to confirm if your custimzed image has problem

0 Kudos

641 Views
wenbochen
Contributor I

Thank you, Xie. But now I have solved the problem. The main problem is that the firmware of MFGtool doesn't work, so I use the default  image of Mfgtool.

0 Kudos