Hi, Thanks for sharing this bootloader. For my projects i used the original tini bootloader but now for the 18F66K80 I could not make it run.
In the past my project used the software reset option, (reset codes to send first) So my code receives for example +++ and reboots. This way i can program system physically far from my pc.
Your programming software uses the RTS to reboot, not handy because Hyperterminal makes this high so i have to remove the wire after every time programming.
Can you restore the reset codes to send first option?
gr,
Mark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure I understood your question :-s Because, there never was reset code in TinyBootloader+.
The software reset is in your application firmware?
RTS reset from TinyBootloader+ is annoying you?
If so, you could uncheck "RTS Reset" below "Detected COMs" and then send the reset code from hyperterminal.
Best regards,
Edorul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Old thread, but let me chip in, looks like he wants a software option a set of serial characters can be sent from the windows bootloader software instead of an rts reset. In his program that runs on the PIC if he received those characters he'll call an asm reset which would trigger the bootloader on PIC. Yes that functionality was there in the original tinybootloader pc application.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
During executing application, without using external reset you reset by software.
The following 3 items are considered as a matter of the restrictions of a reset by software.
Application is in the idle state. Or you can shift in the idle state promptly at the time of cord reception.
A cord can always be received using polling and interruption at the time of application behavior.
The PIC16F is unapplied because there are no software resets.
It's mounted on your comment and Tiny Pic Bootloader from V1.7.
1.7(Oct.2004)
- any COM port (just write: COMx in the COM box)
- any baud rate (just write another baud in the BaudRate box)
- can write a hex file name in the (real) command line => auto. write that file
- RecentlyUsedList
- variable "search delay"
- an option to increase the wait time for a response from PIC after each command;
- user selectable codes to be sent before searching for bootloader
(eg. to perform a remote reset)
- option to pulse RTS line for software trigered reset
- selectable PC identifier (other than C1h)
- fix final RCSTA bank
- fix for picbasic (don't forget to add the directive: "Define LOADER_USED 1")
- minor modification for trayicon: RightClick->show/hide DoubleLeftClick->Write
(useful for writing without showing main window)
- save position&size&settings
- included some .asm files with modifications for 16F873, 16F88
I am using the 18F66K80 and used the bootloader lots of times. Sometimes is works the first time but most times it fails after a few seconds, Timeout or no response. To program i have to connect the RTS, and back to Hyperterminal disconnect TRS. It is possible to use the old tiny bootloader (with the reset code to send first). Only when it fails i cannot call the bootloader again. You can use the old bootloader when in the tinyboot.asm in the mainloop the 'C' is replaced by a 'K'
movlw 'C' ; "-Everything OK, ready and waiting."
Anyone with a good working tinybld18F66K80_int16MHz_38400 ?
I have done many projects with the old tinybootlaoder and never ever a problem with uploading.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've tried to port the reset remote option to TinyBootloader+.
Can you test the attached version?
To activate the reset remote option: you'll have to put your string in the "Remote Message" textbox situated in the "Configuration" tab, and then select "Remote signal" in the "Reset Option" groupbox.
I am using the 18F66K80 with some modified code see attachment. Sometime it works for serval days without problems multiple uploads a day. Some time i have to try 5 times, the bootloader responses with:
no answer
ERROR: problem in writing flash memory!!!
It is running on internal oscillator. Nearly all of the IO of the PIC are used. There many good quality X7R's on the power supply. Bootloader using 38400 baud.
Is there any external influence i forgot? incoming IRQ's during programming?
How can i debug this problem? I'm not sure of the circuit board (two pieces react the same) and i'm not sure of my modified asm file
But, I've made a modification: instead of a string, the user must put the decimal ASCII codes separated by space in the "Remote message" textbox (for example your signal +++ will be 43 43 43). This method should be more flexible for different users (like the original TinyBootloader).
Can you try the attached latest version? (sorry for the annoyance)
Hi, Thanks for sharing this bootloader. For my projects i used the original tini bootloader but now for the 18F66K80 I could not make it run.
In the past my project used the software reset option, (reset codes to send first) So my code receives for example +++ and reboots. This way i can program system physically far from my pc.
Your programming software uses the RTS to reboot, not handy because Hyperterminal makes this high so i have to remove the wire after every time programming.
Can you restore the reset codes to send first option?
gr,
Mark
Hello !
I'm not sure I understood your question :-s Because, there never was reset code in TinyBootloader+.
The software reset is in your application firmware?
RTS reset from TinyBootloader+ is annoying you?
If so, you could uncheck "RTS Reset" below "Detected COMs" and then send the reset code from hyperterminal.
Best regards,
Edorul
Old thread, but let me chip in, looks like he wants a software option a set of serial characters can be sent from the windows bootloader software instead of an rts reset. In his program that runs on the PIC if he received those characters he'll call an asm reset which would trigger the bootloader on PIC. Yes that functionality was there in the original tinybootloader pc application.
Hi,Sunish
Thank you very much for your valuable opinion.
During executing application, without using external reset you reset by software.
The following 3 items are considered as a matter of the restrictions of a reset by software.
It's mounted on your comment and Tiny Pic Bootloader from V1.7.
1.7(Oct.2004)
- any COM port (just write: COMx in the COM box)
- any baud rate (just write another baud in the BaudRate box)
- can write a hex file name in the (real) command line => auto. write that file
- RecentlyUsedList
- variable "search delay"
- an option to increase the wait time for a response from PIC after each command;
- user selectable codes to be sent before searching for bootloader
(eg. to perform a remote reset)
- option to pulse RTS line for software trigered reset
- selectable PC identifier (other than C1h)
- fix final RCSTA bank
- fix for picbasic (don't forget to add the directive: "Define LOADER_USED 1")
- minor modification for trayicon: RightClick->show/hide DoubleLeftClick->Write
(useful for writing without showing main window)
- save position&size&settings
- included some .asm files with modifications for 16F873, 16F88
Best regards,
Dan
Last edit: Dan 2014-12-12
Hi,
Yes that is the option i want.
I am using the 18F66K80 and used the bootloader lots of times. Sometimes is works the first time but most times it fails after a few seconds, Timeout or no response. To program i have to connect the RTS, and back to Hyperterminal disconnect TRS. It is possible to use the old tiny bootloader (with the reset code to send first). Only when it fails i cannot call the bootloader again. You can use the old bootloader when in the tinyboot.asm in the mainloop the 'C' is replaced by a 'K'
movlw 'C' ; "-Everything OK, ready and waiting."
Anyone with a good working tinybld18F66K80_int16MHz_38400 ?
I have done many projects with the old tinybootlaoder and never ever a problem with uploading.
Hello Mark,
I've tried to port the reset remote option to TinyBootloader+.
Can you test the attached version?
To activate the reset remote option: you'll have to put your string in the "Remote Message" textbox situated in the "Configuration" tab, and then select "Remote signal" in the "Reset Option" groupbox.
Best regards,
Edorul
Thank you very much! It works great!
I am using the 18F66K80 with some modified code see attachment. Sometime it works for serval days without problems multiple uploads a day. Some time i have to try 5 times, the bootloader responses with:
no answer
ERROR: problem in writing flash memory!!!
It is running on internal oscillator. Nearly all of the IO of the PIC are used. There many good quality X7R's on the power supply. Bootloader using 38400 baud.
Is there any external influence i forgot? incoming IRQ's during programming?
How can i debug this problem? I'm not sure of the circuit board (two pieces react the same) and i'm not sure of my modified asm file
Mark
Hi,Mark
Even if it's compiled by "Generate absolute code", does an error occur?
Best regards,
Dan
Hello Mark,
I'm glad to see the "remote reset" works fine :-)
But, I've made a modification: instead of a string, the user must put the decimal ASCII codes separated by space in the "Remote message" textbox (for example your signal +++ will be 43 43 43). This method should be more flexible for different users (like the original TinyBootloader).
Can you try the attached latest version? (sorry for the annoyance)
Best regards,
Edorul
It works as aspected, at the massage tab I still see the character instead of the asci code, no problem for me.
Mark
Hello Mark,
Thanks a lot for the feedback!!!
In the message tab, I think I should display the ASCII code and the characters.
Best regards,
Edorul