Quantcast
Channel: Forums - Recent Threads
Viewing all articles
Browse latest Browse all 262198

CCS/RF430FRL152H: Programming Over the Air vs. JTAG

$
0
0

Part Number:RF430FRL152H

Tool/software: Code Composer Studio

I've been playing around with the RF430FRL152HEVM for a while now along with going as far as building an RF programmer on a breakout for new RF430FRL152H.  I am now getting to the point where I need to start thinking about actual device code and what the best options are for programming the device down the road.  What exactly is missed when using over the air programming vs. programming through JTAG and CCS.  

http://www.ti.com/lit/ug/slau607b/slau607b.pdf it can program is F867h to FFFFh."  

Taking a look at http://www.ti.com/lit/ug/slau603b/slau603b.pdf , on page 33 we get register information starting at F868h to F8B0h (along with any offsets to account for additional logging space).  These registers appear to be only related to the SD14 settings along with the General Control and Firmware Status Registers.  

On the other hand, http://www.ti.com/lit/ug/slau506/slau506.pdf in Table 9-3 for the largest configuration available. The base address can be found in the device-specific data sheet."  However, in the device specific data sheet, http://www.ti.com/lit/ds/symlink/rf430frl152h.pdf, 

have no idea what some of these registers are.  Starting from the top:

Write succeeded at block: 0 at address: F868h

Write succeeded at block: 3 at address: F880h

Write succeeded at block: 6 at address: F898h

These fall within the F868h to F8B0h range that the data sheet says the OTA has access to program.  Then you get into the rest

Write succeeded at block: 9 at address: F8B0h
Write succeeded at block: 12 at address: F8C8h
Write succeeded at block: 15 at address: F8E0h
Write succeeded at block: 18 at address: F8F8h

Plus many others.  This all appears to fall into the Logging FRAM Memory Space, but obviously is part of the original program.  

So long story short, it looks like all over the air should have access to are registers handling the SD14 captures, but it looks like the programmer is programming much more into FRAM space that does not seem to have any information as to what it is.  


Viewing all articles
Browse latest Browse all 262198

Trending Articles



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