This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Dear Sir,
Customer using DS100BR111 and setting file at attach, if you can help transfer to .bin file?
Thanks, Ian.re-driver config setting.zip
Dear Michael,
Thanks for information.
1. customer use 8 EEPROM (Each 4 configurations in 3U and 7U)
2. Thanks and I will ask customer send us .h in future.
Thanks, Ian.
Hi Ian,
I went through SigCon Architect to first generate the .hex file, then used hex2bin to translate the file to .bin.
The .bin and .hex files have been added to the previous attachment you provided me.
Next time, please refer to the following post for details about how to create a hex file so that you can create these .bin files in case there is need in the future: https://e2e.ti.com/support/interface/high_speed_interface/f/138/p/583561/2143136
Dear Michael,
I would like convert 1.hex to 1.bin and according your suggest using hex2bin,
I got 1.bin at attach, would you pls kindly help to check is correct .bin file I convert?
Thanks for help.1.zip
Hi Ian,
Yes, I believe this is done correctly! For future reference, a good, free tool you can use to check on the .bin file contents is Hex Editor Neo. From there, you can check the contents of the .bin file with the contents of the .hex file. Note that Hex Editor Neo will parse out everything except for the data. In other words, you will only see the gray portion when viewing the .bin file in Hex Editor Neo.
I'm curious about the contents of the .bin file and whether this is just a simple test or an actual hex file. I ask because it seems like all the registers in each of the EEPROM slots are programmed to 0x00.
Regards,
Michael
Dear Michael,
I checked .bin content that I transfer from .hex looks content is empty. Would you pls help to check what I'm wrong? Thanks for help.
Hi Ian,
There appears to be nothing wrong with the .bin file based on the .hex file you provided.
The 1.hex file you provided in the zip folder is also empty. What should the .hex file content be?
Thanks,
Michael
Dear Michael,
Here are .cfg, .hex and bin at tatach, I according your describe general .hex from .cfg then to .bin.
Pls kindly advise wher is wrong.
Appreciate for help. IAN.Release.zip
Hi Ian,
I tried with several profiles to load in the .cfg file, but it seems like you used a profile other than the DS100BR111 to generate the .cfg file. Using the incorrect profile to log a .cfg file results in a parsing error.
Can you let me know which profile you used to generate this .cfg? From there, I should be able to help you create the .hex file.
Michael
Hi Ian,
Please see the corrected hex file and bin file attached.
I think what you may have been doing is setting the correct configurations in the High or Low Level Page, but not updating the EEPROM slot from the device settings. You must click "Update Slot From Device" in order to update the highlighted slot (note that Device 0xB0 in Slot 0 is selected in the "Address/Slot list Section" table). Afterwards, you can "Write to EEPROM Hex" file to generate the hex file.
After ensuring that Slot 0 is updated, I generated the hex file, then used "hex2bin.exe" to create the binary file. Note that this binary file assumes that only 1 device with Address 0xB0 is being programmed. You will need to add "No. of Device" in the top left in order to program more Slots.
Michael