XDS100 ON MY CUSTOM BOARD..WINDOWS CODE 43 ISSUE..USB DEVICE NOT RECOGNISED

Hi,

Did you program the EEPROM of the FTDI chip?

You'll get the eeprom file here in MProg directory: http://processors.wiki.ti.com/index.php/XDS100#Q:_Where_can_I_get_the_design_.2F_schematic_.2F_BOM_for_the_XDS100v2.3F

Refer this:

http://processors.wiki.ti.com/index.php/XDS100#Q:_Ok.2C_I_built_an_XDS100.2C_but_how_do_I_program_the_EEPROM_for_manufacturing.3F

Regards,

Gautam

Hi Gautam,

                     Thank you for the reply. I have programmed  eeprom and now when i connect the board to pc. it recognizes the board as if the development board is recognizes. But now i am not able to connect to the code composer studio. When i debug and try to conect to ccs. The following error occur.

Error connecting to the target:
Error 0x00001200/-1135
Error during: OCS, Target,
Unrecoverable emulation error

Please help me as i am not able to move forward.

Regards,

JAYENDRA TEJA

Hi,

I hope you've selected XDS100v2 as your emulator in the target configuration. Else,

The connection may be failing for several reasons, including a hardware problem; the page below explains how to use the low-level connect utility dbgjtag, which is useful to rule out any CCS issues.

http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems

Regards,

Gautam

Hi,

I have checked my board with an external emulator it works fine (JTAG SCAN Tests are succeeded and i am able to dump my code ). So i am now clear that the problem is not with emulator Pins. So it is an issue with FTDI chip. I am able to dump the contents of EEPROM and my custom board is being recognized as if the development card is recognized. But am not able to dump the code.

The following error is occuring

is this an issue due to FTDI chip not being configured properly for MPSSE. How can i do it? Please give your thoughts.

Regards,

JAYENDRA TEJA K

Hi,

I have verified my board using External emulator and it works fine. (JTAG SCAN successful and i am able to dump my code). So now i am clear that the problem is not with my emulator pins and with FTDI chip on board. But i am able to program EEPROM and my custom card is being recognized as if the Development board is recognized. But i am not able to dump code. Is it some thing to do with FTDI chip (keeping it in MPSSE mode) or The contents of EEPROM. The following error occurs when i try to dump the code

C28xx: Error connecting to the target: Error 0x00001200/-1135 Error during: OCS, Target,  Unrecoverable emulation error

Regards,

JAYENDRA TEJA K

Hello,

What are you using to program your FTDI chip's EEPROM?

In general, Gautam's comments relate to the FT2232H-based xds100v2.  However, your on-board emulator appears to be based on the FT2232D-based xds100v1.

To program this FTDI FT2232D chip's EEPROM I would consult the following page:
http://e2e.ti.com/support/microcontrollers/c2000/f/171/t/21086.aspx

As mentioned in the above thread, Windows should recognize a TI XDS100 Channel A and TI XDS100 Channel B if everything is done correctly.  Can you let us know if this is happening?


Thank you,
Brett

Hi Brett,

              I have read the contents used in TMDSPREX28335 using Mprog utility and replicated the same .ept file on my board. The board  is being recognized as the development board works. Please find the screenshot of my device manager.

and my board works with the emulator on development card. So bad processor, supply issues, emulator pins issues (pull up';s and pull down's ) can be ruled out.

It is something between FTDI and emulator pins.

Please find the .xml file i am using for programming eeprom.

Thank you,

JAYENDRA TEJA

Hello,

You did not post the image you meant to attach from device manager.  (if correct, device manager should look something like the fifth image in the following post: http://e2e.ti.com/support/microcontrollers/c2000/f/171/t/21086.aspx).  However, based on what you are saying you believe this to be correct.

If device manager is correct then the connection between windows and the FTDI is correct + the FTDI is being powered correctly. In addition, if an external emulator works on your board's J4 the routing between JTAG and the processor is correct and everything is powered correctly + the MCU's support circuitry is working.  This leaves:
1) the connection between CCS and the FTDI Windows driver
2) the very minimal amount of routing between the FTDI chip and the JTAG header

I would suspect [1].  What version of CCS are you running?  What is CCS's target configuration (it should be xds100v1 and F28335)?  If you are using CCSv5, what happens if you click 'Test Connection' in the target configuration window?

My other thought might be to reprogram the FTDI chip as described in the post below.  I have seen occasionally that Windows doesn't recognize the driver as it should.  I don't believe this will resolve your issue, but just in case...:
http://e2e.ti.com/support/microcontrollers/c2000/f/171/t/21086.aspx


Thank you,
Brett

Hello,

         I have found that i am not getting TCK signal to my custom board when i run a test connection from CCS. My debug process went something like this.

1)First i connected the TI development board and recorded the activity on TDI,TDO,TRSTn,TCK signals. The following image gives the activity

Yellow -TDI , Green -TRSTn,  Pink -TDO, Blue -TCK.. TCK doesn't look good bcoz of low sampling. actual TCK looked like square wave with frequency of  1 MHZ. Below is the picture of clock

2) On my custom board it looked like this

So i was not getting clk.

When i checked that properly FTDI chip TCK was not soldered properly when i tried to do it i broke the pin of FTDI chip. I ordered a new one. Will that solve the problem?

Can i give a external clock to check that? and one more thing is that the emulator is XDS100V2 because we use the development board like that.

Regards,

JAYENDRA TEJA K

Hello,

I cannot tell if replacing the chip will fix things or not, but you now need to do it regardless because the FTDI chip broke.  I just tried to see what Test Connection actually does to the JTAG signals on my xds100v1-based development kit.  With my setup I see similar activity to your second screenshot.  When I try to connect to the MCU, TCK does attempt to provide clocks though.

I wouldn't recommend providing your own TCK via function generator, etc.  Instead I'd wait for the new FTDI chip.

In general, if an xds100 emulator is based on the FT2232D it is a xds100v1 and should be programmed and treated as one.  If it is based on the FT2232H then it is a xds100v2.  In the last post I said that you are using xds100v1.  The got this feeling because the attachment in your first post, which I assumed to be from your custom board,  shows an emulator with a FT2232D. 

My belief is still that the root cause issue (that started this thread) comes from CCS/drivers.

Let me know what you think...


Thank you,
Brett