• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 583 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.

SK-AM64B: No serial output while first power up, no possibility to write Flash SOC Initialization Binary

Sandro Kuhr
Prodigy 30 points
Part Number: SK-AM64B
Other Parts Discussed in Thread: UNIFLASH

Hello,
I would like to evaluate the SK-AM64B. I have CCS installed and the SDK. The debugging of a FreeRTOS example application failed so I found out via the forum that access is only possible if the Flash SOC Initialization Binary is flashed. For this I set the DIP switches to serial boot. According to the following link, there should then be an output on the UART after powering up the Board: https://software-dl.ti.com/mcu-plus-sdk/esd/AM64X/latest/exports/docs/api_guide_am64x/EVM_SETUP_PAGE.html No SD card is inserted. Unfortunately, I am not receiving any characters in the terminal program, tested with all interfaces. Also the Python scripts to load the flash memory can not establish a connection.

What do I have to do to debug the board via CCS?

  • 0
    Intellectual 602 points
    Sandro Kuhr said:
    What do I have to do to debug the board via CCS?

    If your board has a LED that is active and glowing red on the bottom side of the board, it is dead.

    Would you be able to post a picture of the boot switches in the UART boot mode?

  • 0 in reply to Fred Fisher
    Prodigy 30 points

    Thank you for your reply!
    I have set the DIP switches as in the picture from the manual. The red LED LD15 lights up as soon as the USB-C is plugged in, regardless of whether the switch is on or not.
    What do I have to do to fix the problem?

  • 0 in reply to Fred Fisher
    Prodigy 30 points

    After I changed the USC-C cable, the red LED is no longer lit and the serial output works. Unfortunately I get an error message when flashing. What could be the reason for this?

  • 0 in reply to Sandro Kuhr
    Intellectual 602 points 

    $sudo apt install gtkterm

    You should see it send a  the letter "c" and a string of numbers out if it is working fine. That is according to the docs. Make sure you have the correct USB port selected.

  • 0 in reply to Fred Fisher
    Prodigy 30 points

    I work with windows, so sudo will not work for me.

    I have another terminal program and can also receive the character C. Otherwise the python script would not have run halfway through either. I also decoded the output of the characters after power on and found out then my device is a HS-FS type and therefore apparently different from the normal? I have adjusted the files according to these instructions https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1183777/faq-am64x-how-can-i-flash-soc-initialization-binaries-on-hs---fs-hw-versions?tisearch=e2e-sitesearch&keymatch=faq%3Atrue but unfortunately it still does not work. See screenshot above.

  • 0 in reply to Sandro Kuhr
    TI__Mastermind 47096 points

    Hi Sandro,

    Does the issue still persist?

    If yes, can you confirm if you are setting the right UART bootmode.

    The UART bootmodes for SK and EVM are different.

    Also make sure to have hs_fs images as mentioned in the above FAQ.

    Moreover, you can try power cycling the EVM, maybe more than once. That way the known issue "XMODEM send failed" will be resolved.

    Regards,

    Vaibhav

  • 0 in reply to Vaibhav Kumar
    Prodigy 30 points

    Hello, unfortunately I have had no success flashing the bootloader to the flash memory on the board. Therefore I have used an SD card. But I would still like to use the flash on the board.
    I have used the hs_fs image and have also powered the board on and off a few times. Unfortunately, the problems described here in the article still show up.
    What can I do to solve the problem?

  • 0 in reply to Sandro Kuhr
    TI__Mastermind 47096 points

    Hi Sandro,

    Lets clarify few things.

    So you are using AM64x EVM correct ?

    Regards,

    Vaibhav

  • 0 in reply to Vaibhav Kumar
    Prodigy 30 points

    I am using SK-AM64B, not the EVM. DIP switches are set as shown in the picture above.

    Regards

  • +1 in reply to Sandro Kuhr
    TI__Mastermind 47096 points

    Hi Sandro,

    Sandro Kuhr said:

    After I changed the USC-C cable, the red LED is no longer lit and the serial output works. Unfortunately I get an error message when flashing. What could be the reason for this?

    If its a SK, I have seen you have tried the command where you have written --cfg=sbl_prebuilt/am64x-evm/default_sbl_null.cfg

    Can you instead write the following and check ?

    python uart_uniflash.py -p COM14 --cfg=sbl_prebuilt/am64x-sk/default_sbl_null.cfg


    Directory will remain the same that is inside MCU PLUS SDK INSTALL PATH/tools/boot

    After you have tried, please let me know.

    Regards,

    Vaibhav

  • 0 in reply to Vaibhav Kumar
    Prodigy 30 points

    How can I generate the initialization file if I don't use the AM64x-SK board but use the processor on my own hardware? So how to generate the .tiimage file?

  • 0 in reply to Sandro Kuhr
    TI__Mastermind 47096 points

    Hi Sandro,

    You can do the following steps to generate the tiimage files.

    Lets say in your configuration file, you see that sbl_uart_uniflash_stage2.release.appimage(Suppose) is missing.

    Then you can go to the respective directory, in this case you can see the screenshot and simply run gmake all. Please find attached screenshot.

    You can follow the above steps for building tiimage files as well.

    BR Vaibhav