• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 16 subscribers
  • Views 402 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.

RF430FRL153H: flash programming problems

Martin Tsai61
Prodigy 185 points
Part Number: RF430FRL153H

We are a third party flash programming tool maker.

1. Now we are referring to SLAU603B(RF430FRL15xH Firmware User's Guide) It says that you need to write 0x39 to the JTAG Enable Password Register to enter JTAG mode, but how do we write 0x39 before we enter jtag mode?

 

2. There's JTAG signature address in SLAS834(RF430FRL15xH NFC ISO 15693 Sensor Transponder) but it doesn’t suggest what the Lock and Unlock values are.

Is it the same as MSP430F where 0x00000000 & 0xFFFFFFFF are Unlock and other values are Lock(SLAU445H doc)?

3. Referring to SLAU320 1.4.3 Testing for a Successfully Protected Device , it means protection is valid when TDI outputs 0xAAAA and then TDO receives 0x5555. And referring to 1.3.2.2.1 Taking the CPU Under JTAG Control, we received  a JTAG ID of 0x95(we are not sure if this is correct), and then Bit9 of TDO word won't change to 1 and we have been stuck on this. Is there anything we missed or is this related to my first two questions?

Thanks for your help!

Ryan

overseas@leap.com.tw

  • 0
    TI__Guru*** 128235 points
    Hello Martin,

    I believe your question is related to this thread: e2e.ti.com/.../2655589

    I have answered question 1 there already.

    For question 2, I don't think the device would deviate from that so please try that approach.

    For question 3, I don't understand enough about the question to really comment.

    We aren't really geared to support JTAG questions at this level... our expertise is with RF. We've never in all the years of supporting this device have dealt with such questions. All other users have had no issues using JTAG correctly.

    I think the issue at hand is that developing a Flash Programming tool is more advanced than typical JTAG applications, so it goes beyond our knowledge and very frankly, beyond what we have any interest in supporting because we have working Flash Programming tools used by all of our customers.