Bootloader - new hex -file

Testing/Troubleshooting
1

Hi ,

It’s my first post over here and first of all thanks for this great site;

Now my problem :

I’m gonna build an midibox64 for control TRAKTOR-software throught the RS232-port.

So for the bootloader I have to change the ID device in  ID = 0000000000000100. Correct me if I’m wrong.

But I can’t use ICprog , because my pic programmer (WISP628) doesn’t work with this program.

I use BUMBLEBEE and in the hex-file I have to change the next rule :

200000  00 00 00 00 00 00 00 00 to 200000  00 00 00 00 00 00 01 00 (I thaught this was the correct adres an ID-setting)

And that I can’t , So can someone send me a new hex of the bootloader with the right ID , or give me another suggestion?

Thank

CHRISTOPH

2

Hi Christoph,

does this help?

Patching the .hex file

If your PIC programmer doesn't allow to edit the ID field, it's also possible to patch the .hex file instead.

Just open the .hex file, and search for the line below ":020000040020DA" which begins with :08000000
The following eight bytes (16 digits) are the ID values in hexadecimal format.
The last value is the checksum over these 8 bytes (0 - byte1 - byte2 - ... - byte8)

Here some examples:

Normal ID field (all 8 bytes are zero) - to-COM disabled, MIOS Device ID = 0x00
:080000000000000000000000F8

to-COM disabled, MIOS Device ID = 0x01
:080000000000000000000001F7

to-COM disabled, MIOS Device ID = 0x02
:080000000000000000000002F6

to-COM disabled, MIOS Device ID = 0x03
:080000000000000000000003F5


to-COM disabled, MIOS Device ID = 0x00, KS0108 GLCD driver (1)
:080000000000000000001000E8

to-COM disabled, MIOS Device ID = 0x00, custom LCD driver (7)
:08000000000000000000700088


to-COM enabled, MIOS Device ID = 0x00
:080000000000000000000100F7

to-COM enabled, MIOS Device ID = 0x01
:080000000000000000000101F6

to-COM enabled, MIOS Device ID = 0x02
:080000000000000000000102F5

to-COM enabled, MIOS Device ID = 0x03
:080000000000000000000103F4
[/code]









Best Regards, Thorsten.
3

Thanks Thorsten,

I was able to patch the file , but now is going crazier:

If I compare your hex file , with the one I uploaded from the pic is everything the same besides:

YOUR HEX FILE

200000  00 00 00 00 00 00 01 00

300000  FF FE FF FF FF FF FB FF FF FF FF FF FF FF

MY HEX UPLOAD (FROM THE 18F452)

NO ADRES 200000

300000  00 26 0F 00 01 81 00 0F C0 0F E0 0F 40

Al the rest is the same

Do I have a wiring prob, or what?

4

Hi,

the unimplemented bits in the configuration sector are always zero when reading them back.

Just use the verify function of your programming software to check if the flash content is correct

Best Regards, Thorsten.

5

Ok , that I didn’t know , but when I do an VERIFY I got an error message on adres 300000

" Value in image is 0xFF ; value in target is 0x00"  :-\

Did I screw the pic?

I think I’ll better make MBHP-burner , 

Thorsten , I’ll hope your an patient one  :wink: