VSCP Bootloader wizzard

Back to HowTo's

 rev 0.32.0:  2004

Setup program for win32 - http://www.vscp.org/download/setup4vscpboot020.exe

The VSCP application is a simple wizard to boot load a node in a VSCP environment. It should be no problem to adopt it for your own needs. It is written in C++ and uses the wxWidgets library to be portable to other platforms. The source is in the VSCP source distribution or in the VSCP CVS. You need to have the CANAL service started or at least have one CANAL driver available to be able to use the application. If you need to design your own CANAL driver please check the CANAL documentation on how to do so. This is a very easy task.

Start the vscpboot.exe application wizard. The welcome screen will be displayed.

Press Next to move forward

Select the interface you want to communicate through. It is faster to go directly through a driver then to use the CANAL daemon. If the listbox is blank you need to install CANAL and/or one or more CANAL drivers. See the documentation for CANAL on how to do this.

This screen tells how the input file is interpreted and loaded. The input file should be a standard Intel Hex file. When you press next you are asked to select the file and load it. If everything is OK with the file the next screen will be shown.

Here you have the ability to choose which areas should be loaded. You can also change the address range. If you try to load data into the boot sector a warning will be issued. Also to write configuration bits is very dangerous. Likewise for VSCP nodes it is not good to write to EEPROM memory. In boot cases you should know what you are doing and understand that you can end up with a node that does not work if you write the wrong information to the wrong place.

On this screen you choose the nodes you want to load data to.

This is the last screen before the actual boot loading process starts. Just press next and wait until the code has been loaded. If everything goes well the node will reboot with the new code and start the new application firmware.