Other Parts Discussed in Thread: TMDSCNCD28379D, LAUNCHXL-F28379D
Tool/software:
Programming the image from the TMDSCNCD28379D on the EEPROM using the FT_PROG utility caused two COM ports to become one working one in our first prototype, with the ability to communicate actively. However, in subsequent boards, this did not occur. In order to get the system to appear in the COM ports section, we had to go to the Texas Instruments Debug Probes section and go to properties of either the XDS100 Class Auxiliary or Debug ports, and override the normal device behavior by selecting the Load VCP option. This then allows the use of the XDS100 Class USB Serial Port for deploying built programs to target, but does not allow active communication.
Without this setting enabled on either of the two XDS100 probes, their corresponding COM port does not appear and thus it cannot be programmed as a target.
In either of the two configurations, when the computer tries to connect with the board with an open line of communication after deploying the build, it gives the following error.
