• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 572 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.

Removing Evaluation Board related code from SimpleBLEPeripheral project

Joe Bloggs
Intellectual 400 points
Other Parts Discussed in Thread: CC2541, CC2540

Hi,

I have recently ported my code over to v1.4 stack and am having problems not only with IAR ("Failed to fit all Segments into specified ranges...") but I'm also seeing a number of errors relating to Hal-Key and Hal-LCD and Hal-LED definitions.

I can't see a definition of these anywhere in my project or the IDE;

#define HAL_LCD

and #define HAL_KEYS  

and HAL_LED

These are not turning up when I search for them in my (now v1.4) project OR in the Project OPTIONS (Category=C/C++ Compiler (tab) Preprocessor, Defined Symbols).....

Has anyone attempted to 'clean' the Simple BLE Peripheral' reference design (software) so that anything relating to LCD and KEYS are removed from the project... Mine has neither of these as it is a 'Peripheral' device with no physical input or outputs.

I get the feeling that this isn't going to be easy task as there are references to these definitions all over the place. It would be useful if anyone can point me to where these are #defined, so that I can comment them out and let the conditional compilation just ignore these.. At least to get my code to compile if not to save the overhead of code space in my project, which is less important at the moment.

Thanks in advance.


Ps.

IAR.... What were you thinking when you decided to make various elements of the OPTIONS screen the size of an ATOM, I have a 27" screen and the Project OPTIONS screen forces me to scroll up and down tiny boxes to see what my setting are. Honestly, you guys have no idea what it is like developing with your tools  and the EW8051 IDE is really getting on my nerves!!

And what is the point of having the Assembler Window continuously force itself on top of all the other useful windows during debug???? What is the point of having a C-Compiler/Environment if 1/3 of your screen is continuously being hijacked by the Assembler View ??? If I wanted to work in an Assembler environment, I wouldn't buy a C-Compiler!!!     Please..... Disable this window from forcing itself to the 'top' in future releases of your already sub standard, crippling IDE...... I would much rather be looking at a Watch Window when I'm debugging and if I want to see the Assembler version of what I can see in the other 2/3 of my window I should have the option to choose to do so..

  • 0
    TI__Guru** 105180 points
    Hi Joe,

    Which simpleBLEPeripheral project config are you using? The "CC2541" config does not use keys. This is the config for the CC2541EM. The LCD is supported, but can be disabled by undefining the HAL_LCD from the predefined symbols. With these options disabled, are you seeing references in your map file?

    For IAR feedback, it would be helpful to bring this to IAR directly.

    Best wishes
  • 0 in reply to JXS
    Intellectual 400 points

    Thanks for this information JXS.

    My design is based around the CC2540 (as per tags included with my post). I'm not sure that it would be a good idea to use the CC2541 as reference (to disable the keys) given that I will want my code to work on the CC2540. They use different DDF files don't they? And memory maps may be different. Besides that would only solve half of my problem (just disables 'keys' functions, as you say not LED and LCD).

    Yes, you're probably right about my IAR feedback comments but, as far as product development with TI BLE is concerned, they are one of the same, no? Should I go and file a separate post at some other dedicated IAR web-site to notify IAR or do you think IAR might be reading these posts anyway?

    Where is the IAR (compiler) dedicated forum anyway?

    Thanks.
    JB.

  • 0 in reply to Joe Bloggs
    TI__Guru** 105180 points
    Hi,

    For CC2540, the same logic applies. Only the CC2540_MINIDK configuration includes support for keys. If you are using the "CC2540" project config, you should not include any key handling logic. The same logic applies for HAL_LCD / HAL_LED support. Did you check your map file?

    Note that IAR is independent of TI. It may be more productive to provide your feedback to IAR directly at IAR.com.

    Best wishes