I am having troubles getting started with the app development using the Blue Gecko Module Wireless Starter Kit, BGM111....I would like to know why I can't get BGTool working (it is a compatible tool, device is powered up and connected via USB cable to the computer and power switch is in AEM position)...what am I missing?
Please see the error that I get when launching BGTool: ''Unknown option 'commander'".
(Image 1 in the attachment)
After I click OK, the main window opens and I have the option to select:
1. The PORT
-Intel(R) Active Management Technoogy - SOL (COM3)
-Jlink CDC UART Port (COM4)
-Communications Port (COM1)
--->I tried choosing either of the three...same situation. The device manager indicates that there are drivers for Jlink CDC UART Port (COM4).
2. and BAUD RATE: 115200 (i choose 115200)
Immediately after clicking OPEN, the connection is established, but I get this error:
"Device not responding!
The device not responding. Check that:
-the kit is powered
-the module carrier is connected to the WSTK main board
-the baud rate is set correctly (default 115200)"
(image 2 in the attachment)
Can anyone explain what I am doing wrong or what I need to do to get thinga working?
the error "Unknown option 'commander" can be ignored. This will be fixed in next update and the error does not prevent using BGTool normally.
The COM port you should use is Jink CDC UART Port and use the default baud rate 115200.
BGTool tries to talk to the BGM111 using BGAPI commands. This requires that the BGM111 is programmed with a firmware that is configured to receive BGAPI commands over UART. This mode of operation is called NCP mode (Network CoProcessor). See application note AN1042 for more details.
I have attached a series of screenshots that shows step-by-step how to program NCP mode firmware and how to launch BGTool. The instructions refer to BGM121 but the same applies to BGM111 as well.
Thank you! That seems like progress. What I did not do before is program it into NCP mode. I did it this time and followed all your steps (the LCD display on the device no longer shows what it did before so it has been programmed), but after setting Jink CDC UART Port and the default baud rate 115200, the next window shows the same "Device not responding error". What else can I do? What could the problem be?
That's strange. I tested the exact same sequence both with BGM111 and BGM113 kits. The LCD goes blank and I get the 'unknown option "commander"' that I simply ignore. Then I get the response from the development kit as shown in the screenshots.
Let's see if you can get the "LED blinky" thing working. If that is also failing then your kit must be broken. To me it seems you have done everything as instructed but still nothing seems to work properly.
I find the whole thing very unstable....I shut down Simplicity Studio and restarted it. I unplugged the kit and reconnected it. Then tried the demo again and the BGTool with the tools you pointed out and it connected! There was no issue and it worked. So as far as getting the BGTool to work, this is sorted (for now).
I then started the BGTool again and went to Upload my own file for Blinky. I placed my folder on the desktop so I selected the path to the project.xml and hit Build. Build has failed. Because "Cannot find the project file"? Does this sound right?
Does it make a difference is the project extension is *.XML or *.bgproj?
I think I got the difference between bgproj and the xml file. There are 2 options:
- to use a *.bgproj file, which includes the scripting (the bgs content too).
- to use a file for scripting (.bgs) and one for the project (.xml)
So the only thing now is...Blinky - has the build failed because of my coding or is there another problem with: "Build has failed. Cannot find the project file." ?
Corrected version of "blinky" is posted in the other thread: