map_mse

Overview

This example demonstrates the MAP MSE basic functionality, the MSE device support be connected to a MAP MCE like a Hands-Free unit in the car or a board running a MAP MCE application. And the MSE example support sending response/event to the MCE.

Prepare the Demo

  1. Open example’s project and build it.

  2. Connect a USB cable between the PC host and the OpenSDA USB port on the target board.

  3. Open a serial terminal on PC for OpenSDA serial device with these settings:

    • 115200 baud rate

    • 8 data bits

    • No parity

    • One stop bit

    • No flow control

  4. Download the program to the target board.

  5. Either press the reset button on your board or launch the debugger in your IDE to begin running the example.

Running the demo

The log below shows the output of the example in the terminal window. The demo start waiting for the MCE to connect.

Bluetooth MAP MSE demo start...
Bluetooth initialized
BR/EDR set connectable and discoverable done

Procedures to run

  1. Prepare a MCE, connect the MSE device and then create MAS OBEX connection.

  2. After that, MCE can send commands to MSE and MSE will respond to the commands.

The bellow commands have been supported:

  1. get folder listing

    • This example will send Folder-listing object but not parse/send application parameters from/to MCE.

  2. set folder

    • This example will set folder correctly.

  3. get message listing

    • This example will send Messages-listing object with NewMessage, MSETime and ListingSize but not parse application parameters from MCE.

  4. get message

    • This example will send bMessage object but not parse/send application parameters from/to MCE.

  5. set message status

    • This example will set the read status and the deleted status correctly and save the extended data to the local buffer.

  6. push message

    • This example will save the message and return a message handle but not parse application parameters from MCE.

  7. set notification registration

    • When NotificationStatus is ON, this example will initiates a MNS OBEX connection.

  8. update inbox

    • This example always send success when receiving update inbox request.

  9. get mas instance information

    • This example will send MASInstanceInformation but not send application parameters to MCE.

  10. set owner status

    • This example will save the application parameters to the local buffer that is used to respond to get owner status.

  11. get owner status

    • This example will respond to get owner status with the application parameters saved in set owner status.

  12. get conversation listing

    • This example will send Conversation-Listing object but not parse/send application parameters from/to MCE.

  13. set notification filter

    • This example always send success when receiving set notification filter request.

Note:

  1. This example only supports one MAS and MNS OBEX connection.

  2. This example doesn’t support all application parameters and only supports to parse/send the part of application parameters from/to MCE.

  3. This example is based on FatFs RAM disk. There is a limited memory to store the incoming message from MCE.

Supported Boards