Éimear Murphy

It was just the debug messages...working finally! Thank you for your help and patience, really really appreciate it. Re-posting the final .asm file to operate TMBL+ over RS485 on pic18f13k22. There was no changes made to piccodes.ini file. Main changes made to the .asm were for control of RC7 pin which enables transmit and receive to the pic. Some code was removed from the .asm file to allow the pin control changes to be made while keeping the code under 100 words.

Here is piccodes.ini, it is unmodified and allows the blink code to program successfully.

Note also I can get my real application hex code to program via the modified rs485 tbl when I change the piccodes.ini to have a greater max flash value, this and the debug messages that come up suggests to me that the PC software has an issue with the lenth of the real hex code application. However, as you previously pointed out, changing the value of the max flash in the piccodes.ini file messes up the jump vectors in the program memory.

No hex doesn't work. Message tab extended address: 0x0030 -> Configuration Bytes: :03000100681F1E57 0x0001: 68 1F 1E :02000500088170 0x0005: 08 81 :0600080003C003E0034009 0x0008: 03 C0 03 E0 03 40 minMemPos=00000000, maxMemPos=00001F40, blockSize=64 first 4 words at address 0x1F38: 0xEF06 0xF000 0xFFFF 0xFFFF Uploading PROGMEM Uploading program memory write mem pos: 0x00000000(byte) send: TBLPTRU=0x00, TBLPTRH=0x00, TBLPTRL=0x00, block=64 A0 EF 0F F0 FF FF FF FF 10 00 FF FF 0F EC 0F F0 93 9C 8A 8C...

Failure is with adapted code for rs485- but I'm able to program successfully the blink code for with adapted btl rs485. Attched is asm for reference.

I will send you over the real hex via email. This is what I get in the messages tab when I try program the real application code User ID(s) removed from source extended address: 0x0030 -> Configuration Bytes: minMemPos=00000000, maxMemPos=00001F40, blockSize=64 first 4 words at address 0x1F38: 0xEF7C 0xF000 0xFFFF 0xFFFF Uploading PROGMEM Uploading program memory write mem pos: 0x00000000(byte) send: TBLPTRU=0x00, TBLPTRH=0x00, TBLPTRL=0x00, block=64 A0 EF 0F F0 FF FF FF FF 58 82 D9 CF 02 F0 DA CF...

Messages tab when loading blink code is as follows: Checking device Open COM8 serial port at 19200 Baud Rate Hardware RTS resetting device Device answer: 0x61 0x43='C' byte OK, now check ID-code and Family idCode = $61 family = C description = 18F w/8KB flash & 256B EE flash mem = 8192 bytes EEPROM mem = 256 bytes Bootloader size = 200 bytes Transfer block size = 64 bytes Device detected:18F w/8KB flash & 256B EE Closed COM8 serial port TinyMultiBootLoader+ device check completed Checking device...

Hi Anobium, Attached is the program memory without piccodes.ini and the the blink file loader via TBL. The memory is as you say above and I can see the pin toggling on the oscilliscope. There is no changes to piccodes.ini. However, when I try load my real application code, I get an Error on the TBL GUI. Simulating this on a virtual device tells me that my real application code hex file is too large. That is why I'm trying to changes picodes.ini (or make some change) so that my real application code...