• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 50 subscribers
  • Views 451 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Dynamic attribute table not possible ... Why?

Barna Csenteri
Expert 1880 points

Hi

I need a solution where the attribute table is built up dinamically but before GATTServApp_RegisterService is called (from flash).

The attAttribute_t structure has a const pValue which cannot be changed later, that cannot be changed to non-const since GATTServApp_RegisterService is external function from TI precompiled libraries and get's in conflict if I do so:

 

Warning[w6]: Type conflict for external/entry "GATTServApp_RegisterService", in module battery against external/entry in module gattservapp; function types differ in parameter 1; class/struct/union  

field/base types do not match for field/base 'pValue'; different composite type kinds 

Warning[w35]: There is more than one definition for the struct/union type with tag 'attAttribute_t'; class/struct/union field/base types do not match for field/base 'pValue'; different composite type kinds 

It is intended to force developers creating static attribute tables? If it is why?
I think i am not the only one who will load up the ATTR table structure from the flash and this glitch stopping me from doing this.
In my opinion everyone will need this unless their device is a simple temperature sensor.  
GATTServApp_RegisterService should have all his parameters non-const and all attribute table values should be non const too ...
If there is any way to go around this annoying "feature" please advise ...
regards,
B.