• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 78 subscribers
  • Views 982 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.

MSP430F5419A: During programming I'm getting intermittent Exit: 59 Could not write device memory

Ernie Seubert
Prodigy 10 points
Part Number: MSP430F5419A
Other Parts Discussed in Thread: MSP-FET, , UNIFLASH

Sometimes this works and other times I get the ERROR 59. My computer is Windows 7.  Using an MSP-FET tool.

This is what I'm running at the command prompt:

c:\ti\mspflasher_1.3.20\msp430flasher.exe -i COM10 -n "msp430F5419a" -w "c:\cdc_test_sw\pad5_MB_MP_MT_0_0_10.a43" -v

This is the result when failing:

MSP Flasher v1.3.20
Evaluating triggers...done
Checking for available FET debuggers:
Found USB FET @COM10 <-Selected

Initializing interface @ COM10...done
Checking firmware compatibility:
FET firmware is up to date.
Reading FW version...done
Setting VCC to 3000 mV...done
Accessing device...done
Reading device information...done
Loading file into device...
Exit: 59
ERROR: Could not write device memory
Powering down...done       Disconnecting from device...done

Driver :closed

  • 0
    TI__Guru 68141 points

    Hi Ernie,

    Not sure why you are seeing this error.  Have you tried using Uniflash?  I'm curious if you will see same.

  • 0 in reply to Dennis Lehman
    Prodigy 10 points

    I have not tried the Uniflash. I was using an MSP-FET430UIF unit before this one with no problems.

  • 0
    Prodigy 10 points

    I ran uniflash.  Passed 3 out of 4 tries.  This is the error received:

    [ERROR] MSP430: Trouble Writing Memory Block at 0x62da on page 0 of Length 0x2e4e: Could not write device memory.

  • 0
    Prodigy 10 points

    Looked at the location in our code that was failing and this is what we had:

    :1062C000090909090908080808080808070707074D
    :0962D00007070707070707070786
    :1062DA003140005C3C40001C3D401906B013A08FC1\

    We saw that the Uniflash program was hesitating at address 0x62DA.  Looking in the file we saw that a byte was missing so we put in an FF.

    :1062C000090909090908080808080808070707074D
    :0A62D000070707070707070707FF86
    :1062DA003140005C3C40001C3D401906B013A08FC1

    Uniflash does not hesitate at this address anymore and have not had any failures yet.  I do not know why we never had this problem our older programmer (MSP-FET430UIF)

  • 0 in reply to Ernie Seubert
    TI__Guru 68141 points

    Hi Ernie,

    So you are saying that the output file you are using to program the target is not supposed to have FF, but when you edited and inserted FF it now works???

    I believe the error "cannot write device  memory"  is actually coming from the msp430 dll (MSP debug stack API) that MSP430Flasher and Uniflash use to control the MSP-FET HW.

    What is your status now?  Do you still need help?

  • 0
    Prodigy 10 points

    Hi Dennis,

    That is correct.  I do not need the FF to run properly but it looks like it is needed to do the programming.  We were thinking the same thing about the DLL.

    I did the programming 10 times without any error.  Before I would get 2 to 4 fails out of 10 tries.  I was going to put this in my test program and run it today just to make sure there is no problem.  I'm pretty sure this will work so I think I'm good.

    Thanks for suggesting Uniflash as that gave us the exact location to look at.   

**Attention** This is a public forum