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.
Champs,
I am asking this for our customer.
We used TI F28379D EVM (TMDSDOCK28379D) and tested C2000ware example code "usb_dev_serial" from
C:\TI\c2000\C2000Ware_1_00_05_00\device_support\f2837xd\examples\cpu1\usb_dev_serial\cpu01
It worked with build configuration CPU1_RAM.
When we tested with build configuration CPU1_FLASH, it worked before powering off the EVM board.
That is, we could see the virtual USB COM port on Windows device manager when running F28379 on CCS after flash programming.
However, when we powered on the board again, that is, by standalone mode (flash boot), it did not work.
That is, we could not find the virtual USB COM port on Windows device manager.
We tested on Windows 10 and 7, and both results were same.
Is there anything wrong that we could not run it by standalone mode (flash boot)?
Wayne Huang
Sal,
I could run another example blinky successfully with standalone mode (flash boot) with the same board so that I did not think there was anything wrong with the TI EVM with default flash boot mode.
C:\TI\c2000\C2000Ware_1_00_05_00\device_support\f2837xd\examples\cpu1\blinky
Why does it matter when the emulator is connected and power cycle it?
But anyway, it fails no matter the emulator is connector or not when we power cycle it.
Wayne
Harshmeet,
Yes, I can run it successfully by either adding “DisableDog();” in the beginning of main() in usb_dev_serial.c or setting “WD_DISABLE .set 1” in F2837xD_CodeStartBranch.asm.
Thank you!
Wayne