Hi,
I am trying to program DSpic30f6014 using Tinypic bootloader via RS232 port.
Firstly, I loaded the modified bootloader code that is written for dspic30f3012 using MPlab ide. It is successfully loaded. Then I loaded the hex file of basic DSpic30f6014 test code to Tinypic bootloader. Then I write it to DSpic30f6014. It says "transferring hex file successfully". But tinypic bootloader gave a warning: "Hex file for PIC24, dsPIC30 AND dsPIC33 not verified for the moment". Consequently microcontroller does not work as expected.
What may be the problem? Do you have any experience programming DSpic30f6014 using bootloader? Could you please help me?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I attached the file I use for bootloader firmware and the code I am trying to load. I still have the same problem. Could you please find the problem?
Hello Dan,
I can load a programme once via tinybootloader (dspic30f6014). But I still have problems:
1-When I try to load a new program, tinybootloader cannot detect the device.
2-ADC and UART functions does not work. Do I make a mistake about adressing?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1.Please read a flash in the state in which a user program was written once.
[Checkpoint]
(1)Does a reset vector indicate start address of a bootloader?
(2)Isn't the bootloader body rewritten?
(3)Does 4 words of head of the bootloader indicate the head of the user program?
Please load easy application for cutting and dividing of a problem and attach a result.
2-1.The port is changed to a digital port inside the bootloader, so when using ADC, it's necessary to permit use of a AD module by a user program and readjust a digital port in an analog port.
__reset: ;Start of main code label,initial stack pointer = 0x800
BSET PMD1,#ADCMD ;A/D module disable
COM ADPCFG ;All Degital Port
2-2.UART is done prohibited at an exit of a bootloader, so it's necessary to permit use by a user program.
way_to_exit:
clr UxMODE ; deactivate UART
bra first_address
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the solution. I think I solved the problem. I have another question:
-There is a net between MCLR and R2out (also RTS net). Is there a way to eliminate these nets? I wonder if I can use bootloader only using TX and RX nets?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,All
It is the latest firmware.
D-TYPE
PIC24F04KA200
E-TYPE
PIC24FJ64GB002
Last edit: Dan 2014-07-23
Hi,All
I will add PIC24F08KL200.
PIC24F08KL200 does not support PICKIT2,
To rewrite the Device file of PICKIT2, or, must be written in PICKIT3.
Hi Dan !
It's great, thanks a lot :-)
Best regards
Hi,All
Get the PIC16F1704, I confirmed the operation of the beta version.
Result:
Software beta version was work out.
I upgraded from the beta version of the firmware PIC16F1704.
It does not work check for PIC16F1713 and PIC16F1703.
(I think that it will work as it is likely.)
It can write in the PICKIT2 PIC16F170X,PIC16F171X.
Please see attached file for details.
Hi,All
I have updated the firmware.
PIC24F32KA301 and PIC24FV32KA301
D-TYPE
I mistook the D-Type's description.
X
$12, D, PIC24F w/8KB flash & 256B EEPROM, $2C00, 1024, default, default,
$13, D, PIC24F w/8KB flash & 512B EEPROM, $2C00, 2048, default, default,
$14, D, PIC24F w/16KB flash & 512B EEPROM, $5800, 2048, default, default,
$15, D, PIC24F w/32KB flash & 512B EEPROM, $B000, 2048, default, default,
-------------------------------------->
O
$12, D, PIC24F w/8KB flash & 256B EEPROM, $2C00, 256, default, default,
$13, D, PIC24F w/8KB flash & 512B EEPROM, $2C00, 512, default, default,
$14, D, PIC24F w/16KB flash & 512B EEPROM, $5800, 512, default, default,
$15, D, PIC24F w/32KB flash & 512B EEPROM, $B000, 512, default, default,
Hi,All
I found a bug in the firmware of the MSP430.
Content:
If you specify a serial direct connection(Use Direct_TX,Direct_RX),
Level of the start bit is inverted.
Attach the firmware it has been modified.
Hi,All
I have updated the firmware.
ATtiny24A/44A/84A
ATtiny25/45/85
ATtiny261A/461A/861A
I has been reduced code size.
There is no update of the firmware and Devices after this.
Hi,
I am trying to program DSpic30f6014 using Tinypic bootloader via RS232 port.
Firstly, I loaded the modified bootloader code that is written for dspic30f3012 using MPlab ide. It is successfully loaded. Then I loaded the hex file of basic DSpic30f6014 test code to Tinypic bootloader. Then I write it to DSpic30f6014. It says "transferring hex file successfully". But tinypic bootloader gave a warning: "Hex file for PIC24, dsPIC30 AND dsPIC33 not verified for the moment". Consequently microcontroller does not work as expected.
What may be the problem? Do you have any experience programming DSpic30f6014 using bootloader? Could you please help me?
Hi,Erdinc
It does not conduct tests in 6014.
I think 6014 and 3013 are identical to write algorithm of flash,EEPROM,
and operates according to the following changes.
.equ __30f6014, 1
.include "p30f6014.inc"
.equ IdTypePIC, 0x97
.equ max_flash, 0x18000
.equ Fcy, 7372800/4
.equ baud, 19200
.equ PIN_C, 80
.equ CFG,2
.equ UART_CH, 1
You will not be out by removing the check of "Check File" message is the following.
"Warning: Hex files for PIC24, dsPIC30 and dsPIC33 not verified for the moment"
Hello,
I attached the file I use for bootloader firmware and the code I am trying to load. I still have the same problem. Could you please find the problem?
Hi,Erdinc
Does it work with this?
Last edit: Dan 2014-09-18
Hello Dan,
I can load a programme once via tinybootloader (dspic30f6014). But I still have problems:
1-When I try to load a new program, tinybootloader cannot detect the device.
2-ADC and UART functions does not work. Do I make a mistake about adressing?
Hi,Erdinc
1.Please read a flash in the state in which a user program was written once.
[Checkpoint]
(1)Does a reset vector indicate start address of a bootloader?
(2)Isn't the bootloader body rewritten?
(3)Does 4 words of head of the bootloader indicate the head of the user program?
Please load easy application for cutting and dividing of a problem and attach a result.
2-1.The port is changed to a digital port inside the bootloader, so when using ADC, it's necessary to permit use of a AD module by a user program and readjust a digital port in an analog port.
__reset: ;Start of main code label,initial stack pointer = 0x800
BSET PMD1,#ADCMD ;A/D module disable
COM ADPCFG ;All Degital Port
2-2.UART is done prohibited at an exit of a bootloader, so it's necessary to permit use by a user program.
way_to_exit:
clr UxMODE ; deactivate UART
bra first_address
Thanks for the solution. I think I solved the problem. I have another question:
-There is a net between MCLR and R2out (also RTS net). Is there a way to eliminate these nets? I wonder if I can use bootloader only using TX and RX nets?
Hi,Erdinc
A problem seemed to have settled it and was good.
There are 3 ways to correspond with a host only by TX and RX.
1.Not use RTS Reset
2.Use Manual Reset
3.Use Software Reset(It isn't mounted.)
Referring:
http://sourceforge.net/p/tinypicbootload/discussion/requests/thread/4f42a8db/
Best regards,
Dan
Hi Dan,
it works, thanks for your help.
Hi,All
The ATTiny13A firmware I've uploaded.
It was made independent one character receive routine review the code.
And.
18F23K22-43K22-24K22-44K22-25K22-45K22-26K22-46K22
18F65K22-85K22-66K22-86K22-67K22-87K22
18F65K90-85K90-66K90-86K90-67K90-87K90
http://sourceforge.net/p/tinypicbootload/discussion/bug/thread/e9fb6788/
http://sourceforge.net/p/tinypicbootload/discussion/bug/thread/47493507/
--> 2015.01.31.zip
Best regards,
Dan