MSP430I2031: MSP430I2031 board not detected by EMDC GUI after calibration

Hi,

Have you check your supply voltage of your board? Do you have an EVM for comparison test?

Can this ticket provide help to you?

https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/832762/msp430i2041-hid-bridge-msp-exp430f5529lp-is-not-communicating-with-energy-measurement-design-center-gui-and-energy-meter/3092811?tisearch=e2e-sitesearch&keymatch=EMDC%2520disconnected#3092811

Hi Allen

Thank you for your response.

I checked voltage supply and it is 3.3V and I am getting 1.8 V on Vcore cap.

I don't have EVM. 

I have gone through your suggested ticket. I have already performed many suggested solutions & will perform the rest.

Mentioned Ticket is also not having any logical end.

Thank you!

Hi Devesh,

Have you check that is there anything wrong with your HID board and isolate board? Have you measured the communication signals?

Hi Allen,

Yes I have checked the HID board and isolate board , they are working fine.

In my project i am using esp32 to communicate to MSP430I2031 through UART , ESP32 reads voltage ,current and few energy data every second.

MSP430 was working fine with ESP32 but when I tried to calibrate it something went wrong and now it is not getting detected with EMDC and ESP32.

While calibrating what possible can go wrong?

Hi Allen,

While downloading code into MSP430 through IAR, I noticed that in faulty board (not detecting in EMDC after calibration) I am unable to access Memory, Flash , RAM through Disassemble window.

For more clearity refer below Images : 

And I noticed that buttons ( Go, Next statement , step into etc) which are used for debugging are not active (disabled).

Logs:

Fri May 27, 2022 22:05:33: IAR
Embedded Workbench 7.21.1 (C:\
Program Files (x86)\IAR Systems\
Embedded Workbench 8.5\430\bin\
430proc.dll)
Fri May 27, 2022 22:05:33: Using
license:
Fri May 27, 2022 22:05:34: Firmware
version 3.11.0.1
Fri May 27, 2022 22:05:34: Interface dll
version 3.15.1.1
Fri May 27, 2022 22:05:35: Device :
MSP430I204x_I203x_I202x
Fri May 27, 2022 22:05:35: External
voltage : 0.1 V
Fri May 27, 2022 22:05:35: VCC voltage :
3.3 V
Fri May 27, 2022 22:05:35: Symbol table
loaded.
Fri May 27, 2022 22:05:35: Loaded
debugee: C:\Users\Reet\Desktop\
Smart Plug\Code\Testing_Boards_v0\
src\IAR\Debug\Exe\
Testing_Boards_v0.d43
Fri May 27, 2022 22:05:36: Target reset

Please guide me further for solving this issue.

Thank you!

Hi Devesh,

I want to confirm with you that only this device have the problem? Is this chip still working properly? Have you changed another device for cross test?

Calibration will write some parameters to device. Have you checked the code inside the chip for any anomalies?

Devesh Kumar said:

While downloading code into MSP430 through IAR, I noticed that in faulty board (not detecting in EMDC after calibration) I am unable to access Memory, Flash , RAM through Disassemble window.

Hi Allen,

Devesh Kumar said:

While downloading code into MSP430 through IAR, I noticed that in faulty board (not detecting in EMDC after calibration) I am unable to access Memory, Flash , RAM through Disassemble window.

Today, I was trying to reprogram it and found that when I click "Pause button" ( Red highlighed in below image) , I was able to see all memories in disassembly window.

Here I noticed that the code is starting from

"/* Calibrate REF */

 REFCAL1 = *(TLV_address_for_parse + TLV_CAL_REFCAL1);"

Earlier , It was starting from main().

Now I clicked on Next statement button ( mentioned in RED mark)

I got under mentioned Pop- up.

Can you help me in solving this issue?

Allen Gao said:

I want to confirm with you that only this device have the problem?

No, Now I am facing same issue with 2 boards.

Allen Gao said:

 Is this chip still working properly?

No, it is not working properly.

Devesh Kumar said:

Can you help me in solving this issue?

In a MSP430I2031 the reference calibration data is stored in information memory. Given that your boards are halting in LPM4 in the __low_level_init() function due to an invalid checksum in the reference calibration (TLV) think the issue is somehow that the information memory with the reference calibration got erased.

I don't have the hardware to investigate, but not sure if anyone from TI explain how to resolve the issue without replacing the MSP430I2031.

Hi Devesh,

Like Chester said, if the TLV value in the flash information memory is erased by some mistake that will cause something wrong in the start up code(SUC). The SUC is the _low_level_init() function. The calibration operation will store some calibration value (TLV) which is in the information memory. I just suspect that if there is something wrong when update the calibration value that cause the information memory abnormal. f

Some details you can see in the chapter14 in technical reference manual.

I suggest that you check the information memory. 

Hi Chester and Allen 

Thank you for your valuable response.

Can you please suggest me some solution to recover my chipset?

If the information memory is corrupted/deleted then, If I reprogram my chipset then it should re-write a fresh data in my information memory and but I am getting same error.

Allen Gao said:

Some details you can see in the chapter14 in technical reference manual.

Dint found any technical reference manual, can you please share link?

Hi Devesh,

Here is the TRM link.

https://www.ti.com/lit/ug/slau335a/slau335a.pdf?ts=1654499105165&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FMSP430I2031

The calibration value is still stored in information memory. And the TLV is stored in info memory too. The TLV value is test by ATE test for each device. Calibration will read the information memory and add the calibration value and re-write all the data to info memory(TLV+ calibration value). If the info memory is already erased by user. The calibration operation will read the changed TLV and re-write it to info memory. That is why you calibration with the same error. Because the true TLV is already lost. If you want to recovery the TLV value it will take a lot of efforts. ATE testing is required to test out and rewrite the device specific TLV data for each chip.

Hi Allen

Thank you for your detail informative reply.

Can selecting "Erase main and information memory" lead to the issue which I am facing?

I was having few IC, and now due to global shortage in chip these ICs are not available in the market.

I am ready to put efforts in rewriting the device specific TLV data for each chip.

Please guide me how can I do it.

Thank you!!

Hi Devesh,

Sorry for reply late. I was out of office for two weeks.

The TLV data store in information memory(0x1000-0x13ff) form 0x13C0. If you select eras information memory, it will eras the TLV data. It will cause this issue.

The TLV date is tested of each device before release to market, it is unique. TI has method to recover it , but the cost and efforts is very large. It may exceed a new one.