Free Linux FLASH utility: mxli

[lpcware]

Content originally posted in LPCWare by MarcVonWindscooting on Thu Feb 06 16:01:21 MST 2014
Hello Members,

I was a bad boy!
I did not support LPC13xx with my Linux ISP flasher mxli until today, although I supported so many others.
It can be found here: http://www.windscooting.com/softy/mxli.html#Latest

Unfortunately, I've never used an LPC13xx so far. I count on you, providing some feedback!
And I would like to know if you consider this posting inappropriate for the LPCWare forum(s).

I started a PCB a few years ago, but then the project was canceled and two chips disappeared in the drawer. Later I used LPC1100 and LPC800. This is my first excuse, why support for a whole family kept missing from the program. The second excuse is: you could have programmed these chips with mxli anyway, from the first version on, just a little bit less comfortable. Only recently I found out, that people would rather modify the source code than provide a few command-line options. Pity, because that was one of the most important design requirements for mxli  :((

[lpcware]

Content originally posted in LPCWare by starblue on Tue Feb 11 01:48:48 MST 2014

---

Quote: MarcVonWindscooting
I should set the default to 115200 if not lower.

---

115200 8N1 would be a nice default. If I remember correctly all the projects I worked on in recent years used that for their console.

BTW, my test was on a Debian Linux.

[lpcware]

Content originally posted in LPCWare by MarcVonWindscooting on Mon Feb 10 10:21:21 MST 2014
Thanks for your feedback!
Yes, the baud rate is too high for most devices running from IRC, although that should not be a problem with a fractional divider.
I'm not sure if I never managed to use an USB-to-RS232 cable for the high rates, only devices that convert from USB to 3.3V-level RXD/TXD.
I should set the default to 115200 if not lower.

Right now I'm still working on mxli, extending it to LPC43xx with dual bank FLASH. It turned out, the current version cannot flash a dual bank device, because it does not allow to define FLASH memory NOT starting at address 0. I missed that requirement :(

And: mxli needs a detailed man-page with usage examples.

[lpcware]

Content originally posted in LPCWare by starblue on Sat Feb 08 08:22:14 MST 2014
Works for me.

Tested with a simple blinky on an Olimex LPC-P1343 board where I added a MAX3232 on the prototype area, and an FTDI-based USB-serial converter.

The default baud rate of 230400 was too high, 115200 worked.

Maybe -x should be the default?

$ ./mxli -b 115200 -x /home/juergen/git/jstlib/jstlib/targets/olimex_lpc-p1343/examples/blink-delay/build/outputs/olimex_lpc-p1343_blink-delay.hex
Detected: LPC1343, FLASH:32kiB, RAM0:8kiB, RAM1:0kiB, RAM2:0kiB
Image: 668 = 0x00029C Bytes
Transfer RAM: 7kiB+112B @ 0x10000270
Transmission RAM: 7blocks (7kiB), units of 1024B
Flash address range 0x00000000..0x000003ff, sectors: 0..0
Erasing sectors 0 to 0 NOW

Transfer block 0 to RAM (uuencode) ..OK.
Transfer block 0 to FLASH, sector 0 
Started program by system RESET