• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 886 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.

How to use JTAG for BeagleBone White

Duy-Ky Nguyen88210
Expert 2250 points
Other Parts Discussed in Thread: AM3358, AM1808, OMAPL138

Hello,

The original BeagleBone White has on-board JTAG shared with serial port via one USB port using FTDI chip.

I created CCXML file for the board with device AM3358 and had successful test connection.

But I'm NOT able to start debug due to error below

Error connecting to the target:
(Error -1266 @ 0x0)
Device is held in reset. Take the device out of reset, and retry the operation.
(Emulation package 5.1.232.0)

I have years of experience using this tool for AM1808 & OMAP. I can start debugging once I have a successful test connection for the JTAG ONLY IFF I set jumper on my board to DEBUG mode.

What should I do with this BB White !?!?

I'm using CCS-5.5 on Win7 PC

I also add AM335x_beaglebone.gel to the project

  • 0
    TI__Guru**** 393215 points

    Moving this to the CCS forum.

  • 0
    TI__Guru**** 420650 points

    Hi,

    Duy-Ky Nguyen88210 said:
    Error connecting to the target:
    (Error -1266 @ 0x0)
    Device is held in reset. Take the device out of reset, and retry the operation.
    (Emulation package 5.1.232.0)

    So you see this when trying to connect to the A8? Or are you trying to connect to the M3?

    Thanks

    ki

  • 0 in reply to Ki
    Expert 2250 points

    Hi ki,

    I see it after click "Debug". I have the right GEL file for Cortex.

    I'm quite familiar with this process for AM1808/OPMAPL138 for years, it's my daily job for the last 3 years, no problem even with daisy chain of 1 AM1808 and 2 OMAPs.

    But I have problem with this MCU! Is it due to "AWAKE" core ? Should I bypass it ?

    Thanks,

    ~Duy-Ky

  • 0 in reply to Duy-Ky Nguyen88210
    TI__Guru**** 168317 points

    ~Duy-Ky,

    Both AM1808 and OMAPL138 only have a single ARM core, thus the green bug button knows exactly which core it needs to bring from reset and load code.

    As Ki mentioned, the most probable scenario is that the green bug button is trying to connect to both ARM cores of the AM335x device (the Cortex A8 and the Cortex M3). The Cortex A8 is fully operational when the device is powered up, but the Cortex M3 is held in reset until released by either a GEL script or the firmware already running on the Cortex A8 core.

    In this case, make sure to manually launch and connect to the Cortex A8 core before loading code to the target - in other words, do not use the green bug button for this device until you find out what is exactly happening.

    For details on the manual launch, check section 4.2 of the page below:

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

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Expert 2250 points

    Hi Rafael,

    Now I know what it means for the M3_Wakeup. It's just another ARM core, probably to minimize power usage to maximize battery usage in phone, for example.

    As mentioned in previous email, currently I have 1 AM1808 and 2 OMAPL138 in series on my product prototype. So I have 3 ARM cores and 2 DSP cores compared to 2 ARM cores in AM335x. I'm still able to load either all core or only any single core I want, with no problem

    I'm not sure how to launch manually, I thought it's a job of GEL file and my job is expected to load the right GEL to the right place ?!?!

    If I have to launch manually, something goes really quite wrong!!!

    Thanks,

    ~Duy-Ky