hum, interesting to know. Thanks for your feedback.
hum, interesting to know. Thanks for your feedback.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Hmm i have now also try Microcode studio plus loader and that doesīt work good..
I have loaded the right HEX file with my PICkit2 programmer and then when i try to "Compile and program" i get the message "Please reset the target microcontroller" and when i do that with the MCLR pin nothings happends... then i klick on the close button in the right corner of the window and now microcode loader starts to program the PIC, but i have to try severel times before the PIC works after the programming from the microloader.
It will work all the time if you use their schematic as it add a connection to MCLR and you'll not need to do it yourself... hence why I'd modified my EasyPIC 4 board in the past.
![]()
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
But it should work to reset it manualy.
And when using microloader the programming time is slow.. my small testprogram takes about 6 secounds whit microloader and with Tiny Bootloader it takes "0.249 sec"...
Yup, but MicroCode do more check than Tiny... this is why Microcode firmware is 'round 2.5 time bigger than Tiny.
Sometimes there's a price to pay if you want reliability or speed![]()
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Yes thatīs true.
But with microcode and manual reset i have to program the PIC severel times whit the same program before the PIC starts...
So i think something is wrong.
I will do some more tests and then give you some feedback here.
Why do you sometimes have the define
DEFINE BOOTLOADER_USED 1
Tiny bootloader works with and without this define so i wonder what does the define do?
Bookmarks