What about using BGscript?
I'm using a fresh install of simplicity studio and OSX and BG tool failes to compile with an error:
This is fixed for 2.1.1
I followed the steps and it converted my project quite well, except for one problem. When I compile my project the service characteristic id could not be resolved. What I found is that the gatt_db_bg.proj did not seem to be compiled (I'm using Simplicity Studio with an iar compiler). I created a new example project to see if I could figure out what was wrong and I see that the gatt_db.bgproj is not longer a part of the project, rather, all of the data that was once in gatt_db.bgproj is now found in the gatt.xml file. Is it fair to say that I can just copy the database from my gatt_db.bgproj file to the newly created gatt.xml file, or is this a bug in the conversion process?
The .bgproj is not used since SDK 2.1.0. Your gatt defined in the visual gatt editor. Hovewer you stil can import the .bgproj to it.
The gatt.xml is the output of the visual gatt editor but only used in IAR only projects.
Thank you for describing what I need to do for importing the .bgproj into the visual gatt editor. That resolved the issue and my service id now compiles. However, I've encountered another problem, the defines used for em_i2c.c, em_timer.c, and em_gpio.c are no longer defined. I tried changing the .hwconf file in hopes that that would create the defines, but to no avail. I can add them directly to the project properties but I'm afraid that is only a bandaid. Any thoughts on how I can correct this?
It appears that the problem I'm having has to do with the peripheral mapping. When I select that tab in the configurator I get a "No valid mapping selection" rather than the periperal mapping. When I created a thermometer project from the Launcher, I was able to the a valid periperal map, however, when I enabled Timer 0 in the perifpheral map and enabled the defaultmode periperal the message "No valid mapping selection" returned. However, in this case the defines for the timer were defined. Is there any way to figure out what in the .hwconf is wrong? I'm sure this happened in the conversion from sdk 2.0.3 to sdk 2.1.1