• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 251 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.

MCU-PLUS-SDK-AM243X: Trying to flash the enet_cpsw_tcpserver example without success

Xander
Prodigy 30 points
Part Number: MCU-PLUS-SDK-AM243X
Other Parts Discussed in Thread: UNIFLASH

I'm trying to flash the enet_cpsw_tcpserver example to the AM243x Launchpad with the SBL OSPI bootloader, but the bootloader gets stuck when flashed.

I flashed using the UART bootmode with the command "python uart_uniflash.py -p COM7 --cfg=sbl_prebuilt\am243x-lp\default_sbl_ospi.cfg"

Everything in the .cfg file is according to the "Flash hello world example" here and it gets stuck on the following:

Fullscreen
1
2
3
DMSC Firmware Version 8.4.7--v08.04.07 (Jolly Jellyfi
DMSC Firmware revision 0x8
DMSC ABI revision 3.1
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Two questions about this:

1. Why is it getting stuck? I flashed the LED blink examples which ran without any problems, but with using peripherals like ENET and MCSPI the bootloader gets stuck.

2. The firmware version is at 8.4.7, while the examples state version 21.1.1--v2021.01a, where do I get this newer version.

  • 0
    TI__Mastermind 25975 points

    Hi Xander Moerkerken,

    We are also able to reproduce the issue on our end. We apologize for the inconvenience caused and thank you for pointing out this issue.

    Let us come back with a fix on this issue.

    Thanks and Regards,
    Aakash 

  • 0 in reply to Aakash Kedia
    Prodigy 30 points

    Do you have any ETA on that?

  • 0 in reply to Xander
    TI__Mastermind 25975 points

    Hi Xander,

    We do not have full insight on the issue here, so here are some timeline updates -

    1. We will come back with some update by today/tomorrow.
    2. Depending on the issue, if a workaround is possible, we will share that information ASAP.
    3. If a fix is only option here, we will share a patch with you. Right now, the estimate is Friday given that we still have to debug the SBL and find the exact issue here.

    Best Regards,
    Aakash

  • +1 in reply to Aakash Kedia
    TI__Mastermind 25975 points

    Hi Xander,

    I suggest you to change the linker.cmd of the enet_lwip_tcpserver in the application.

    Change the following line in the linker
        MSRAM     : ORIGIN = 0x70080000 , LENGTH = 0x160000
    it should look like this -
    This resolves the problem. I have recorded an internal ticket to raise the issue as well.
    Hope this helps.

    Best Regards,
    Aakash
  • 0 in reply to Aakash Kedia
    Prodigy 30 points

    Thankyou Aakash for the quick resolving!