Question about SIDE
While using the burn button in SIDE to program the EEPROM on a quickstart board I have to reset the board for the program to start running. Is this normal? I am using SIDE version 0.6.10.
I would also like to say a big thank you to all involved in this project and Prop-Gcc.
I would also like to say a big thank you to all involved in this project and Prop-Gcc.

Comments
Yes, it is normal. Maybe it is not intuitive?
I've wondered whether or not the board should be reset after programming. Should it be?
Thanks for the reply. I don't believe I have to manually reset the propeller when using the propeller tool as others have mentioned before me.
Thanks for the reminder. I've added a call to reset the board after burning the EEPROM for the next release.
--Steve
Can I do that by passing -e -r to propeller-load? Honestly I forgot.
There's a DOC for that!
[h=2]Loader Option Details[/h]The command line loader has a built-in syntax help that explains -r and -t and the other parameters. Use propeller-load -h for help. Begin Example C:\>propeller-load -h usage: propeller-load [ -b <type> ] select target board (default is 'default') [ -p <port> ] serial port (default is to auto-detect the port) [ -I <path> ] add a directory to the include path [ -D var=value ] define a board configuration variable [ -e ] write the program into EEPROM [ -r ] run the program after loading [ -s ] write a spin .binary file for use with the Propeller Tool [ -x ] write a .pex binary file for use with the SD loader [ -l ] load the sd loader into either hub memory or EEPROM [ -z ] load the sd cache loader into either hub memory or EEPROM [ -t ] enter terminal mode after running the program [ -t<baud> ] enter terminal mode with a different baud rate [ -q ] quit on the exit sequence (0xff, 0x00, status) <name> elf or spin binary file to loadGood thing I work for free or I'd be pretty annoying!!!
Problem is there are 2 docs for it, and that one is out of date although basically correct. Time to purge and make links to the right stuff.
Sorry I mentioned the PLoadLib option. I forgot that you were just invoking the command line program and don't have access to the internal parameters of PLoadLib directly.