I am using IAR with an I-Jet JTAG device working with the TWR-VF65GS10.
If I plug-in the I-Jet into 20-pin JTAG connector J5 and attempt to debug a program, IAR says the CPU is not powered.
This correct, the I-Jet does not supply power to the Vybrid board.
Now I connect a USB cable to the Tower primary board, the Vybrid board powers up and runs its program. The 4 colored LEDs flash in sequence.
If the I-Jet is then connected, IAR still says that the CPU is not powered.
Below are the power values from the EmuDiag program of the I-Jet.
Channel #0 (ITrgPwr): 0uA
Channel #1 (VTrgPwr): 8.058mV
Channel #2 (VTRef): 3281.465mV
Channel #3 (VUser0): 3030.036mV
Channel #4 (VUser1): 3023.589mV
Channel #5 (VUSB5V): 4981.831mV
Reading TWRVF65GS10UG.pdf, section 2.3.1 discusses how to power the TWR-VF65GS10.
Section 2.3.1.2 states "The J19 is fully open and J25 closed in this mode, and the 5V power comes either from the Tower elevator USB connector or the screw terminal,
The J18 state does not matter thanks to the on-board 3.3V DC switch (see section 2.3.1.2) ."
This tells me to remove J19 if I want the TWR-VF65GS10 to be powered from the primary board.
However, IAR debugging still tells me 'CPU did not power up'.
Alternatively,
if I disconnect the USB cable from the primary board and install J6 and enable 'Target Power' in IAR/I-Jet settings, the power LED, D9, is lit, but still I get 'CPU did not power up'.
I am using the default jumper settings as documented in the TWR-VF65GS10 Quick Start Guide, except as discussed above. (J6 and J25).
If I plug a USB cable into J3, the I-Jet debugger works.
Is it always required that I supply power to J3? If not, what am I doing wrong?
Solved! Go to Solution.
Yes. This works with IAR, but with one small change. The CMSIS DAP setting 'Setup/Reset/Delay After needs to be increased. I set it to 3000ms.
The error one gets is 'CPU did not power on' or something like that. The reason for this error, is the CPU is still booting. The virtual serial port is outputting a lot. The debugger cannot connect until the 'boot sequence' is finished.
Attached is one such boot sequence captured on the virtual serial port.