Thanks a lot for the bug fix! I thought it was a problem like this, but I couldn't put my hands on it!
I'll try to post the new release this week-end.
I'm very sorry, but I still don't understand the usefulness of the "Self writing of bootloader" and how it works :-(
Best regards,
Edorul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Use of self-writing is limited, shade for evaluation purposes is strong.
That the bootloader of the current is not corrupted is limited conditions.
You need to create for each device.
You need terminal software.
I will show below some use.
①Temporarily change the operation of the register, such as ports and.
②Temporarily change the serial TXn, the RXn.
③Changing the communication means such as RS232C-> RS458.
It was the previous thread, but it was created because there were also calls for this function.
It is thought to treat it of utility (I wrote it before) is it reasonable as handling, but leave it to you.
Best regards,
Dan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear Edorul.
Thank you measures.
I realized I have to experiment.
Attached is the HEX file for evaluation.
[Affected Devices]
PIC12F1822 (enhanced PIC16F)
[Symptom]
Can not write the EEPROM data that has been placed in the $ F000 in enhanced PIC16F.
The program down.
Can be written when it is included $ 2100 EEPROM data.
[Appropriate version]
V0.8.0
V0.8.1
V0.8.2
Best regards,
Dan
Last edit: Dan 2013-12-09
Hello Dan!
It seems that EEPROM, in "NG.hex" file, is more than 256 bytes (max for PIC12F1822). If, I'm right, this could explain the problem.
Best regards,
Edorul
Dear Edorul.
Thank you very much reply.
I attach the part of the file list.
It might be garbled because the Japanese? include 'KANJI'
NG.HEX file is the one I compiled with PIC16F1823.
EEPROM is using $ FD from $ 00.
It(NG.HEX) has been confirmed that I change to a 'K','B' can be written in v0.7.2.
With EEPROM File ,Do you write in your PIC12F1840?
Best regards,
Dan
Last edit: Dan 2013-12-17
Dear Edorul.
I found a bug.
EEPROM address of B type was not a proper value.
My Changes --> '//@1' and '//@2'
EEPROM is now written by the change.
Best regards,
Dan
Hello Dan!!!
Thanks a lot for the bug fix! I thought it was a problem like this, but I couldn't put my hands on it!
I'll try to post the new release this week-end.
I'm very sorry, but I still don't understand the usefulness of the "Self writing of bootloader" and how it works :-(
Best regards,
Edorul
Dear Edorul.
You say so it's most.
Use of self-writing is limited, shade for evaluation purposes is strong.
That the bootloader of the current is not corrupted is limited conditions.
You need to create for each device.
You need terminal software.
I will show below some use.
①Temporarily change the operation of the register, such as ports and.
②Temporarily change the serial TXn, the RXn.
③Changing the communication means such as RS232C-> RS458.
It was the previous thread, but it was created because there were also calls for this function.
It is thought to treat it of utility (I wrote it before) is it reasonable as handling, but leave it to you.
Best regards,
Dan