Content originally posted in LPCWare by MarcVonWindscooting on Mon Oct 20 09:24:54 MST 2014
@capiman:Many thanks for pointing me to this thread!
From my experience with mxli: you need the sudo, probably, because as a normal user, you're not allowed to access /dev/ttyUSB0 (owner: root, group: uucp on my machine, for example). So I suggest adding your regular user to the group 'uucp' or whatever group /dev/ttyUSB0 is
assigned to.
About LPC11U67. User manual states the following:
ISP handler uses RAM 0x1000_017C .. 0x1000_025B
That means: 0x200 bytes are NOT sufficient. mxli will overwrite the ISP area => crash!
Use 0x25C bytes at least (round to a word boundary - which is already the case)
Likewise: the flash commands use the top 32 bytes of RAM and a stack of up to 256 bytes is used from that point downwards.
No comes the question: what the hell is the top of RAM? 0x1000_0000 + 16ki -1 ? 0x2000_0000 +2ki -1 ? 0x2000_4000 +2ki -1 ?
If in doubt (I am in doubt) don't tell mxli about the additional RAM regions and assume the worst:
Only the 0x1000_0000 .. 0x1000_4000 (16k region is usable)
-M4ki@0x1000_0000
and subtract ISP demands from bottom and top:
-R 0x25C@0x1000_0000,-0x120@0x1000_0000
Hope this helps.
Sorry for LPC17 failing, this is a bug of my 3.0 release, because I included bad data into the compiled-in table. 3.1 catches this kind of problem in device information.