Problem with debugging of the L138

Hi Wolf,

Hope you’re using right target configuration for OMAP-L138.

Which board are you using LCDK, EVM or Custom Board?

Have you set the boot modes to Emulation Debug?

Have you tried using the Sauris SAU510-USB Iso Plus Emulator with other board and succeed in connecting to the target?

Have you tried booting the board with other boot configuration SPI flash or NAND?

Please give me some more information on this

Regards

Antony

Hi Artyom,

There exist a TI wiki page which deals with "Debugging JTAG connectivity problems". Please do check whether it is of any help to resolve your problem.

Regards,

Shankari

-------------------------------------------------------------------------------------------------------

Please click the Verify Answer button on this post if it answers your question.
--------------------------------------------------------------------------------------------------------

Antony Samsunil said:

Hope you’re using right target configuration for OMAP-L138.

Seems to be right.

Which board are you using LCDK, EVM or Custom Board?

I use this board: https://inmyswiki.atlassian.net/wiki/display/SOM/SOM_AM180x+Programming+board

Have you set the boot modes to Emulation Debug?

Yes.

Have you tried using the Sauris SAU510-USB Iso Plus Emulator with other board and succeed in connecting to the target?

Yes, with TMS320. And this was succeed.

Have you tried booting the board with other boot configuration SPI flash or NAND?

No.

Shankari G said:

There exist a TI wiki page which deals with "Debugging JTAG connectivity problems". Please do check whether it is of any help to resolve your problem.

Thanks.

My JTAG emulator works well with TMS320, consequently, it's not a problem with a driver or quality of cables.

I don't know name of phase, at which error is occurred.

I try to manually launch the target configuration and connect to each core individually instead of clicking on the Debug Active Project button. And this occurred the same error, when I press "Connect target" on both ARM and DSP cores.

DBGJTAG I did not try because I can not find Board File.

Hi Artyom,

Have you tested this board earlier or this is the first time you’re testing?

Which emulator option you're selecting from the connection drop down list in the Target configuration? Please check attached the screen shot.

Have checked the test connection option available in the target configuration tab before connecting it to the actual device target? You need to save the target configuration before that . Please check attached the screen shot.

Can you please provide the ccxml target configuration file for cross check?

If you’re testing this board for the first time .please make sure the power supply, clock, reset and JTAG connection are good.

Regards

Antony

Antony Samsunil said:

Have you tested this board earlier or this is the first time you’re testing?

It's a first time.

Which emulator option you're selecting from the connection drop down list in the Target configuration?

I select the "OmapL138" option.

Have checked the test connection option available in the target configuration tab before connecting it to the actual device target? You need to save the target configuration before that .

Button "Test Connection" doesn't active. I save target configuration before that.

Can you please provide the ccxml target configuration file for cross check?

http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/42/4774.OMAPL138.7z

If you’re testing this board for the first time .please make sure the power supply, clock, reset and JTAG connection are good.

Power is Ok. How can I check clock, reset and JTAG connection on the board? 

Hi Artyom,

Hope you’re using the same Emulator (Sauris SAU510-USB Iso Plus Emulator) for connecting other TI device TM320Cxxx by the time have you seen the test connection button is active.

Have you installed the suitable driver for the emulator to support OMAP-L138 Device?

Please check the Windows drivers for SAU510 rev.1.2.1.4. 13-Dec-2012

http://sauris.de/downloads/xds510/sau510-usb_iso_plus_jtag_emulator/

Regards

Antony

Hello, Antony!

Thanks for your help.

Antony Samsunil said:

Hope you’re using the same Emulator (Sauris SAU510-USB Iso Plus Emulator) for connecting other TI device TM320Cxxx by the time have you seen the test connection button is active.

I'm using The same Emulator also for TMS320. And he works fine, but button "Test Connection" is not active.

Have you installed the suitable driver for the emulator to support OMAP-L138 Device?

I have installed the latest version of this driver.

Looks like it's something with my Emulator and his configuration...

Hi Artyom,

We move this to emualtion forum to get the right advice.

Regards

Antony

Hello,

The 'Test Connection' button is not always available for all emulator vendors. However it is common for emulator vendors to provide their own diagnostics software to check the JTAG scan path. If you have one for your emulator, please run them. 

You can also manually run the dbgjtag utility from the command-line. The wiki topic has information on where both utility and board files are:

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

Thanks

ki

Hello!

> C:\ti\ccsv5\ccs_base\common\uscif\dbgjtag.exe -f C:\Users\User\AppData\Local\.TI\693494126\0\0\BrdDat\ccBoard0.dat -rv -S pathlength

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

C:\Users\User\AppData\Local\.TI\693494126\0\0\BrdDat\ccBoard0.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'sm510usb.dll'.
The library build date was 'Apr 1 2013'.
The library build time was '23:55:08'.
The library package version is '5.1.73.0'.
The library component version is '35.34.40.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '1' (0x00000001).
The controller has an insertion length of '16' (0x00000010).
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 software is configured for only TBC features.
The controller is the production TBC (74ACT8990).
The software is configured for only TBC features.
The controller has been hardware reset via its utility logic.
The controller has been software reset via its utility logic.
The controller has been successfully accessed.
The software is configured for slower clock operation.
The controller has a logic ONE on its EMU[0] input pin.
The controller has a logic ONE on its EMU[1] input pin.
The controller will use rising-edge timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '3' (0x0003).
The utility logic has detected a previous power-loss.
The utility logic is not currently detecting a power-loss.

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

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

The test for the JTAG IR instruction path-length failed.
The JTAG IR instruction scan-path is stuck-at-ones.

The test for the JTAG DR bypass path-length failed.
The JTAG DR bypass scan-path is stuck-at-ones.

UPD1:

Just now I successfully connected to the TMDXLCDK138 board over same JTAG emulator.

I do not understand, why the first board is not working.

UPD2:

More detailed explanation:

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.

The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.

---

With the best regards, Artyom.