• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 101 subscribers
  • Views 2105 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/AM3352: Arago images do not boot

Divyeshkumar M
Expert 1390 points
Part Number: AM3352
Other Parts Discussed in Thread: AM3358

Tool/software: Linux

Hello there,

We have a custom board using AM3352 processor, we are in a board bring up state of the project. Our custom board is based on the Beaglebone Green Wireless device, and I have compiled the latest Arago images for the project using processor-sdk-04.00.00.04. I compiled the entire tisdk using arago-core-tisdk-image. After the successful compilation I have list of images in my Build deploy directory. Listed below are the few I wanted to use to boot my custom board.

  1. MLO-am335x-evm-2017.01+gitAUTOINC+9fd60700db-r4 ----> MLO

  2. u-boot-am335x-evm-2017.01+gitAUTOINC+9fd60700db-r4.img ----> u-boot.img

  3. zImage--4.9.28+git0+eed43d1050-r22c.arago5.tisdk3-am335x-bonegreen-20170912170513.dtb

  4. zImage--4.9.28+git0+eed43d1050-r22c.arago5.tisdk3-am335x-evm-20170912170513.bin ----> zImage

  5. tisdk-rootfs-image-am335x-evm-20170914131632.rootfs.tar.xz

I have changed name of all the files appropriately. 

First of all, I want to boot the images (at least MLO and u-boot) from the SD Card, and to create a compatible SD Card I have used following technique.

After I created the SD Card, I put MLO, u-boot.img and other files on it and inserted to the custom board. I made sure that SYSBOOT are configured in a way it can boot from SD Card. 

MAIN ISSUE:


The problem is, when I insert the SD card and turn on the board, it does not show anything on the console. Without SD card inserted I can see ROM code trying UART boot with "CCCCCCCCCCCCCCCCCCC.." on console.

I also have beaglebone Green Wireless and it's SD card .img file. If I try to boot beaglebone Green Wireless using the same SD card, it does boot properly through SD card and I can see the Arago Project console login shell.

If I burn the Beaglebone Green Wireless' .img file to an SD card and insert it to my custom board, my custom board does boot from the SD card and complete till kernel booting.

SAME THING IS HAPPENING FOR BEAGLEBONE BLACK is well.

QUE. :

Since, Beaglebone Green Wireless has AM3358, does that make a difference in booting process? 

What is the possible cause of this issue?

What is the ideal SD card booting process for AM3352?


Thank you,

Divyeshkumar

  • 0
    Expert 2020 points
    Hi Divyeshkumar,

    If I understood your issue properly, then, your custom board MLO, uboot and kernel images are not booting properly but BB green wireless MLO, uboot and kernel images are bootting fine on the custom board.
    If above case is correct, then, can you try to rename the custom board MLO, uboot and kernel images same as beaglebone Green's MLO, uboot and kernel files names and try to boot on the custom board?

    thanks,
    Prabhuraj
    BlackPepper Technologies
  • 0 in reply to prabhuraj tavag20
    Expert 1390 points

    Hi Prabhuraj,

    I have already kept the file names same as of BBGW's.

    Thanks,

    Divyeshkumar

  • 0 in reply to Divyeshkumar M
    Expert 2020 points

    Thanks Divyesh.
    Can you keep the BBGW's MLO in custom board's uboot and kernel image sdcard and see what happens?

    The uboot and kernel image should be of custom board.
    Basically, it will help us segregate if the problem.
    Let me know your views.

    Regards,
    Prabhuraj
    BlackPepper Technologies

  • 0 in reply to prabhuraj tavag20
    Expert 1390 points

    If I keep the MLO of BB and put custom u-boot, It does not boot the u-boot. Logs are below:

    U-Boot SPL 2016.03-00002-g30051ac (Jun 06 2016 - 11:28:30)
    Timed out in wait_for_event: status=0000
    Check if pads/pull-ups of bus 0 are properly configured
    Could not probe the EEPROM; something fundamentally wrong on the I2C bus.
    Could not get board ID.
    Timed out in wait_for_event: status=0000
    Check if pads/pull-ups of bus 0 are properly configured
    Trying to boot from MMC
    reading args
    spl_load_image_fat_os: error reading image args, err - -1
    reading u-boot.img
    reading u-boot.img

    Thanks,

    Divyeshkumar

    PS: It's not even showing the U-boot version info at top, if there's any issue with the peripherals, it should at least show the u-boot version info and then get stuck in-between. 

  • 0 in reply to Divyeshkumar M
    Expert 2020 points
    Okay good. We will first boot the custom MLO on custom board. So how different is MLO of BBGW and MLO of custom board.
    What are the changes you have made in custom MLO compared to BBGW MLO source code?
    Are you compiling the custom MLO similar to BBGW MLO?
    Also, since BBGW's MLO is booting on custom board, I am assuming you have kept the low level board details as similar to BBGW.

    Thanks,
    Prabhuraj
    BlackPepper Technologies
  • 0 in reply to prabhuraj tavag20
    Expert 1390 points
    I have not made any changes to the uboot so far, I have just downloaded the tisdk and compiled it. I am using the native images out of the compilation. Yes, most of the basic peripherals are the same as of BBGW, hence BBGW's uboot and MLO working on my custom board. Moreover, my custom MLO and uboot (build out of tisdk untouched) working OK on BBGW, so I am confused why wouldn't it work on my custom board.
    I have downloaded the BBGW's SD card image and extracted the MLO and uboot from it.

    Thanks,
    Divyeshkumar
  • 0 in reply to Divyeshkumar M
    Expert 1390 points
    HI Prabhuraj,

    Do we have any update? Next thing I am gonna check is the U-boot init in debug mode, to see how the startup functioning.

    Thanks,
    Divyeshkumar
  • 0 in reply to Divyeshkumar M
    Expert 1390 points
    Hi all,

    Making a custom board platform resolved the issue.

    Thanks,
    Divyeshkumar
  • 0 in reply to Divyeshkumar M
    Expert 2020 points

    Hi Divyeshkumar,
    Good to know that you could make progress. Can you please provide more details on how you resolved the issues?
    It will greatly help other community members.

    Thanks,
    Prabhuraj
    BlackPepper Technologies

  • 0 in reply to prabhuraj tavag20
    Expert 1390 points
    HI Prabhuraj,

    I have solved the issue by creating a custom board package in U-boot. The main issue was, as I don't use the EEPROM to detect the board type in my custom board, those binaries were not working properly on my board.

    Thanks,
    Divyeshkumar