• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 347 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.

TMS320DM648 UART Boot

Fredrik35148
Expert 7485 points
Other Parts Discussed in Thread: TMS320DM648

Hi,

My customer is using the UART Boot feature of the TMS320DM648, and are experiencing some problems when the data transfer of the AIS script is delayed.

The AIS script is transmitted to the DSP on CAN through an MCU and is therefore split into 7 blocks. These blocks are forwarded to the DSP with a small delay in between (less than a second). This seems to work fine unless the delay between two blocks are to large (more than two seconds). When this happens the DSP will respond with DATA CORRUPT after the transmission of the sixth block, which is the first block to contain a check CRC op-code. We have monitored the UART communcation and there is no difference in the transmitted data from our MCU between a successful and an unsuccessful download.

We have seen that there is an error code ERR_TIMEOUT_WAITING_FOR_HOST in the bootloader user guide, but there is no description of this.

Is this behaviour related to a timeout in the DSP bootloader?
If so, how long is this timeout?
Can this timeout be reset by some op-code during the delay?

Thanks,
Fredrik

  • 0
    TI__Expert 7485 points

    Please provide feedback. I've not received any feedback after two weeks...

  • 0 in reply to Fredrik35148
    TI__Genius 9775 points

    Hi Fredrik.  I'm working to get an answer from our ROM expert.

  • 0
    TI__Guru 66120 points

    Fredrik

    There is a timeout mechanism inside bootloader for the UART, DSP will check the UART IRQ status for both transmitter or rececing. if nothing is detected withing certain mount of time, it timeout.

    As for the during of the timeout. I do not hav exactly number, here is the snapshot of the codes before timeout, the DSP is running at 27MHz, you can roughly get a number of the timeout

    do{
    status = ((uartRegs->LSR)&1);
    ++timeOut;
    } while ((!status) && (timeOut < 0x1000000));

    There is not  see a way to reset this timeout.

    just curious, why host can not sent the package with minmum delay?

    Regards

    yihe