great thanks
I also use -Q that exits the programmer when completed
great thanks
I also use -Q that exits the programmer when completed
Steve,
That's great! I've been holding back on buying one because it didn't support the MCS bootloader. I didn't know you could kick that programmer from with in MCS.
Programming a 18F2431 with my PICStart+ takes about a minute, bootloading it takes a couple of seconds, depending on size of code ofcourse. How is the built in programmer speedwise compared to a bootloader or the PICStart for example?
TIA
/Henrik Olsson.
It's actually faster than PICSTART, just send me your .HEX file (in a ZIP) in my e-mail, i'll do the test for you.
BUT YES, you can use the Bootloader as well. The only thing if you don't do a little modification to the board is that you'll need to press on RESET each time. No big deal.
On the other hand, the modification to do is sooooo simple. a SOT-23 n-channel mosfet (or transistor) and a few inch wire is all you need.
It take about 1 minute to modify it... big deal...
- MOSFET gate to DB9 pin 4
- MOSFET drain to the MCLR line (a via can be found close to the E5 capacitor... near the + sign on the bottom side of the board. It's also PIN 7 of the PIC PROG IC)
- MOSFET source to DB9 pin 5
everything fit pretty well on the bottom side. The SOT-23 mosfet have two pin directly soldered on the DB9 pin. Easy easy easy.
Last edited by mister_e; - 21st February 2007 at 19:05.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
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.
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.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
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.
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 baudbut i'm not sure of it...
EDIT... ALWAYS handy to have a serial COM port sniffer... PICSTART work @19200 Bauds
Originally Posted by HHD Software, Serial Monitor
Last edited by mister_e; - 21st February 2007 at 21:56.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Bookmarks