26 Nov 06: uploaded BLIPS 2.8 to BLIPS in project section. See revision history there.
Nov 10, 2006: mega168 was tested OK, no changes to assembly language code was needed. This fact isn't yet reflected in the comments in the source code uploaded here.
I'm looking for someone to help test the following.
I have implemented an AVR bootloader, PC side, called
"BLIPS" - meaning: Bootstrap Loader for Internet Protocol and Serial (communications)
This PC program is Windows GUI/mouse based, rather than strictly command line based.
BLIPS enables loading and verifying FLASH and EEPROM files in AVR chips that have a bootloader in place in flash. That AVR side follows Atmel's application note 109 protocol.
BLIPS communicates with the AVR chip in the following manners:
1. AVR connected to serial port on same PC as BLIPS runs on.
2. AVR connected to a serial port on a distant PC which has LAN or Internet connectivity to the PC running BLIPS. The freeware called Proxy Serial is used on the distant PC. BLIPS connects to Proxy Serial and the remote AVR using BLIPS' TCP/IP connection option.
3. AVR connected to a distant device rather than a PC, where the device converts ethernet or WiFi to serial. Example devices include Lantronix XPort, Lantronix WiPort (WiFi), Moxa NPort W2150 (WiFi), Digi, and many others. BLIPS uses either UDP or TCP (user's choice) to connect to these kinds of devices.
The testing I've done has used two AVR-side bootloaders. One is in assembly language, fits in 512 bytes; the other is in GCC/C, requires 1024 bytes. The concept is that BLIPS triggers the AVR remotely to go to bootstrap mode by sending two
BLIPS was compiled for Windows 98 and later compatibility. A different version with the WIndows XP look and feel and use of .NET 2.0 is what I'd like to see tested - with chips and flash/eeprom files that try out test cases I cannot do.
Thanks in advance.