• Resolved

Linux/AM3354: U-boot showing data abort error

Part Number: AM3354

Tool/software: Linux

I running the Kernel version 4.9.28 and uboot 2017.1 in the custom board which design is similar to beagle-bone black, kernel is not booting. U-boot is booting with some warnings, kindly check the logs stated below.

U-Boot SPL 2017.01-00319-g7752743-dirty (Sep 22 2017 - 10:28:50)
tps65217: Set UVLO
Trying to boot from MMC1
spl: falcon_args_file not set in environment, falling back to default
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img


U-Boot 2017.01-00319-g7752743-dirty (Sep 22 2017 - 10:28:50 +0530)

CPU  : AM335X-GP rev 2.1
I2C:   ready
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
** First descriptor is NOT a primary desc on 1:1 **
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Error: usb_ether address not set.

Press SPACE to abort autoboot in 2 seconds
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
reading uEnv.txt
3051 bytes read in 154 ms (18.6 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...

I tried running below commands to boot zimage:

1. Press SPACE to abort autoboot in 2 seconds
=> run mmcboot
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
reading uEnv.txt
3051 bytes read in 154 ms (18.6 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
(Note:not going forward after this)
2. Press SPACE to abort autoboot in 2 seconds
=> go 0x80200000
## Starting application at 0x80200000 ...
undefined instruction
pc : [<801ff000>]          lr : [<80200004>]
reloc pc : [<60aac000>]    lr : [<60aad004>]
sp : 9df32d78  ip : 0000001c     fp : 00000002
r10: 9ffa0b58  r9 : 9df32ed8     r8 : 9df360c8
r7 : 9ff5450d  r6 : 00000002     r5 : 80200000  r4 : 9df360cc
r3 : 80200000  r2 : 9df360cc     r1 : 9df360cc  r0 : 00000001
Flags: nzCv  IRQs off  FIQs on  Mode SVC_32
Resetting CPU ...

resetting ...
(Note:not going forward after this)
Please find the attached uEnv file.
  • In reply to Kemal R. Shakir:

    Hi,

    I did few trials, to find the issue.

    I am using 4.9.28 kernel and uboot-2017.1 in my custom board which is similar to beaglebone black.

    The custom board is working in kernel version 3.14 with device tree. Now i want to made it to work on kernel 4.9.28 + uboot.2017.1.

    Trial 1: uboot-2017.1 + kernel 4.9.28 + custom board dts ---------> Not Booting

    Trail 2: Uboot-2017.1 + kerenl 3.14 + custom board dts ---------> Booting properly

    Trail 3: uboot-2017.1 + kernel 3.14 + am335x-evm.dts ---------> Booting properly

    According to the above trails, Uboot and dts is working fine..., the issue is with kernel 4.9.28.

    The following steps, i followed to configure and compile the kernel 4.9.28. Kindly suggest, if any of the steps i should modify/add.

    Steps 1: Downloaded the SDK and extracted it.

    Steps 2: Under kernel source tree,
    make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- mrproper

    make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- tisdk_am335x-evm_defconfig

    make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- uImage dtbs(here .dts files are not compiled).
    So i did the following command

    make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- am335x-evm.dtb

    step 3: Partitioned SDCARD

    step 4: copied MLO,uboot.img to /media/boot , Copied roofs, copied zimage,dtb to /media/rootfs/boot/

    step 5: after power up the board. I am getting the following error

    ## Booting kernel from Legacy Image at 80200000 ...
    Image Name: Linux-4.9.28-geed43d1050
    Created: 2017-10-13 7:11:04 UTC
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 3590872 Bytes = 3.4 MiB
    Load Address: 80200000
    Entry Point: 80200000
    Verifying Checksum ... OK
    ## Flattened Device Tree blob at 80f80000
    Booting using the fdt blob at 0x80f80000
    Loading Kernel Image ... OK
    Using Device Tree in place at 80f80000, end 80f8d75d

    Starting kernel ...


    Error: unrecognized/unsupported machine ID (r1 = 0x0000157d).

    Available machine support:

    ID (hex) NAME
    ffffffff Generic DT based system
    ffffffff Generic AM33XX (Flattened Device Tree)

    Please check your kernel config and/or bootloader.
  • In reply to madhu sundar:

    Please, check this post.