mcafzap got a reaction from energia in SPI on cc1310
I was using 'SPI.end()' at the end of each read or write method/subroutine but I had noticed on the 5969 and the cc3200 that I had to re-declare the mode, speed and bit order.
In the case of the 1310, I initially solved the problem by re-starting the bus with SPI.begin(), but simply excluding all references to SPI.end() is better.
Thank-you for your response. It just goes to show you should sleep on a problem first before posting.
mcafzap got a reaction from spirilis in [Energia Library] Nordic nRF24L01+ library
Having spent some time thinking about this, I'm undecided. Simply setting a flag before transmitting and clearing it when done, does the trick. Testing this flag in the interrupt routine prevents the reading of data. It would be unnecessary if interrupts are not used. (I needed to use interrupts to minimise power.)
BTW, thanks for your efforts - it has saved me a lot of time despite my problems.
mcafzap reacted to spirilis in Energia - Assembler warning
It's safe to ignore.
The linker script for the compiler has "permission attributes" for the different sections or more specifically the memory segments where they go. The default permissions for the ROM segment, where .text lives, is RX - Readable, Executable, but not Writable. In practice this isn't enforced or enforceable in any way besides the fact that it helps the compiler catch goofy mistakes like trying to put something writable in ROM ...
... except "ROM" on the FRAM chips isn't ROM, but FRAM, which IS writable. However the conventional name "ROM" is used in the msp430fr5969 linker script anyhow to allow the template section linker script to be used (I think that's how it works) without modification, so you end up with this benign warning since you are declaring an array that can be written to.