• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 80 subscribers
  • Views 760 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.

eZ430-RF2500T SMPL_Send bytes limitation

Vinx5
Prodigy 20 points

Other Parts Discussed in Thread: SIMPLICITI

Hi guys. I'm using an eZ430-RF2500T target board. I start with the demo project where if i try to send over than 10 bytes (modifing the number of messages) the device seem that it doesn't work (and the red led blink). What is the byte limitation that i can send with an SMPL_Send function?

  • 0
    TI__Guru 64920 points

    There is a #define declared in the smpl_nwk_config.dat file called MAX_APP_PAYLOAD which defines the maximum data payload size.  The default is 10 bytes which is consistent with your findings.  You can adjust this number to the size you need.

    Keep in mind the SimpliciTI stack supports up to a 50 byte payload maximum.

  • 0 in reply to BrandonAzbell
    Prodigy 20 points
    if I try to change that value I get the following warnings

    Building configuration: Access Point - Debug
    Updating build tree...
     
    5  file(s) deleted.
    Updating build tree...
    bsp.c 
    demo_AP.c 
    Warning[Pa093]: implicit conversion from floating point to integer C:\Documents and Settings\vinx5\Desktop\eZ430-RF2500 Wireless Sensor Monitor (IAR Source) v1.02\demo_AP.c 329
    mrfi.c 
    nwk_globals.c 
    vlo_rand.s43
    Linking
    Warning[w6]: Type conflict for external/entry "MRFI_Receive", in module nwk_frame against external/entry in module mrfi; 
    function types differ in parameter 1; class/struct/union types have different sizes
      /* In module nwk_frame: */
      /* Function, args 1, attr 0 */
      void (__cc_version2 MRFI_Receive)(mrfiPacket_t *);
        typedef struct __Unnamed_6_137 mrfiPacket_t;
      /* In module mrfi: */
      /* Function, args 1, attr 0 */
      void (__cc_version2 MRFI_Receive)(mrfiPacket_t *);
        typedef struct __Unnamed_3_118 mrfiPacket_t;
    Warning[w6]: Type conflict for external/entry "MRFI_Transmit", in module nwk_frame against external/entry in module mrfi; 
    function types differ in parameter 1; class/struct/union types have different sizes
      /* In module nwk_frame: */
      /* Function, args 1, attr 0 */
      uint8_t (__cc_version2 MRFI_Transmit)(mrfiPacket_t *);
        typedef __bsp_uint8_t__ uint8_t;
        typedef struct __Unnamed_6_137 mrfiPacket_t;
        typedef unsigned char __bsp_uint8_t__;
      /* In module mrfi: */
      /* Function, args 1, attr 0 */
      uint8_t (__cc_version2 MRFI_Transmit)(mrfiPacket_t *);
        typedef __bsp_uint8_t__ uint8_t;
        typedef struct __Unnamed_3_118 mrfiPacket_t;
        typedef unsigned char __bsp_uint8_t__;
     
    Total number of errors: 0
    Total number of warnings: 3

    If i try to load the program into the device (the AP or the EP) is seems that doesn't work. i've read that the cause is the library wich is builded with APP_PAYLOAD on 10. If i want to change this value i need to rebuild the simpliciTI library? how i can do this? i'm trying to rebuild the library from this morning with no success :(   

  • 0 in reply to Vinx5
    TI__Guru 64920 points

    Are you using the evaluation version of the IAR Systems Embedded workbench?  If so, you will need to upgrade to the full version as I don't believe the code size limited evaluation version of IAR will allow you to build the SimpliciTI stack (ie. too large) and your application.

    See other thread about this subject as well.

  • 0 in reply to BrandonAzbell
    Prodigy 180 points

    Hello, I have a question. How to upgrade to a full version  IAR system? Thanks. :)

  • 0 in reply to songye ho
    TI__Guru 64920 points

    You will need to contact IAR Systems directly for a quote.  IAR Systems Embedded Workbench is not a product of Texas Instruments.

**Attention** This is a public forum