- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
MCU : TC387QP
Debugger : Lauterbach TRACE32 Powerview for AURIX/Tricore
I am trying to trigger LBIST execution and get the LBIST results
Here's what I approached
1) AURIX TC3xx Safety Manual - SMC[SW]:MCU:LBIST_CFG
-> UCB registers , Configuration A, I found these two key words
2) AURIX TC3XX_um_part1_v2.0_xxx
3.1.1.7.5 LBIST execution
If selected in a valid BMHD by LBISTENA=1 (refer to Chapter 3.1.1.6), LBIST execution will be triggered by SSW.
-> follow this manual, I set up UCB,(BMHD0_ORIG/COPY.LBISTENA = 1)
-> As I successfully change this bit field, CRCBMHD and CRCBMHD_N also recalculated as well.
3) I expected LBIST execution start triggered and get the LBIST results by checking LBISTDONE, RSTAT.LBTERM =1,
but it doesn't seem properly operated and finished "LBIST",LBISTDONE, RSTAT.LBTERM still LOW = 0
Could you tell me what I am missing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi baeky
I think you should check LBIST configurations such as LBISTCTRL0, LBISTCTRL1, LBISTCTRL2, LBISTCTRL3.
you can check this parameter at TC38x_appx_um_v2.0.pdf P108.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
thanks for your reply
As I check those parameter with debugger, it seems properly set up already.
<TC38x_appx_um_v2.0.pdf, P109>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The settings seem to be correct.
How do you test it?
Are you testing with Cold Power Reset?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I guess that is the point.
when I powered up the board, It seems to be Warm Power Reset.
other reset, system/application Reset also doesn't trigger SSW.
now I'm looking for how to Cold Power Reset without unstable voltage state.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In my case, I put the Trace32 in Nodebug state and turn the ignition or power on the board off and on.
After that, I attach Trace32 and check it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
as you follow your sequence, "debug port fail" message showed, when I attach Trace32.
something different for my board. 😞
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you do Cold Power-On Reset with NoDebug status before attaching?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yes, I tried it same as you mentioned "In my case, I put the Trace32 in Nodebug state and turn the ignition or power on the board off and on. After that, I attach Trace32 and check it."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Okay... I don't know why such an issue is happening. I am tested normally in the same way...