• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 32 subscribers
  • Views 458 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.

MCU-PLUS-SDK-AM243X: EVM-board stopped working out of nowhere

Felix Heil
Expert 1235 points
Part Number: MCU-PLUS-SDK-AM243X


Hello,

my AM243X-EVM stopped working from one day to the next day.
I always followed the startup-procedure, having the power switch to off, connecting the power source, the debugger and then turn the power on. so far all LEDS are going green. I also always follow the description in the documentation for EVM DEV-Boot by setting boot-pins to DEV-Boot-mode, like described in the picture. When I then try executing the script like it is described I run into this error:

This is new and never happened before. I did not change the target configuration in the meanwhile or anything else. it just stopped when I started it up another day. A manual connect just shows shortly the 0x00000024 and then it restarts automatically after some seconds and I can't reconnect at all, always showing the DAP-access-error:

The board itself is probably not populated with an hs-fs-sitara but with an gp-sitara since it was sealed at 09/08/22 but nevertheless it did work that way before. But also if I try to do it the old way with the no-boot mode it doesn't work. it won't even read out the boot mode correctly and always tells me the boot mode is 0x00.

A repower leads to the same behaviour all the time. I also restarted CCS, my PC, made everything powerless, disconnected and reconnected everything. the debugger, the power-cable of the evm, each one for itself, all together.... but the problem persists. A colleaguw also had this issue out of nowhere and we weren't able to fix this.

How can I solve this problem?

Best regards
Felix

  • 0
    TI__Guru 53508 points

    Hello Felix,

    Thanks for reaching out to Texas Instruments E2E support forum.

    Can you please confirm are you using a GP or HSFS device?

    To check the device type, please refer Device Type Identification.

    Please note the script(load_dmsc_hsfs.js) which you are running is meant for HSFS Device only. If the device type is GP then it will not work. You have to use the script(load_dmsc.js) provided in older version of MCU+SDK. (i.e. SDK v08.06). 

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Expert 1235 points

    Hello Tushar, and thanks for your reply.

    I just checked the print on the SoC which should also tell this information:


    it is SF GH IALV
    The second GH should means:
    G - Non-Functional Safety
    H - Secure
    Anyway it start with an X at first for the AM-description, so it's also an prototype.

    Also we solved it by setting it to Uart-Bootmode and flashing the SBL_NULL onto it, now I can connect again, so we won't investigate further. But it's weird that the DEV_BOOT stopped working suddenly.