• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 55 subscribers
  • Views 865 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/AM5728: AM5728 Custom board SPL Debug

vijay Patil
Intellectual 810 points
Part Number: AM5728


Tool/software: Code Composer Studio

Hi,

I am using AM5728 Custom board. My requirement spl debug using CCS.
I am using the following process to SPL Debug of AM5728 board:

1- On CCSv7.3 as File->New->Project->C/C++->Makefile Project with Existing Code for Uboot source project

2- Build and Compile Uboot source by using CCSv7.3
   Make File Target in detail training.ti.com/linux-board-porting-series-module-6-building-u-boot-ccs
   or
   using following command

export PATH=/home/user/ti-processor-sdk-linux-am57xx-evm-04.01.00.06/linux-devkit/sysroots/x86_64-arago-linux/usr/bin:$PATH

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- distclean

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- am57xx_evm_config

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

3- Setup target configuration with "Blackhawk XDS100v2-USB System Trace Emulator" and Board or Device: AM5728.

4- Launch Configuration and connect to the CortexA15_0 target.

5- CPU Reset (SW) to CortexA15_0 target for changing the ARM core mode from THUMB-2 to ARM or Core Registers -> CPSR register list change the T register from 1 to 0

6- Load Memory with (Uboot source dir)/spl/u-boot-spl.bin, start address 0x40300000 (CONFIG_SPL_TEXT_BASE value in u-boot-spl.cfg) and type-size 32bits

7- Load symbols from (Uboot source dir)/spl/u-boot-spl (code and data offset left empty)

8- Set Program Counter Register(PC) to address 0x40300000

With above test process 3 boards i am able to test spl using ccs and checked the following message on serial console:

U-Boot SPL 2017.01-00360-g9f4b0ab-dirty (Aug 14 2020 - 18:17:28)
DRA752-GP ES2.0
SPL: failed to boot from all boot devices
### ERROR ### Please Reset the board ###

But I am having problem with 1 board in which i am unable to get any SPL Debug log on serial console.
Please help me to resolve the issue.

Thanks

Vijay Patil

  • 0
    TI__Guru**** 164200 points

    Hi VIjay,

    Do you have any other boot mode? Preferably MMC-SD. That would be quick
    to check if SPL comes up on that board.

    If the same steps are working on 3 boards and not on 1 board then does it
    mean something bad with that particular board?

    - Keerthy

  • 0 in reply to Keerthy J
    Intellectual 810 points

    Hi Keerthy,

    Thanks for reply.

    I tried alternate boot method which is MMC-SD. I am able to boot the other 3 boards using SD card boot.

    But the 1 board which is having issue that is unable to boot using SD.

    My 1 board which i am unable to boot using SD-MMC so we have tried SPL Debug using CCS.

    But using SPL debug also i am getting any SPL logs on serial console.

    Please suggest/provide me if any option is available.

    Thanks & Regards,

    Vijay Patil

  • 0 in reply to vijay Patil
    TI__Guru**** 164200 points

    Hi Vijay,

    If you have UART boot supported then follow this post:

    https://e2e.ti.com/support/processors/f/791/p/884254/3294003#3294003

    Try to see if you get some characters on the failing board using UART boot.

    Best Regards,
    Keerthy

  • 0 in reply to Keerthy J
    Intellectual 810 points

    Hi Keerthy,

    I have changed the boot mode setting to UART Boot and loaded the files using following command:

    vijay@vijay#./serial-boot.pl -p /dev/ttyUSB0 -s u-boot-spl.bin-d1 -t40

    vijay@vijay# sx -kb --ymodem u-boot.img < /dev/ttyUSB0 > /dev/ttyUSB0


    But still i am unable to see anything on serial console.

    Please provide if any other debug method is there.

    Thanks & Regards,

    Vijay Patil

  • 0 in reply to vijay Patil
    TI__Guru**** 164200 points

    Hi Vijay,

    Since 3 boards do work as expected i suspect some hardware related issue with the failing
    board. I am looping it to the hardware expert to get more insight.

    Best Regards,
    Keerthy

  • 0 in reply to Keerthy J
    TI__Guru 52915 points

    Vijay,

    Yes - with 3 boards working and 1 board failing - it could be a manufacturing issue.  If I understand - you get no response on the failing board (no console message from any boot mode?)

    Have you verified all power rails to the SoC are at a valid level?

    Have you verified input clocks are correct frequency and voltage levels?

    Is the power-on reset signal asserted until after all supplies are valid level and input clock is stable?

    Does the device come out of reset (check that the RSTOUTn signal is de-asserted).

    If all of those things are correct - then device should be booting.