Quantcast
Channel: Wireless Connectivity
Viewing all articles
Browse latest Browse all 116964

Forum Post: RE: TI BLE Stack v1.3.1 released (April 18th 2013)

$
0
0

So you have not (or not completely) ported your HAL target subdirectory (BLE-CC254x-1.3.1\Components\hal\target\your-target-sub-dir-name (e.g. CC2540EB)

The new function call has 2 parameters:       LL_PowerOnReq( (halPwrMgtMode == CC2540_PM3), wakeForRF );

But that is not the only change to port in hal_sleep.c - you will see that a constant has changed as well.

So - how do you find all of the pertinent changes that you need to port?

Embedded Systems Porting 101:

I use WinMerge to do a directory compare of the 2 stack installs and then recursively diff down through all of the subdirectories. So wrt to the specific module in question, I will iterate and eventually be diff-ing these sub-dirs:

BLE-CC254x-1.3\Components\hal\target\CC2540EB
BLE-CC254x-1.3.1\Components\hal\target\CC2540EB

Which will result in seeing a diff in what TI has done with the hal_sleep.c module, in which case I open the diff between them:

BLE-CC254x-1.3\Components\hal\target\CC2540EB\hal_sleep.c
BLE-CC254x-1.3.1\Components\hal\target\CC2540EB\hal_sleep.c

And then I make the same diffs to the hal_sleep.c in the specific HAL target that I created for my proprietary h/w.




Viewing all articles
Browse latest Browse all 116964

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>