• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 83 subscribers
  • Views 942 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.

CCS/TMS320F28377S: SCI flash-kernel stuck at autobaud

Hasiflo
Prodigy 50 points
Part Number: TMS320F28377S
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

Hi everyone,

I try to use the 'F2837xS_sci_flash_kernel'-example with the LaunchPad TMS320F28377S. 
So i compiled the example from "C:\ti\c2000\C2000Ware_1_00_05_00\device_support\f2837xs\examples\cpu1\F2837xS_sci_flash_kernel"  (with SCI_BOOT for GPIO84,85) and flashed it to the MCU.
I also created the .txt file with:

hex2000.exe -boot -sci8 -a -o f28377s.txt F2837xS_sci_flash_kernel.out

Next I did the same for the Blink example and used following command:

hex2000.exe -boot -sci8 -a -o blinky.txt blinky_cpu01.out

After this I set the 'Boot-Switches' 1 --> ON, 2 --> OFF, 3--> OFF and used following command for connecting via UART:

.\serial_flash_programmer.exe -d f2837xS -k f28377s.txt -a blinky.txt -p COM5

But it get stuck every time at the autobaud-recognition.

So do I have to flash a specific bootloader or an initial-programm to the MCU before performing this command?
Have I set the BOOT-Pins right?
What else could be wrong?

I use the latest C2000Ware_1_00_05_00.

thanks.

  • 0
    TI__Mastermind 32995 points
    Hi,

    What GPIO pins are you using for communication with the SCI bootloader?

    Please make sure that you are using the same GPIO pins that the SCI bootloader boot mode you selected is using. This should fix your problem.

    And then make sure that the kernel you compiled is using those same pins you are using for communication.

    Regards,
    sal
  • 0 in reply to Sal Pezzino
    Prodigy 50 points

    Hi,

    I use the standard pins of the USB-port on the launchpad. This should be pin 84 and pin 85. Therefore I select in the F2837xS_sci_flash_kernel.c 'SCI_BOOT', which is for GPIO84,85.

    So I think this config should be fine.

    Thanks
    Flo

  • 0 in reply to Hasiflo
    TI__Mastermind 32995 points
    If you are physically connecting to 84/85 and booting the device to the SCI boot mode which uses those pins, then it should be working fine.

    Please double check that 1) the pins you are connecting too, 2) the SCI boot mode you selected, and 3) the pins the kernel is compiled to use... are all consistent.

    Hope this helps,
    sal
  • 0 in reply to Sal Pezzino
    Prodigy 50 points

    I think I had identified the problem.
    Something seems to be wrong with the seriel interface.

    For testing I uploaded the "Example_2837xSSci_Echoback.c". This should write the read intput back to the output.
    I choosed other pins (GPIO18 and GPIO19) and changed all to port B in the SCI-config.

    At the beginning of the programm it writes "Hello World" to the SCI.
    What I receive at an USB-to-UART transmitter is following:

    So, I get strange output from the SCI-interface.
    What could here be wrong?
    (I tested this also with the onboard USB of the Launchpad. I get the same result)
    Perhaps something with the UART-Config?

    If I send an 'A' via UART, I got following back:


  • 0 in reply to Hasiflo
    TI__Mastermind 32995 points
    Hi,

    Please make sure your HTerm is configured properly for the SCI communication and also that it prints ASCII characters. It doesn't appear to be printing ASCII characters.

    Once you get echoback working, then this will help you.

    sal