Johna Johnson

Hello. Where is the firmware for any PIC24E type of devices please? In the downloaded file that is named PIC24E, it has the bootloader firmware for the PIC24F type. I'm trying to create a bootloader for the dsPIC33Ck types and they are similar to the PIC24E and dsPIC33E devices, but I need some clues in existing PIC24E code. Has anyone written any working firmware for any of the PIC24E or dsPIC33E devices they would like to share? When I create the bootloader for the dsPIC33CK devices I will share...

Hello. Where is the firmware for any PIC24E type of devides please? In the download that is named PIC24E, it has the bootloader for the PIC24F type. I'm trying to crete a bootloader for teh dsPIC33Ck types and they are similar to the PIC24E and dsPIC33E devices, but I need some clues in existing PIC24E code. Has anyone written any working firmware for any of the PIC24E or dsPIC33E devices they would like to share? When I create the bootloader for the dsPIC33CK devices I will share it on the forum....

Sorry for the late reply. Many thanks for the responses, but I re-wrote the Bootlaoder firmware for the PIC18F26K40 device. I converted the firmware to Proton BASIC, so it is easier to understand and simpler to manipulate and alter. The Proton compiler produces extremely compact Asm code and also accepts Asm mnemonics in the BASIC listings. I used an already functional device type (0x6E) and changed the parameters in the ini file for it because I couldn't quite see an empty spot in the over crowded...

Sorry for the late reply. Many thanks for the responses, but I re-wrote the Bootlaoder firmware for the PIC18F26K40 device. I converted the firmware to Proton BASIC, so it is easier to understand and simpler to manipulate and alter. The Proton compiler produces extremely compact Asm code and also accepts Asm mnemonics in the BASIC listings. I used an already functional device type (0x6E) and changed the parameters in the ini file for it because I couldn't quite see an empty spot in the over crowded...

Sorry for the late reply. Many thanks for the responses, but I re-wrote the Bootlaoder firmware for the PIC18F26K40 device. I converted the firmware to Proton BASIC, so it is easier to understand and simpler to manipulate and alter. The Proton compiler produces extremely compact Asm code and also accepts Asm mnemonics in the BASIC listings. I used an already functional device type (0x6E) and changed the parameters in the ini file for it because I couldn't quite see an empty spot in the over crowded...

Sorry for the late reply. Many thanks for the responses, but I re-wrote the Bootlaoder firmware for the PIC18F26K40 device. I converted the firmware to Proton BASIC, so it is easier to understand and simpler to manipulate and alter. The Proton compiler produces extremely compact Asm code and accepts mnemonics in the BASIC listings. I used an already functional device type (0x6E) and changed the parameters in the ini file for it, because I couldn't quite see an empty spot in the over crowded ini file....

Sorry for the late reply. Many thanks for the responses, but I re-wrote the Bootlaoder firmware for the PIC18F26K40 device. I converted the firmware to Proton BASIC, so it is easier to understand and simpler to manipulate and alter. The Proton compiler produces extremely compact Asm code and accepts mnemonics in the BASIC listings. I used an already functional device type (0x6E) and changed the parameters in the ini file for it, because I couldn't quite see an empty spot in the over crowded ini file....

Hello. Has anyone got a firmware for the Tiny Bootloader+ for the PIC18F26K40 or PIC27K40 please? And teh PC app to work with them. I altered the firmware for them, but the PC application does not support them and I tried to use the PIC18F26K42 bits and pieces on the PC application, but it keeps coming back with the error that it will overwrite the bootloader. It has something to do with the on-board eeprom address being different on the PIC18FxxK40 and PIC18FxxK42 devices to standard 18F devices,...