Write failed - Error -2 or error #4

[istlf]

Hi guys,

 

haven't been working on my Midibox for some time and then i wanted t ostart again and first time i tried transferring my app via MIOS Studio i get the following error which i can't resolve. Have tried with the bootloader switch, but i still can't get it to write. I am getting two error codes (-2 and #4). Can't find anything about either - when trying to set the forum with -2 it doesn't really work..  Anyway, i've uploaded a screenshot of the problems.

 

Weird thing is that it can obviously connect to the Core, see that it is LPC1769 etc. But when i try to transfer app, it fails.

 

Any documentation anywhere of error codes? I can't find them anywhere.

 

 

 

[istlf]

Somebody able to point me in the direction of documentatino of error codes? I can't seem to find it anywhere.

[Hawkeye]

Hmm... it is a quite uncommon thing... maybe something wrong on the core board? I'd suspect maybe some misplaced component somewhere or an unwanted solder bridge, that drops USB voltage, so the flash fails... but... fishing in the dark ;-). Can you measure USB voltage and 3V3 voltage with a voltmeter? Maybe someone else has a better idea! :-)

 

Many greets and good luck!

Peter

[istlf]

I should try that. Will do that when i get back to my workspace.

 

Hmm - i used it for a long time where i flashed it many times and it was working flawlessly. No problems communication with it at that point.

Then i had it standing around for 5-6 months, and then recently i tried working on it again and then this problem..

So i'm thinking it can't be a misplaced component.

 

Will try the voltage checking next time i get a chance and report back.

 

But isn't there some doc. concerning error codes? Will try searching the code repo. when i have a chance of getting it down. Google searching the SVN isn't really helpful.

Edited July 28, 2015 by istlf

[TK.]

Unfortunately not from a user documentation: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Finclude%2Fmios32%2Fmios32_midi.h

 

 

#define MIOS32_MIDI_SYSEX_DISACK_LESS_BYTES_THAN_EXP  0x01
#define MIOS32_MIDI_SYSEX_DISACK_MORE_BYTES_THAN_EXP  0x02
#define MIOS32_MIDI_SYSEX_DISACK_WRONG_CHECKSUM       0x03
#define MIOS32_MIDI_SYSEX_DISACK_WRITE_FAILED         0x04
#define MIOS32_MIDI_SYSEX_DISACK_WRITE_ACCESS         0x05
#define MIOS32_MIDI_SYSEX_DISACK_MIDI_TIMEOUT         0x06
#define MIOS32_MIDI_SYSEX_DISACK_WRONG_DEBUG_CMD      0x07
#define MIOS32_MIDI_SYSEX_DISACK_WRONG_ADDR_RANGE     0x08
#define MIOS32_MIDI_SYSEX_DISACK_ADDR_NOT_ALIGNED     0x09
#define MIOS32_MIDI_SYSEX_DISACK_BS_NOT_AVAILABLE     0x0a
#define MIOS32_MIDI_SYSEX_DISACK_OVERRUN              0x0b
#define MIOS32_MIDI_SYSEX_DISACK_FRAME_ERROR          0x0c
#define MIOS32_MIDI_SYSEX_DISACK_UNKNOWN_QUERY        0x0d
#define MIOS32_MIDI_SYSEX_DISACK_INVALID_COMMAND      0x0e
#define MIOS32_MIDI_SYSEX_DISACK_PROG_ID_NOT_ALLOWED  0x0f
#define MIOS32_MIDI_SYSEX_DISACK_UNSUPPORTED_DEBUG    0x10

 

 

-2 means: more bytes have been received than expected

-4 means: write access (to flash) failed, which is just the result of -2

 

Which MacOS version are you using?

I'm a MacOS user as well, and never got this error code... and I upload code to different core modules very frequently ;-)

 

Best Regards, Thorsten.

[TK.]

Update: the copyright message is originated from 2012 - seems that you missed an important bootloader update!

Last update 2012 was v1.010 (at this time w/o version information displayed in MIOS Studio)

Current version is V1.018 (2014 release)

 

If previously a version before V1.010 was installed, please follow this process: 

 

Best Regards, Thorsten.