- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Per your response here: Need to program a certain Bluetooth address into my device....
I see the address changing in the BLE dongle GUI which I use to scan my BLE device:
The "Public" address shown in the picture above used to be: 20:73:7a:13:5d:a6 .
Each time I program the device, I see a different "randomly" generated address there. Like I said, I didn't change anything in the test.hex file. I only run the following command each time:
ChipLoad.exe -BLUETOOLMODE -PORT COM24 -BAUDRATE 115200 -MINIDRIVER
uart_DISABLE_EEPROM_WP_PIN1.hex -BTP 20737_EEPROM.btp -CONFIG test.hex
-CHECKCRC -NOVERIFY -DLMINIDRIVERCHUNKSIZE 251
How do you explain this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Here is a good article explaining the BD_ADDR and how to manage it.
Cliff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am using the cgs-and-chipload console method to download the hello_sensor onto a tag3.
1) The following is my make target in the SDK: hello_sensor-BCM920736TAG_Q32
2) I used cgs.exe to do a conversion to .hex file, with a pre-determined BD address:
cgs.exe -I myHello.hex -O DLConfigBD_ADDRBase:207777123456 -A 0xFF000000 -B 20736_EEPROM.btp -D . A_20736A1-hello_sensor-rom-ram-spar.cgs
3) I used chipload.exe to download it onto my tag3:
chipload.exe -BLUETOOLMODE -BAUDRATE 115200nfc -PORT COM13 -MINIDRIVER uart_DISABLE_EEPROM_WP_PIN1.hex -CONFIG myHello.hex -DLMINIDRIVERCHUNKSIZE 251 -BTP 20736_EEPROM.btp
It works for me. For your reference.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello.
Since you haven't changed the hex, I don't think that is the problem.
However to rule out this case completely, do you see the same behavior when you use another hex file?
Also, have you changed the btp file?
Have you used the original btp file that you haven't changed to program?
Lastly, have you tried boont's way to program? using cgs to produce hex file with predefined BD address and then uploading with chipload?
This method seems to be the best instead of changing the btp file. This method has worked for me too.
James
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok, I gathered all the necessary files into a temp folder. Do you have similar ones as well?
Then I follow the steps described in my above post.
Can you try your download using the SDK? Just to check it out.
Otherwise, can you try to download the hello_sensor onto your product?
Let us know how it goes. yliu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content