Trouble programming BGM111 on custom board using WSTK
06/163/2019 | 12:19 PM
Hello world,
I ran into a weird issue which has brought my progress to a grinding halt.
I recently made a custom board with a BGM111 on it for BLE communication. It worked just fine, the BGM could be programmed and was operational.
I decided to make a small tweak to the power filtering and charging of lipo’s and had new pcb’s manufactured. The thing is that I am unable to program the BGM111 on this new pcb. The new pcb has nothing changed in regard to the JLINK connector.
I soldered different versions to see if I could isolate the problem.
I have one version with all peripheral components.
I have one version with just the BGM111 and link connector.
I use the starterkit to program the BGM111. I use an external power supply to provide a nice 3.00V to the BGM111.
I checked all my connections using a multimeter. Everything seems to be connected properly and I could find no shorts. I also quadruple checked the ribbon cable. When I "click" in the board that comes with WSTK everything runs just fine.
Is there something I am missing / does someone have tip or hint on how to resolve this issue?
The Simplicity Studio settings I tried:
Configuration 1
Debug mode : OUT
Adapter Firmware Version 1v4p0b1016
Switch on WSTK : BAT USB [AEM] -> switching to other modes does not affect the outcome
-> when pressing debug in SS :
Builds successful
Does not give an error message
Resume button is (and remains) in active, making it unable to run the program
Device does not show up on LightBlue app
------
Configuration 2
Debug mode : MCU
Adapter Firmware Version 1v4p0b1016
Switch on WSTK : BAT USB [AEM] -> switching to other modes does not affect the outcome
Device hardware:
Target part : BGM111A256V2
Boards : BGM111 Bluetooth Module Radio Board (BRD4300A)
-> when pressing debug in SS :
Builds successful
Give error : Could not connect debugger. Could not connect to target device.
Kind regards,
Tijs
Discussion Forums
32-bit MCUs
Unanswered
You need to have 3Vdc connected to VTARGET on your programming connector, Pin #1.
0
Hey GeneC, thanks for the quick reply. My 3Vdc is connected to the VTARGET via the power supply. So that can't be it, I am afraid.
0
do you have a chance to check if the simplicity Commander could connectand detect the target?
I was able to successfully flash the projects .bin file. However, still BGM111 would not show up in the LightBlue app.
Then I switched back to Simplicity Studio and when I debug I can ‘resume/run’ the software; yet I have to unfold the ‘folder-tree’ a bit (see image 1). This is something I did not have to do with my previous prototype.
image 1 : expanded folder tree in the debug-window -> I can only 'resume/run' from the lowest level (main() at main.c:108 0xebec)
The BGM111 then runs successfully and can be discovered, connected and interacted with via the app.
However, there are still some issues that arise :
Issue 1
However, after a minute or so some error messages pop-up from Simplicity Studio. Terminating the debug session.
image 2 : Two error messages appear in quick succession in Simplicity Studio when the debug session is resumed.
Issue 2
If I try to debug again before the fatal messages I get an error stating that the device is underpowered, which is impossible as it is hooked up to 3Vdc power supply. Or that it cannot reconnect to the J-LINK
image 3 : Error messages when trying to re-debug.
Issue 3
If I want to re-upload I have to reconnect the Adapter in Simplicity Commander, then reconnect the Target, then flash, then go to Simplicity Studio, quickly press Debug, then go into the folder-tree highlight the correct file and press resume.
image 4 : warning pop-up if I try to re-flash before reconnecting Adapter and Target.
These issue really mess up my work flow and are far from ideal. I also do not understand what is causing them. In a previous prototype I was able to directly program via the Simplicity Studio Debug, without any issue.
My hardware setup is the same as mentioned in my first post.
Switch on the WSTK is set to AEM.
Does anyone know a way to fix these issue in order to get smooth and reliable workflow to program an external BGM111
0
Did you remove the board (if any) from the WSTK socket? It will draw power from VTARGET (whatever the switch position).
Your external 3.0V supply may also interfere with the 3.3V that AEM mode supplies to VTARGET.
(Presumably you have also added a common ground between the external supply and the WSTK.)
Trouble programming BGM111 on custom board using WSTK
Hello world,
I ran into a weird issue which has brought my progress to a grinding halt.
I recently made a custom board with a BGM111 on it for BLE communication. It worked just fine, the BGM could be programmed and was operational.
I decided to make a small tweak to the power filtering and charging of lipo’s and had new pcb’s manufactured. The thing is that I am unable to program the BGM111 on this new pcb. The new pcb has nothing changed in regard to the JLINK connector.
I soldered different versions to see if I could isolate the problem.
I use the starterkit to program the BGM111. I use an external power supply to provide a nice 3.00V to the BGM111.
I checked all my connections using a multimeter. Everything seems to be connected properly and I could find no shorts. I also quadruple checked the ribbon cable. When I "click" in the board that comes with WSTK everything runs just fine.
Is there something I am missing / does someone have tip or hint on how to resolve this issue?
The Simplicity Studio settings I tried:
Configuration 1
Debug mode : OUT
Adapter Firmware Version 1v4p0b1016
Switch on WSTK : BAT USB [AEM] -> switching to other modes does not affect the outcome
-> when pressing debug in SS :
Builds successful
Does not give an error message
Resume button is (and remains) in active, making it unable to run the program
Device does not show up on LightBlue app
------
Configuration 2
Debug mode : MCU
Adapter Firmware Version 1v4p0b1016
Switch on WSTK : BAT USB [AEM] -> switching to other modes does not affect the outcome
Device hardware:
Target part : BGM111A256V2
Boards : BGM111 Bluetooth Module Radio Board (BRD4300A)
-> when pressing debug in SS :
Builds successful
Give error : Could not connect debugger. Could not connect to target device.
Kind regards,
Tijs
Hey GeneC, thanks for the quick reply. My 3Vdc is connected to the VTARGET via the power supply. So that can't be it, I am afraid.
do you have a chance to check if the simplicity Commander could connectand detect the target?
not sure if below KBA helps or not.
https://www.silabs.com/community/software/simplicity-studio/knowledge-base.entry.html/2016/10/07/simplicity_studiov4-FMQd
https://www.silabs.com/community/wireless/bluetooth/knowledge-base.entry.html/2015/12/01/programming_an_exter-kEU6
The plot thickens :
I have been playing around with simplicity commander following this guide:
https://www.silabs.com/community/wireless/bluetooth/knowledge-base.entry.html/2015/12/01/programming_an_exter-kEU6
I was able to successfully flash the projects .bin file. However, still BGM111 would not show up in the LightBlue app.
Then I switched back to Simplicity Studio and when I debug I can ‘resume/run’ the software; yet I have to unfold the ‘folder-tree’ a bit (see image 1). This is something I did not have to do with my previous prototype.
image 1 : expanded folder tree in the debug-window -> I can only 'resume/run' from the lowest level (main() at main.c:108 0xebec)
The BGM111 then runs successfully and can be discovered, connected and interacted with via the app.
However, there are still some issues that arise :
Issue 1
However, after a minute or so some error messages pop-up from Simplicity Studio. Terminating the debug session.
image 2 : Two error messages appear in quick succession in Simplicity Studio when the debug session is resumed.
Issue 2
If I try to debug again before the fatal messages I get an error stating that the device is underpowered, which is impossible as it is hooked up to 3Vdc power supply. Or that it cannot reconnect to the J-LINK
image 3 : Error messages when trying to re-debug.
Issue 3
If I want to re-upload I have to reconnect the Adapter in Simplicity Commander, then reconnect the Target, then flash, then go to Simplicity Studio, quickly press Debug, then go into the folder-tree highlight the correct file and press resume.
image 4 : warning pop-up if I try to re-flash before reconnecting Adapter and Target.
These issue really mess up my work flow and are far from ideal. I also do not understand what is causing them. In a previous prototype I was able to directly program via the Simplicity Studio Debug, without any issue.
My hardware setup is the same as mentioned in my first post.
Switch on the WSTK is set to AEM.
Does anyone know a way to fix these issue in order to get smooth and reliable workflow to program an external BGM111
Did you remove the board (if any) from the WSTK socket? It will draw power from VTARGET (whatever the switch position).
Your external 3.0V supply may also interfere with the 3.3V that AEM mode supplies to VTARGET.
(Presumably you have also added a common ground between the external supply and the WSTK.)