Hello everyone,
Apologize if it's not the right channel to ask this kind of questions. I
have build an image using YOCTO for an arm7 platform. I'm creating a
fitImage with the kernel and the dtb file, but after installing the
image and starting the device I get this error:
```
Starting kernel ...
undefined instruction
pc : [<61008004>] lr : [<dff4d8c4>]
sp : dfefbda8 ip : 0000001e fp : 00000000
r10: dffa16e8 r9 : 00000000 r8 : dfefdf68
r7 : dff4db6c r6 : dfefe4f8 r5 : 61008000 r4 : dffa2e00
r3 : 0000293a r2 : 64ffa000 r1 : 0000127f r0 : 00000000
Flags: nzCv IRQs off FIQs off Mode SVC_32
Resetting CPU ...
```
Can someone give me some hint on what is the error's cause? How do I fix
the error? Can be a matter of load addresses?
In the attachment the entire startup log.
Thank you very much,
Pierluigi
Loading from usb device 0, partition 0: Name: Type: DISK 2.0 PMAP
Fit image detected...
....... FIT description: U-Boot fitImage for BISDN Linux/4.14.109+gitAUTOINC+ec36e24410/accton-as4610-54
Image 0 (kernel@1)
Description: Linux kernel
Type: Kernel Image
Compression: uncompressed
Data Start: 0x70000100
Data Size: 4104280 Bytes = 3.9 MiB
Architecture: ARM
OS: Linux
Load Address: 0x70000000
Entry Point: 0x70000000
Hash algo: sha1
Hash value: 4bee1e89735e2cf59a9722603ddadf6b1e43e062
Image 1 (f...@arm-accton-as4610.dtb)
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x703ea260
Data Size: 10554 Bytes = 10.3 KiB
Architecture: ARM
Hash algo: sha1
Hash value: 2b2305715b470c28f4fd53966d5771b9bf19ef73
Image 2 (ramdisk@1)
Description: core-image-base
Type: RAMDisk Image
Compression: gzip compressed
Data Start: 0x703ecc54
Data Size: 11489044 Bytes = 11 MiB
Architecture: ARM
OS: Linux
Load Address: 0x00000000
Entry Point: 0x00000000
Hash algo: sha1
Hash value: 856e6fe237a33af99a76af82c51504c1566b1e7f
Default Configuration: 'c...@arm-accton-as4610.dtb'
Configuration 0 (c...@arm-accton-as4610.dtb)
Description: 1 Linux kernel, FDT blob, ramdisk
Kernel: kernel@1
Init Ramdisk: ramdisk@1
FDT: f...@arm-accton-as4610.dtb
## Booting kernel from FIT Image at 70000000 ...
Using 'c...@arm-accton-as4610.dtb' configuration
Trying 'kernel@1' kernel subimage
Description: Linux kernel
Type: Kernel Image
Compression: uncompressed
Data Start: 0x70000100
Data Size: 4104280 Bytes = 3.9 MiB
Architecture: ARM
OS: Linux
Load Address: 0x70000000
Entry Point: 0x70000000
Hash algo: sha1
Hash value: 4bee1e89735e2cf59a9722603ddadf6b1e43e062
Verifying Hash Integrity ... sha1+ OK
## Loading init Ramdisk from FIT Image at 70000000 ...
Using 'c...@arm-accton-as4610.dtb' configuration
Trying 'ramdisk@1' ramdisk subimage
Description: core-image-base
Type: RAMDisk Image
Compression: gzip compressed
Data Start: 0x703ecc54
Data Size: 11489044 Bytes = 11 MiB
Architecture: ARM
OS: Linux
Load Address: 0x00000000
Entry Point: 0x00000000
Hash algo: sha1
Hash value: 856e6fe237a33af99a76af82c51504c1566b1e7f
Verifying Hash Integrity ... sha1+ OK
## Flattened Device Tree from FIT Image at 70000000
Using 'c...@arm-accton-as4610.dtb' configuration
Trying 'f...@arm-accton-as4610.dtb' FDT blob subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x703ea260
Data Size: 10554 Bytes = 10.3 KiB
Architecture: ARM
Hash algo: sha1
Hash value: 2b2305715b470c28f4fd53966d5771b9bf19ef73
Verifying Hash Integrity ... sha1+ OK
Booting using the fdt blob at 0x703ea260
XIP Kernel Image ... OK
OK
boot_prep_linux commandline: quiet console=ttyS0,115200
Loading Device Tree to 64ffa000, end 64fff939 ... OK
Starting kernel ...
undefined instruction
pc : [<70000004>] lr : [<dff4d8c4>]
sp : dfefbb88 ip : 0000001e fp : 00000000
r10: dffa16e8 r9 : 00000000 r8 : dfefdf68
r7 : dff4db6c r6 : dfefeb38 r5 : 70000000 r4 : dffa2e00
r3 : 0000293a r2 : 64ffa000 r1 : 0000127f r0 : 00000000
Flags: nzCv IRQs off FIQs off Mode SVC_32
Resetting CPU ...
resetting ...
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
