• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 217 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.

TMS570LS0714: -

Ermine Jose
Prodigy 20 points
Part Number: TMS570LS0714


Hello, 

I have been trying to incorporate the bootloader example application for UART in my board. The UART comm is linked through RS485 module through i am trying to upload the binary. I m using tera term to send bin as per configuration on YMODEM protcol. The issue i'm facing is 9 times out of 10. The file is not getting updated. one time the final is getting updated and stops half way through. how do i effectively go about solving this. thank you

  • 0
    TI__Guru**** 198766 points
    Ermine Jose said:
    The UART comm is linked through RS485 module through i am trying to upload the binary.

    Do you use RS485 instead of RS232?

    Does Tera Term use the same baudrate and STOP bit as in bootloader?

    Please check if any data has been programmed to the flash starting at the Application start address.

  • 0 in reply to QJ Wang
    Prodigy 20 points

    Hello, yes I use RS 485 instead. 

    Yes the tera term uses the same baudrate, stop bit as in bootloader.

    My issue can be mentioned in two parts,

    1) Sometimes, when i compile the Bootloader files with optimization on, the write from tera term is successful for one byte group (1024 bytes). The remaining bytes are not transmitted due some mismatch in the RS 485 TX/RX process which we can debug. 

    2) Most times, when I compile the application,and write attempt happens from tera term, the debugger enters undef area. The compiler version is TI v18.1.4 LTS and Code composer studio is  8.3.0.00009

    The issue with RS 485 transmission can be fixed or debugged based on the delay information. but i'm not sure how to handle this undef behaviour while debugging.

  • 0 in reply to Ermine Jose
    TI__Guru**** 198766 points

    Hi,

    Please refer to the program tips and timeout setup in ymodem protocol. If you use different baudrate, the delay time should be change accordingly.

    http://textfiles.com/programming/ymodem.txt

    Undefined instruction exception can occur if the CPU does not understand the fetched instruction.

    There are no Fault Status and Fault address registers associated with this exception; only Link register (R14_UND) provides relevant information. The instruction that caused the UNDEF abort is at R14_UND – 4.

    Check the instruction at the address read from R14_UND - 4.

    1. If it is a valid instruction, check whether the mode used (ARM or THUMB) for execution is correct (A mode mismatch for a valid instruction can cause undefined instruction exception).
    2. If the instruction is invalid, check for address corruption or RAM corruption.