- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a board based on the BCM20732S, which previously worked but now fails to be detected and programmed.
Is it possible that something I did to it corrupted the internal eeprom? What sorts of things could cause this, and is there any way to recover from this?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello idgirod,
We have an "official" document coming out soon but here are some excerpts to get you out of trouble. You can find each of the programming files under the SDK directory as shown below.
Location of the cgs.exe file:
Location of the Chipload.exe file
Location of the 20732_EEPROM.btp file
Using cygwin:
The following procedure converts the cgs file to a hex file:
1. Using command-line interface(eg. Cygwin, cmd.exe), run cgs.exe.
2. Use the following command
a. ./cgs.exe -I <output_file_name.hex> –A 0xFF000000 –B <btp_file.btp> -D <file.hdf>
3. Definitions of parameters:
a. output_file_name.hex – will be the converted hex file.
b. btp_file.btp – btp file for the TAG.
c. input_file.cgs – built cgs file for the application.
d. 0xFF000000 – base address for the EEPROM
e. File.hdf - directories for hdf file
Results of the successful command execution:
Downloading the hex file:
The following procedure downloads the hex file:
1. Using command-line interface, run chipload.exe.
2. Use the following command
a. ./Chipload.exe –BLUETOOLMODE –PORT COM16 –BAUDRATE 115200nfc –MINIDRIVER <minidriver.hex> -CONFIG <output_file_name.hex> -BTP <btp_file.btp> -NODLMINIDRIVER
3. Definitions of parameters:
a. COM16 – connected port.
b. btp_file.btp – btp file for the TAG.
c. Output_file_name.hex – converted hex file.
d. btp_file.btp – btp file for the TAG
Results of the successful hex file download execution:
Let me know if this helps.