• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 104 subscribers
  • Views 1573 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux: How to get J6 JTAG ID through another J6?

Chen Changchih
Prodigy 30 points
Other Parts Discussed in Thread: DRA752

Tool/software: Linux

Hello,

How can I get J6 JTag ID  through another J6.

thanks

  • 0
    TI__Guru**** 161600 points
    Moving this to the device forum.

    Best Regards,
    Yordan
  • 0
    TI__Genius 15120 points
    Hi Chen,
    JTAG ID is available in the device TRM. See Table 1-4. ID_CODE .
    JTAG ID is consistent accross device and device revision. It is not needed to be read from every particular device.

    Regards,
    Stan
  • 0 in reply to Stanislav Stilyanov
    Prodigy 30 points
    Hi Stan,

    thanks for you response.
    Because our test platform is to use J6 to verify another J6.

    so I need to get J6 JTAG ID through another J6.
    How can I do , if I want to do that.

    thanks
    Chen
  • 0 in reply to Chen Changchih
    TI__Genius 15120 points

    Chen,

    If you need to verify it is a J6 device, I can recall 2  ways:

    ROM code and UART:

    1. Set your target device to boot from UART (through sys_boot pins).

    2. UART3 is the boot interface. ROM will broadcast ID data on this UART.

    3. Set your probing device to: 115.2 Kbps, 8 bits, even parity, 1 stop-bit, no flow control

    4. Power up your target device. It will continuously transmit the following data (HEX):

    04
    01 05 01 56 41 07 02
    13 02 01 00
    12 15 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    14 21 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

    56h41h means it is J6 device family.

    02h means it is SR1.1 or SR2.0 revision

    UBOOT in a SDCARD and UART:

    1. Make bootable SDCARD

    2. UBOOT bootloader will start with the following device data (transmitted over UART3):


    U-Boot SPL 2015.07 (Feb 12 2016 - 16:29:11)
    DRA752 ES1.1
    reading args
    spl_load_image_fat_os: error reading image args, err - -1
    reading u-boot.img
    reading u-boot.img
    reading logo.yuv
    i2c_write: error waiting for addr ACK (status=0x116)

    i2c addr not found


    U-Boot 2015.07 (Feb 12 2016 - 16:29:11 +0200)

    CPU  : DRA752 ES1.1
    Board: BeagleBoard x15
    I2C:   ready
    DRAM:  2 GiB
    MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1

    Other ways would involve loading your custom code to the target board.

    Hope this helps,

    Regards,

    Stan

  • 0 in reply to Stanislav Stilyanov
    Prodigy 30 points
    Hi Stan

    Thanks for your suggestion!!

    Chen
  • 0 in reply to Stanislav Stilyanov
    Genius 3440 points
    Hi Stan,

    We want to verify if JTAG interface of J6 is good. Does it mean that JTAG interface of J6 is good if JTAG ID can be read successfully? Or we just can verify JTAG interface of J6 by JTAG boundary-scan?
    Thanks for your support.

    Regards,
    Shawn
  • 0 in reply to shawn lin
    TI__Genius 13175 points
    ,

    There are several ways to go to verify JTAG interface is good. I wouldn't be settled by just reading JTAG ID successfully. So you can(and should) do boundary-scan test. You can try test connecting to all cores in CCS when you do a new target configuration (there is a test button). You can start a debug session in CCS connect to cores one by one and see if registers/memory regions are all accessible which will verify JTAG TAP port pipes are clean. In fact you can do all these just to be sure.

    Hope it helps,

    Thanks,
    Alex
  • 0 in reply to Alex Bashkov
    Genius 3440 points
    Hi Alex,

    It is helpful. Thanks for your reply.

    Regards,
    Shawn