LAUNCHXL-F28069M: USBVCC - External Supply Seperation Problem

Troodon

Part Number: LAUNCHXL-F28069M

Hello all,

Normally my LaunchXL-F28069M kit works properly with its sci-pc communication when I plug its XDS100V2 usb cable. I can debug programs, write to Flash memory etc.

What I need is to seperate its USBVCC and supply the rest of the kit with an 3.3V external voltage. When I do that, the kit does not work. Its sci communication etc are gone. I can not connect with code composer studio or my other pc interface.

Probably I am on a wrong path.

- I removed JP1 and JP2 jumpers for the isolation.

- I supplied the kit from J9 3.3V and GND connections. I did not connect any other 5V supply etc.

- DIP switches (S1) are H, H, H (as it is before)

- I don't do anything for JP3

- I removed JP6

- JP7 is connected.

I want this kit to be energized with the external 3.3V supply whenever I want and if it is necessary, I want to be able to connect the device with XDS100V2 mini usb cable. When I do that I want to connect the kit either with ccs or with my sci pc interface.

Is this possible and what should I do? Thank you for your attention.

P.S: When JP1 and JP2 are not removed, giving an external 3.3V and USBVCC atthe same time burns its C28 I guess. So this is my 2nd, well actually 3rd kit. The other one is another story. :)

over 4 years ago

0 Troodon over 4 years ago

Intellectual 615 points

Maybe reducing the scope of my question will help me find an answer more easily.

Is it possible to connect to the development kit with Code Composer Studio when I separate the 2 sections by removing the JP1, JP2 and JP5 jumpers and isolate the 2 sections, then feed one side with an external 3.3V power supply and the other side with a usb port? Do I also need to connect an external 5V or make a different connection to connect with Code Composer Studio?

0 Kevin Allen18 over 4 years ago in reply to Troodon

TI__Mastermind 45606 points

Hi Troodon,

Troodon said:
Is it possible to connect to the development kit with Code Composer Studio when I separate the 2 sections by removing the JP1, JP2 and JP5 jumpers and isolate the 2 sections, then feed one side with an external 3.3V power supply and the other side with a usb port? Do I also need to connect an external 5V or make a different connection to connect with Code Composer Studio?

Yes, this should work. No need to provide 5V power.

Does the external power supply you're using show the current? Also are you limiting the current, maybe to 500mA or so? Maybe the F2806x device is getting too little current, or too much if something is wrong.

Best,

Kevin

0 Troodon over 4 years ago in reply to Kevin Allen18

Intellectual 615 points

Hello Kevin,

3.3V supply works with the circuit below.

It does not show the current and I could not measure it with my multimeter but if you mention 500mA current levels, maybe curent is way too little for the kit's requirements.

When energized, after some seconds, D10 blue led becomes active.

This led lights when the temperature has decreased, right?

Thank you.

0 Troodon over 4 years ago in reply to Troodon

Intellectual 615 points

When I try to debug my program, I get the errors below.

C28xx: Failed CPU Reset: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042) 
C28xx: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042) 
C28xx: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042) 
C28xx: GEL: Error while executing OnReset(-1): Target failed to read register ST1
	 at (ST1&~(0x0100)) [f28069.gel:312]
	 at C28x_Mode() [f28069.gel:32]
	 at OnReset(-(1))
C28xx: GEL: Error while executing OnTargetConnect(): Reset failed: retcode=-1
	 at GEL_Reset() [f28069.gel:92]
	 at OnTargetConnect()
C28xx: Flash Programmer: Warning: The configured device (TMS320F28069), does not match the detected device (). Flash Programming operations could be affected. Please consider modifying your target configuration file.
C28xx: Failed CPU Reset: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042) 
C28xx: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042) 
C28xx: Trouble Reading Register ST1: (Error -1137 @ 0x6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042) 
C28xx: GEL: Error while executing OnReset(-1): Target failed to read register ST1
	 at (ST1&~(0x0100)) [f28069.gel:312]
	 at C28x_Mode() [f28069.gel:32]
	 at OnReset(-(1))
C28xx: GEL: Error calling OnPreFileLoaded(): Reset failed: retcode=-1
C28xx: Trouble Writing Memory Block at 0xae0 on Page 1 of Length 0x1: (Error -1137 @ 0xAE1) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042) 
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE0@Data
C28xx: Trouble Writing Memory Block at 0xae1 on Page 1 of Length 0x1: (Error -1137 @ 0xAE2) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042) 
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE1@Data
C28xx: Trouble Writing Memory Block at 0xae2 on Page 1 of Length 0x1: (Error -1137 @ 0xAE3) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042) 
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE2@Data
C28xx: Trouble Writing Memory Block at 0xae3 on Page 1 of Length 0x1: (Error -1137 @ 0xAE4) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042) 
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE3@Data
C28xx: Trouble Writing Memory Block at 0xae4 on Page 1 of Length 0x1: (Error -1137 @ 0xAE5) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042) 
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE4@Data
C28xx: Trouble Writing Memory Block at 0xae5 on Page 1 of Length 0x1: (Error -1137 @ 0xAE6) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042) 
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE5@Data
C28xx: Trouble Writing Memory Block at 0xae6 on Page 1 of Length 0x1: (Error -1137 @ 0xAE7) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042) 
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE6@Data
C28xx: Trouble Writing Memory Block at 0xae7 on Page 1 of Length 0x1: (Error -1137 @ 0xAE8) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042) 
C28xx: Error occurred during flash operation: Target failed to write 0x00000AE7@Data
C28xx: Flash Programmer: Device is locked or not connected. Operation cancelled.
C28xx: File Loader: Memory write failed: Unknown error
C28xx: GEL: File: C:\Users\abc\Desktop\Programming\TI\Inverter.out: Load failed.

When I insist on with "Resume" button, this appears:

C28xx: Can't Run Target CPU: (Error -1137 @ 0xAEF) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042) 
C28xx: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 9.3.0.00042)

Normally while working with usb port, without seperating supplies, I use the command below to reset my sci channel.

    SciaRegs.SCICTL1.bit.SWRESET = 0;
    SciaRegs.SCICTL1.bit.SWRESET = 1;

But now, I don't know how this command behaves. As a result, I can not debug programs for my kit with Code Composer Studio this way.

0 Troodon over 4 years ago in reply to Troodon

Intellectual 615 points

These are the connection test results:

[Start: Texas Instruments XDS100v2 USB Debug Probe]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\elk3\AppData\Local\TEXASI~1\CCS\
ccs1000\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Jan 31 2021'.
The library build time was '20:08:09'.
The library package version is '9.3.0.00042'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[The log-file for the JTAG TCLK output generated from the PLL]----------

There is no hardware for programming the JTAG TCLK frequency.

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

There is no hardware for measuring the JTAG TCLK frequency.

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 64 32-bit words.

The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 38 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 bits.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS100v2 USB Debug Probe]

Actually I think I have some progress. When I seperate 2 sides (by removing J1, J2 and J5), naturally, I don't energize the two parts at the same time. If I give the energy at the same time, there is no problem in the system. The purpose of separating the two sides was to allow the user to connect the usb cable at any time to enable communication.

Two different results are obtained between first energizing the microprocessor side or the XDS100V2 side. In order to eliminate these 2 different results, if I start the system with the S1 DIP switches on wait mode by setting LHL physically and do HHH after energizing both sides. The system does not work normally that way but there just a system clock error. (some interrupt problem: Break at address "0x3f76fc" with no debug information available, or outside of program code.) I could not find how to change DIP switch modes from the inside program (not physically).

Anyway, If I do not change the mode and remain S2 as HHH, if I energize the microprocessor first, then XDS100V2, .out file error appears. But if I energize XDS100V2 first, then the microprocessor, again, only the system clock fault appears.

I need to unplug and plug that usb cable whenever I want so as far as I understand it cannot be done this way. Or, in such a situation, I don't know how effectively you use these 2 parts. Therefore, I think I will have to not separate the 2 sides and include them in the system by powering them only from usb. Because I cannot combine the usb and the system with the external supply, in the slightest short-circuit, the system burns because I do not have enough knowledge on the subject. If I don’t seperate, I can unplug and plug the usb at any time, it does not cause any problems.

Another way is to disconnect the usb's Vcc connection from the board and simply give the com and tx, rx connections. Thus, I do not have to separate the two sections, I can feed the card from J9 and can continue to work with usb whenever I want.

The issue has been resolved for me, thank you.

C2000™︎ microcontrollers

C2000 microcontrollers forum

LAUNCHXL-F28069M: USBVCC - External Supply Seperation Problem