• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 79 subscribers
  • Views 545 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSP430FR5043: Uniflash error message

Oba
Genius 17385 points
Part Number: MSP430FR5043
Other Parts Discussed in Thread: UNIFLASH,

Hello,

 

My customer has a question for UniFlash(the latest one, 7.1.0.03976) with MSP430FR5043.

 

When they start the UniFlash session with detected devices configuration.

It showed the below error message.

 

“Can't generate board data file C:\Users\xxx\AppData\Local\TEXASI~1\CCS\TICLOU~1\1\0\BrdDat\ccBoard0.dat An invalid processor ID has been found”

 

Could you tell me the reason of this error?

 

When they start the session with selecting the device manually, this error never show and they can finish FRAM writing without any problem.

 

Regards,

Oba

  • +1
    TI__Genius 13095 points

    Oba,

    Can you check if your customer is seeing the "Can't generate board data" error on the first time they configure UniFlash using the detected device?

    We have a known issue in UniFlash where the second time you configure an MSP430 (ie; Start UniFlash, configure for an MSP430, click on 'New Session' in the menu to go back to configuration page, and configure for an MSP430 again), it will generate an incorrect MSP430 ccxml the second time that requires board data. That issue is already being tracked in our system.

    But if the customer is seeing the issue with the first configuration (ie; Start UniFlash and click on the detected MSP430 device), then it is a different issue. In that case, can you ask the customer to download the ccxml for the working and non-working case by configuring for the device in UniFlash and clicking on the "download ccxml" button in the GUI, and then sending me the generated ccxml files for analysis.

    Thanks,

    Ricky

  • 0 in reply to Ricky Lau
    TI__Genius 17385 points

    Hello Ricky,

    Sorry for my late reaponse.
    We found that the probelm was exactly the same as the knwon problem.

    Thank you very much for your support.

    Regards,
    Oba

  • 0 in reply to Oba
    TI__Genius 17385 points

    Hello Ricky,

    I have an additional quesiton.
    Wil this probelm be fixed on near future update?

    Regards,
    Oba

  • +1 in reply to Oba
    TI__Genius 13095 points

    Oba,

    This bug is not currently tagged for a release at this time, but I have updated the project plan to at least look at the root cause of the problem during this release cycle. After the analysis, if the solution is simple, I can look into including it into the next release (8.0 in July), but if not, I will need to schedule the fix for a future release.

    I'll keep you updated.

    Thanks,

    Ricky

**Attention** This is a public forum