Support needed on porting MSP430F5438 sample codes in bluetopia SDK to MSP430F5529

Hi Santosh,

The only BT demo that is available on the MSP5520 is the "SPPLEDemo_Lite".

You might run into memory issues if you try to run the samples of MSP430F5438 on MSP430F5529. You would need to trim/optimize the sample apps written for MSP430F5438 to be able to work with MSP430F5529.

For example, the SPPDemo app available on the 5438 can be split into two apps (Client/Server) on the 5529 environment.  In addition, you can retain only the basic command set (basically reduce the AddCommand() calls to a minimum).

Hi Santosh,

To add the MSP430F5529 does support only SPPLEDemo_Lite. You have to use the MSP430F5438 board for the other demos.

Regards,

Stonestreet One.

Hi Sandeep/Stonestreet Team,

Thanks for needful suggestions.

We have tried compiling SPP, SPPdemolite and HID program by changing the hardware .h filesand were able to compile and load it to F5529 board. Rest of the examples were giving segment write error.

Please let us know apart from flash size is there any other difference between F5529 and F5438A because we had seen in HRDWCFG.h file UART and port pins assigned is different for F5529 and F5438 as shown below.

#define BT_UART_IV                     (USCI_A1_VECTOR)       // F5529

#define BT_UART_IV                      (USCI_A2_VECTOR)      // F5438

 So does the connection interface changes for F5529?? if yes please let us know what need to be done.

Really it helps in quick development.

Best Regards,

Santosh.

Hi Santosh,

Please check the below link for the hardware porting, and let me know if you still have any queries

http://processors.wiki.ti.com/index.php/CC256x_MSP430_Bluetopia_Hardware_Porting_Guide

Hi Santosh,

The MSP430F5529 board doesn't not have debug output because the debug uart is shared with BT uart. The SPPLE_Lite Demo works but the other demos which require user interaction will not work as shown in the SPP Demo example. To use those demos, you will have to use 5438 board.

Regards,

Stonestreet One. 

Hi team,

I am using the SPPLE_Lite Demo on MSP430F5529 and trying to follow the link provided by you SPP Demo but not able to get any response in the terminal after the reset.

I am using P4.4 and P4.5 for UART debug, please let us know which UART pins on the board should be used for UART debug.

Best Regards,

Santosh.

Hi Santosh,

To clear any confusion here, the 5529 doesn't support any demo except SPPLE_Lite because there is no terminal output. You will not be able to communicate with it using a terminal program. You will have to use the 5438 board. 

Thanks,

Stonestreeet One. 

Hi Team,

Thanks for the clarification.

Can you please provide the link for the document to communicate with bluetooth device (MSP430F5438A+CC2564) from external MPU/MCU to send/receive data, device discovery etc.

Best Regards,

Santosh.

Hi Santosh,

What profile are you looking at? Our basic demo apps page has a link to all the profiles and guides on how to use them. Link here. If you have any issues please post them here.

Regards,

Stonestreet One. 

What would be required to disable the terminal output and make the SPP Demo compatible with the 5529 or 5219 device?  I ask because it has a smaller memory footprint than the SPPLE Demo Lite.  Also does the SPPLE demo switch between legacy and LE modes automatically, i.e. does it support both simultaneously?

Thanks

Angelo

Hi Angelo,

The SPPLE_Lite is basically the terminal less version of the demos. It can be used to make both LE and BR/EDR connections. If you do not require one or the other you can remove those portions. SPPLE Demo does support a simulataneous BR/EDR and LE connection.

Thanks,

Stonestreet One.

Thanks for clarifying regarding classic and LE support with the Lite project. 

My reason for asking about the SPP demo is that even with the SPPLE lite demo, I'm close to the limit of Flash space on the 128kB MSP.  I see that the SPP Demo produces a considerably smaller code image (without GATT, etc.) so I'm trying to get that working in case I can't find enough extra space in the SPPLE lite demo for my application code.

Thanks

I guess the better question/approach is as you say to remove the LE functionality from the SPPLE lite demo project if not needed (rather than trying to port the SPP demo project to the 5529).  Is that (disable LE from the SPPLE lite demo project) an easy thing to do?

Another question I had was regarding the UART flow control (RTS/CTS) lines.  Does the stack use these lines and if so, how can it be configured to work without them?

Thanks

Hi AQ,

The CC256x requires HW flow control, you must connect the RTS and CTS properly.

Please see the section "3.5.2 Host Controller Interface" in the datasheet(from CC256x Bluetooth Main Wiki page)

   I hope this is not too far off topic, as it relates more to timer interrupts, but it also pertains to these example BT projects.

   I see that the SPPLE example project uses timer T1, and I added interrupts for T0 and T2 which are working OK.  But now I'm trying to modify the timer period and I'm not seeing the changes I would expect.  I used the same timer setup code in HAL.c as is being used for T1, so I'm getting ~1kH timer period.  (I actually get about 960 Hz so I'm not sure why it's not more accurate.)

    If I change the TA0CCR0 value I can adjust the timer period, but I would prefer to have a higher resolution.  Currently it seems the clock source is set to ACLK.  I tried to set the source to SMCLK (TASSEL_2), but it seems to make the BT unresponsive.  I'm not sure why that would be since I didn't think this timer was setup or used by the SSO stack or example application.  Also, I'm not sure where/how the rate of the SMCLK is set, and I assume I can't change the ACLK clock rate. 

    How would I go about using a higher frequency clock source for T0?  Can the SMCLK be used, and if so can I change the rate?

HI AQ,

The question you have posted looks more related to MSP430. 

Please check with the MSP430 forum.