Announcements

Robots are revolutionizing our lives in many ways. Join our webinar to learn about Infineon’s broad portfolio of robot building blocks.
Click here to register.

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

AURIX™ Forum Discussions

Mmmmmm
Level 3
Level 3
25 sign-ins 25 replies posted First like given

after lbist the expected value of STMEM4 is 0x1 but the actual value is 0x401 ( tc39 BB )

0 Likes
7 Replies
Jeremy_Zhou
Moderator
Moderator
Moderator
10 solutions authored 10 likes given 100 replies posted

Hi @Mmmmmm ,
Thank you for your interest in Infineon Semiconductor products and for the opportunity to serve you.
Actually, I'm not clear with your question, can you clarify it again?
BR,
Jeremy

0 Likes

after lbist expected value of STMEM4 is 0x1 but when i try the value of STMEM4 is 0x401 problem in bit 10 which reserved bit by 0 but at actual it's value is 1

Screenshot 2023-03-13 044142.png

0 Likes
Jeremy_Zhou
Moderator
Moderator
Moderator
10 solutions authored 10 likes given 100 replies posted

Hi @Mmmmmm ,
Thank you for your clarification.
I use the TC397 Tri-Board for testing, and I find the STMEM4 is 0x0000_0001 after the reset event arises.
Just as the figure shows, so I was wondering if you can list the steps you tested.

2023-03-13_17h07_01.png
BR,
Jeremy

0 Likes

Before trigger lbist value is 0x1 

After trigger lbist value change to 0x401 

0 Likes
Jeremy_Zhou
Moderator
Moderator
Moderator
10 solutions authored 10 likes given 100 replies posted

Hi
Whether you mean the value of STMEM4 is 0x0000_0001, after executing the LIBIST evaluation, it becomes 0x401, is my understanding right?

Jeremy_Zhou_0-1678870370566.png

BR,
Jeremy

0 Likes

Yes exactly 

0 Likes
Jeremy_Zhou
Moderator
Moderator
Moderator
10 solutions authored 10 likes given 100 replies posted

Hi @Mmmmmm ,

What IDE and demo code did you use? as I've not replicated the phenomenon when using the Aurix Development Studio and Infineon's AURIX demos.

BR,

Jeremy

 

0 Likes
This widget could not be displayed.