Help with Warnings Messages

[William Roth]

TinyMultibootloader+ (Ver0.11.0_
Compiler: Great Cow Basic Ver .95.06
Chip PIC 16F1829

The program seems to run ok after flashing the chip.

However, the following warnings are returned when flashing.
Warning: Config found just writing data
Warning: Config found just writing data
Warning: Config found just writing data
Warning: Config found just writing data

WARNING: pclath not fully initialised before GOTO! ...
Code successfully repaired.

I have been told that these are "normal". However it does not seems normal to me to have such warning messages. Well behaved code should not generate errors or warnings.

---

There are 4 warnings regarding "Config found"

Question 1. What is the root cause of these warnings?
Question 2. Why are there 4?
Question 3. How can these warnings be eliminated?

---

---

"PCLATH not fully initalized before GOTO"
Question 4. What does this actually mean?
Question 5. What is the root cause of this warning?

---

---

"Code successfully repaired"

Question 6. What code is broken that needs to be repaired?
Question 7. How is the code "repaired" (Example?)
Question 8. How can this message be eliminated?

---

Thanks

William

[Dan]

Hi,William

Your question was also answered in even before. (This and the last question.)

You are what you need to know has been debated in this forum before asking questions.

In addition, it will also help to understand the operation of the TMBL the following pages.
http://tinypicbootload.sourceforge.net/

Best regards,
Dan

[William Roth]

Thanks for the reply.

I did see a discussion but NEVER any specific or definitive answers.

Pointing me to the manual is not very helpful.

Thanks Anyway

William

[Sunish Issac]

Dear William,
Those warnings are actually sort of debug messages from the bootloader
desktop software. The first config message is because you have set PIC
configuration bits in your code whic is irrelevant as the bootloader
ignores it. You might have a compiler directive in GCB to remove it from
hex file.
Regarding PCLATH, Iam not knowledgeable enough to give details except for
the fact that bootloader on PIC needs to ensure that your code is executed
and located correctly in the program memory. For this the initial jump
should goto bootloader and shouldnt overwrite it.Probably that correction
is done on your code before uploading to PIC.

Code successfully repaired just means its prepared for writing to PIC
without trying to overwrite the bootloader by doing the above mentioned.

I guess Edorul and Dan are not native English speakers and will have a bit
of difficulty in conveying the right message correctly.

Best regards,
Sunish

On Jun 28, 2016 4:30 AM, "William Roth" williamroth@users.sf.net wrote:

Thanks for the reply.

I did see a discussion but NEVER any specific or definitive answers.

Pointing me to the manual is not very helpful.

Thanks Anyway

William

Help with Warnings Messages
https://sourceforge.net/p/tinypicbootload/discussion/help/thread/a9a6d71f/?limit=25#b8bb

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/tinypicbootload/discussion/help/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[Dan]

①
Warning: Config found just writing data
Warning: Config found just writing data
Warning: Config found just writing data
Warning: Config found just writing data

These warnigs do not appear in the following modification.

[first-start-sample.hex] --> [first-start-sample2.hex]

:020000040000FA
:020000000528D1
:100008000900282021008D1222008D166430F2008C
:10001800F30120001A2022008D128430F2000330F0
:10002800F30020001A20082863001828F30A0E306D
:10003800F100BD30F000F00B1F28F10B1D28F20B6A
:100048001B28F30B1B2808002100191799161916ED
:10005800991199179E131D1023008C018D018E0193
:1000680022009313911320008C018D018E0108004A
:020000040001F9
:04000E00A43FFF1EEE 　　<----- Delete This line
:00000001FF

②PCLATH not fully initalized before GOTO

This warning does not appear in the following change.

[first-start-sample.asm] --> [first-start-sample3.asm]

;Vectors
ORG 0
movlw 0 <---------------- Add This line
movwf PCLATH <---------------- Add This line
goto BASPROGRAMSTART
ORG 4
retfie

③Code successfully repaired

You must understand the operation of the figure on the following pages.
Code that is actually written to the source code is different.

http://tinypicbootload.sourceforge.net/pic16_firmwares.html

Best regards,
Dan

Postscript
It does not affect the operation of either of the warning.

[Anobium]

This should work with respect to the GOTO ASM

;Vectors
  ORG 0
  pagesel BASPROGRAMSTART
  goto  BASPROGRAMSTART
  ORG 4
  retfie

The source should be changed to

                else if ((code & 0x3180) == 0x3180) // looking for a goto somewhere
                        pcLath = 2;

I have attached a revised version of the source code with this change. Is this a valid change the functional code?

Also, this source contains a revised stringset. The language is now focused on the user experience, I have removed many spelling mistakes and have improved the use of English.

Anobium

[Anobium]

Latest revision. Improved dialogs and improved handling of the CONFIG condition error.

If these changes are acceptable then I will document.