LED Blinky with BGScript Programming

If you are not yet setup the development environment. Check the last post.


I am going to guide you how to make LED blink (turn on and turn off) in every 1 seconds with BGScript.

Create 3 config files (gatt.xml, hardware.xml, project.xml)

Every file have it’s own function and contains the information needed when compile to binary file. These 3 files are config files that is needed and you must always remember to import these in every project. What you needs to do is copy following source code and paste it.

hardware.xml is configuration file that related to ble112 hardware configuration.

<?xml version="1.0" encoding="UTF-8" ?>
    <sleeposc enable="true" ppm="30" />
    <usb enable="false" endpoint="none" />
    <txpower power="15" bias="5" />
    <usart channel="1" alternate="1" baud="57600"  endpoint="api" />
    <wakeup_pin enable="true" port="0" pin="0" />
    <port index="0" tristatemask="0" pull="down" />
    <pmux regulator_pin="7" />

gatt.xml exposes the Bluetooth services and profiles.

<?xml version="1.0" encoding="UTF-8" ?>
    <service uuid="1800">
      <description>Generic Access Profile</description>
      <characteristic uuid="2a00">
        <properties read="true" const="true" />
        <value>BG Demo</value>
      <characteristic uuid="2a01">
        <properties read="true" const="true" />
        <value type="hex">4142</value>
    <service type="primary" uuid="9000" id="manufacturer">
        <characteristic uuid="9100">
            <properties read="true" const="true" />
            <value type="hex">000780c0ffeef00d</value>
        <characteristic uuid="9101">
            <properties read="true" const="true" />
        <characteristic uuid="9106">
            <properties read="true" const="true" />
    <service uuid="e001">
       <description>Battery status</description>
       <include id="manufacturer" />
      <characteristic uuid="e101" id="xgatt_battery">
          <properties read="true" notify="true" />
          <value type="hex">ABCD</value>
    <service uuid="00431c4a-a7a4-428b-a96d-d92d43c8c7cf">
        <description>Bluegiga demo service</description>
        <characteristic uuid="f1b41cde-dbf5-4acf-8679-ecb8b4dca6fe">
            <properties read="true" write="true"/>
            <value type="hex">coffee</value>
</configuration></pre><br /><b>project.xml </b>tell bgbuild what roles played by every xml file.<br /><pre class="brush:xml"><project>
    <gatt in="gatt.xml" />
    <hardware in="hardware.xml" />    
    <script in="blink.bgs" />
    <image out="out.hex" />    

Create blink.bgs

I will explain detail on blink.bgs later. Copy following code and paste to blink.bgs
dim flag
dim interval
# Boot event listener
event system_boot(major ,minor ,patch ,build ,ll_version ,protocol_version ,hw)
 flag = 0
 interval = $8000
 # Configure the P0_0 as output
 call hardware_io_port_config_direction(0, 1)
 # Enable P0_0 pin
 call hardware_io_port_write(0, 1, 1)
 # Start a 5 second, one stop timer
 call hardware_set_soft_timer(interval, 0 ,1) 
# Timer event listener
event hardware_soft_timer(handle)
  #declare hardware_set_soft_timer to allow it work as forever loop as recursive
 if flag = 0 then
 # When timer expires disable P0_0 pin
 call hardware_io_port_write(0, 1, 0)
 call hardware_set_soft_timer(interval, 0 ,1)
 flag = 1
 # When timer expires enable P0_0 pin
 call hardware_io_port_write(0, 1, 1)
 call hardware_set_soft_timer(interval, 0 ,1)
 flag = 0
 end if 

Debug with bgbuild.exe

bgbuild.exe can be found at {ble_directory} -> bin directory. 
Open command prompt and go to blink directory that created at beginning of this article, and run following command.
C:\Bluegiga\ble-1.2.1-91\bin\bgbuild.exe project.xml
Replace {ble_directory} to your own path. You should get the result look as below.
Then, binary file out.hex is generated. It is the file we needed to flash into ble112.

BLE SW update tool

Bluegiga prepared a flash tool called Bluegiga BLE SW Update tool. This tool can be found at BleUpdate directory, it is placed at different place with bgbuild.exe.
Click Refresh and Info to choose the debugger. Then click browse to the out.hex that generated at last section inside blink directory.
Then click update and it will write the binary file into ble112.

Last job

Connect LED to P0_0 pin. Then you will see LED blink at every 1 seconds.

Explaination on blink.bgs

event system_boot is something like int main() in c language. It is always the first part to be executed after global variables.
dim is used to declare variable. Usually, it means int or char in c language. 
$ mark in bgscript used to declared the following number is hexadecimal. In this case, interval = $8000 is same as interval = 0x8000 in c language. Following equation is used to calculate the time for timer. Based on the equation below, clock of ble112 is 32.768kHz, in order to set 1 seconds, interval needed to be set to 32768 ( 8000 in hexdecimal ).

You might reliased that there is not for or while loop in my script. How can I achieve forever loop? The answer is recursive between hardware_set_soft_timer and hardware_soft_timer. 
There is no built in delay event so recursive method is the only way to do forever loop.
hardware_set_soft_timer set the timer start and hardware_soft_timer is the handler event after the time specified in 1st parameter of hardware_set_soft_timer is passed.
By adding hardware_set_soft_timer into hardware_soft_timer, the timer will started again when timer is stop.


Thank you for reading.

Getting started with Developing Bluetooth 4.0 LE and Android with BLE112 Bluetooth module

If your objective is asking BLE112 to say “helloworld” to Android or any other smart phone in faster, quick and simple way. You are on the right way. I am going to guide you how to get BLE112 to connect to your Android, Iphone or any others smart phone.


What you need is

  1. Bluetooth module ( BLE112 )  USD$50
  2. CC Debugger USD$ 49
  3. Android which adaptable to Bluetooth 4.0

And the software you need to installed

  1. Bluetooth Smart Software and SDK ( Provided by bluegiga ) 
Bluegiga provide the SDK for free, but you have to register a new account to download it.

Reason why I choose BLE112 breakout board. BLE112 embed with antenna and bluetooth built in chip (Texas Instrument cc2540). It means you can begin your development with ble112 in a very cheap price around USD$12 to $16. However, bluegiga do not provide a nice pin leg and you need to soldering it to board in order to connect it to cc debugger. Here’s the reason why I choose jeff-rowberg breakout board. On jeff-rowberg site, it provide two type of board, one is ble112 embed and one is without embed. It save my time to design the breakout board and soldering ble112.


Download the Bluetooth Smart software and SDK and install it by follow the instruction.

After you have successfully installed Bluetooth SDK, you are almost there. Connect cc debugger and ble112. To easy my developing, I soldering pin socket to ble112. It is optional for you either soldering pin socket or not.

There are three things needed to connect.

  1. usb to cc debugger
  2. cc debugger to ble112
  3. ble112 to 3.3V power supply
Pinout is written on board, so you should able to find GND and 3V3
Newbie usually think that debugger provide power to module, but it is WRONG.
Debugger do not provide power to module, you have to provide external power to module. Here’s the why number 3 comes.
After you have setup all the things, let’s begin to debug the ble112.


Go to Bluetooth Smart SDK directory -> example -> find_me directory. Run project.bgproj and you will see the following window.
Click Refresh button to detect debugger. Then, click Info to detect ble112. The you should see that cc-debugger led turn red to green and the message show in dialog. If led already turn green light, then it should be okay. Green light means that chip have been successfully detected.
If “No chip detected” messages is showed and LED is red, it means that cc debugger unable to detect the ble112. There are 3 things you needs to do.
  1. Make sure BLE112’s power is supplied by external power supply but not from debugger.
  2. Make sure CC debugger pin is correctly connected to ble112.
  3. Long press the cc debugger reset button.
Make sure that File point to correct directory “find_me” and “project.bgproj”.
Then, click Update to begin debug.
If you see the following messages, it means you have successfully debug the chip. 

Testing with Android

Go to bluetooth settings and enable Bluetooth. Click “Search for devices”.
If you see “Bluegiga Find Me”, it means your bluetooth have successfully connected to Android. If you can’t see it. Most probably your android device is not adaptable to Bluetooth 4.0, test it with another device which adaptable to Bluetooth 4.0


Here’s the end of the blog. Hope you are successfully to see the messages. On next section, I will begin to explain about more detail on what is going with “Bluegiga Find me” and how BLE112 interact with microcontroller.
Hope you will continue with it. Thank you for your reading.