sys64738
/
mspdebug
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
393 Commits 6 Branches 0 Tags 1.4 MiB
Commit Graph

14 Commits

Author SHA1 Message Date
Daniel Beer 07780ff11f Fixed error reporting for Win32. 2011-07-27 01:56:45 +12:00
Daniel Beer a81043a656 Now compiling with MinGW. 
- implemented Win32 serial IO
  - added Winsock init/exit
  - added missing strsep()
  - minor API fixups
 2011-07-27 01:23:16 +12:00
Daniel Beer b8dd765a5b sport: serial IO abstraction layer. 2011-07-27 11:26:02 +12:00
Daniel Beer 75f893ef47 Tidy up long lines. 2011-07-18 15:00:17 +12:00
Daniel Beer a079398f42 flash_bsl: advance address pointer after reads/writes. 
Pointed out by Pierre-Emmanuel Goudet <pe.goudet@watteco.com>.
 2011-04-23 11:57:27 +12:00
Daniel Beer ed2c841da9 Separated device vtables/class information. 2011-03-15 14:56:07 +13:00
Daniel Beer b6e241a9e3 Implemented uniform device constructor functions. 2011-03-15 14:20:06 +13:00
Andrew Armenia 1f7808a78f update flash_bsl for increased erase functionality 
"erase all" seems to be unsupported by the BSL. Only DEVICE_ERASE_MAIN
and DEVICE_ERASE_SEGMENT are therefore implemented. DEVICE_ERASE_ALL
could be implemented, if the addresses of information memory were known.
 2010-12-01 14:29:17 +13:00
Daniel Beer fd98116298 Merge branch 'erase' 2010-10-12 11:00:28 +13:00
Daniel Beer 09813e3129 Fixed BSL memory range checking. 2010-09-25 20:29:38 +12:00
Daniel Beer b9e5db63d5 device: altered erase interface to allow different erase types. 2010-09-23 15:45:06 +12:00
Andrew Armenia aedd5f7691 switched off debugging output in flash_bsl 2010-09-23 13:35:33 +12:00
Andrew Armenia 14404af688 cast CRC test vectors to uint16_t to eliminate warning 2010-09-23 13:35:33 +12:00
Andrew Armenia 89520c052e initial version of flash_bsl driver 
This driver allows mspdebug to talk to the bootloader on a flash MSP430
via a serial port. DTR and RTS lines are used to control the TEST and
RST# pins on the MSP430, respectively. Currently, read and program are
supported. However, read is fairly useless because the driver currently
does not support any password other than the default. Thus it must
mass-erase the chip to gain access.

Read that again. USING THIS DRIVER WILL MASS ERASE YOUR CHIP IMMEDIATELY,
WITHOUT YOU ASKING FOR IT.
 2010-09-23 13:35:33 +12:00