This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

problem with HEX2BIX.EXE output (B6 file)

Data blocks seem to be mapped to invalid memory addresses when building the b6 EEPROM image?

Product: EZ-USB FX

EERPOM data can only be loaded into 8051 program/data RAM at 0x0000-0x1B3F, but B6 output file put data into addresses 0x42xx - 0x43xx (outside of the specified range). How can i fix this problem? Or is there an updated version of hex2bix.exe with this fixed?

  • the two sets of codes below are B6 version of the same hex file (supposingly)

    this is the first few lines of the code convert by using hex2bix.exe...it does not work

    b6 47 05 31 21 00 00 04 00 00 03 00 00 02 47 a7 00 03 00 33 02 47 cc 00 03 00 43 02 45 00 03 ff 40 00 90 7f e9 e0 70 03 02 41 9b 14 70 03 02 42 17 24 fe 70 03 02 42 8e 24 fb 70 03 02 41 95

    this is the sample B6 code that comes with the development kit i got...and it works

    b6 47 05 31 21 00 00 04 00 00 03 00 00 02 08 2a 00 03 00 33 02 08 4f 00 03 00 43 02 06 00 03 ff 00 80 90 7f e9 e0 70 03 02 02 1b 14 70 03 02 02 97 24 fe 70 03 02 03 0e 24 fb 70 03 02 02 15

  • you are using the eval version which is made that way so it allow you to evaluate but not to produce.

    Erik

  • Is there a way to change the mapping? Any way to create a usable B6 file to test? It doesnt make sense the hex2bix.exe doesnt work when it is there. How am i supposed to evaluate when i dont even know if it works or not? Everything in the b6 ouput files (sample & converterd by hex2bix.exe) are the same except the address locations. Maybe one can change the hex2bix.c and offset the memory locations, but i dont know how as i dont understand what the hex2bix code is doing.

    Thx for the help!

  • I found the solution. It is quite smiple actually. i just need to link the hex file to correct internal memory address and it would solve the problem. (i kept thinking the address mapping is in the hex2bix. my bad)

  • "i kept thinking the address mapping is in the hex2bix"

    Whatever made you think that?!