SENSOR-CONTROLLER-STUDIO: sensor controller ram overflow - cc1350

Hello,

No, there is no way to increase the memory size. I suggest you optimize the size of the code and minimize the use of variables. maybe reuse some of them ?

Regards,
AB

What about splitting the initialization code into a separate project from the execution code?

Basically as follows:
Load the initialization code onto the sensor controller (with empty execution and termination)
Configure the i2c sensors from that initialization code
Unload that project from the sensor controller

Load the execution code onto the sensor controller (with an empty initialization block)
Read from the previously configured sensors in the previous project

Terminate, unload, and repeat....

Currently, the Initialization, execution, and termination code all live in the same project and need to be loaded into ram at once (when only one of these three is actually being processed at any given time)


The generated code is not setup for this sort of split operation, so I'd have to do some significant modifications. Ultimately I'll have to optimize my code, but I'm thinking this approach might increase the usable code size.

That sounds like a good idea, but I have not tried it before. I am interested in knowing if you get it to work that way. But I do not think you need to keep unloading it and reloading it.

Maybe only once, after you initialize and when you load the execution code activate the RTC and just run the execution code at a periodic rate?

AB

I'm a long ways from implementing that. I just wanted to see what folks thought about the general concept since it seems a bit hacky. Along those lines, it might be easier to just initialize the device in CCS, and then switch over to the CCS code for the execution cycles. I dont know if the i2c pins can be easily shared between processors like this (i'm still investigating).

On the optimization front, the following appears to take 18 words of code ram:

    i2cStart();
    i2cTx(I2C_OP_WRITE | (BMP280_ADDRESS<<1));
    i2cTx(BMP280_RESET);
    i2cTx(BMP280_RESET_VAL);
    i2cStop();

In the documentation it mentions procedure calls and macros. Macros don't appear to save space (I believe they just get expanded by the compiler?). Procedure calls don't seem to be user definable, or at least is indicated not by the documentation. If I had a bunch of calls that look like the above, is there any way to optimize across them? A true procedure sounds like it would be ideal because it would reuse 3 of the 5 lines (which appears to be 10 words according to the code generator). I know... I "might" also be able to write all the addresses and bytes in a single i2c transaction,  but not all devices support that behavior.

I'm also reading a number of 16 bit values, but those take 2 i2cRxAck's and a shift/addition to cram the 2 bytes into one output. It seems like that would be a good candidate for some code reuse/optimization as well. I already have larger read blocks in a loop, which saves a lot of code words, but I still have to deal with the final nack, so looping is not as efficient when trying to read a 2byte (16bit) piece of data from the i2c device.