Development Board Recomendations ???

[HenrikOlsson]

Hi Steve,
Thanks for the offer, I really appreciate it! (hex file sent off list)

For the record:
The hex file is for a 16F877 and compiles to 1502 words.
PICStart+ takes 28 seconds to flash the device.
MCS Bootloader takes ~2seconds to write the code to the device.

Now, I understand that the PICStart+ writes to all memory locations and the bootloader only to the ones actually being used by the program.

Anyway, looking forward to the results, if you can squeese it in - no rush!

And thank you VERY much for the retrofitting details on the EasyPIC4!

/Henrik Olsson.

[mister_e]

with the .HEX you sent me, it's around 10 seconds with the verify option checked. so close to be 3 time faster than PICSTART.

if i remove the verify option... around 5 seconds.

To me the BOOTLOADER option is always handy even using this board. Using the mod i suggested.. it's pretty slick

As i previously said, on some device, the on-board programmer fail for some odd reason, you just need to reprogram the device once again.... this NEVER happen with the bootloader.

[HenrikOlsson]

Steve,
Thanks! That's a lot better than the PICStart+ then....hmm wonder why...never mind. Now I just can't find an excuse not get a EasyPIC4.

Thanks again!

/Henrik Olsson.

[mister_e]

Well i think the explanation is really easy... compare the data transfer capability of the USB against RS232... and PICSTART is still old. I think it's working @9600 baud but i'm not sure of it...

EDIT... ALWAYS handy to have a serial COM port sniffer... PICSTART work @19200 Bauds

Port opened by process "MPLAB.exe" (PID: 2028)

IO Control: 21/02/2007 3:52:36 PM.50064 (+0.0000 seconds)
UP (0x00000000): IOCTL_SERIAL_GET_BAUD_RATE: Retrieve Baud Rate
Baud Rate=19200