• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 16 subscribers
  • Views 469 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.

Creating RemoTI Project

Jessica Inocencio1
Intellectual 475 points
Other Parts Discussed in Thread: REMOTI, CC2530, CC2533

Hello,

I wanted to create a project in IAR Workbench IDE on top of the RemoTI Application Framework (RTI). The project that I intend to develop will be developed for the white remote control included in RF4CE hardware kit. The purpose of the project that I wanted to create is similar to the purpose of Basic Remote project from RemoTI software, process key inputs and send the corresponding ZRC command over-the-air to a target node.

The difference is in some few things I wanted to add ( process some of keys that are not been processed in Basic Remote application), change (map differently the special keys as recommanded in RemoTI Sample Application) and exclude (test mode).

I dont want to use RemoTI_OadDemo because I wanted to learn from scratch how to create a new RemoTI project. To build my own project I am guiding through the samples application projects but I am a bit confused about which files from HAL , OSAL and Profile components I have to include in my project.

For OSAL component:
I added to my project those files.
C:\Texas Instruments\RemoTI-CC253xDK-1.3.1\Components\osal\common :
OSAL.c
OSAL_clock.c
OSAL_Memory.c
OSAL_PwrMgr.c
OSAL_Timers.c
C:\Texas Instruments\RemoTI-CC253xDK-1.3.1\Components\osal\mcu\cc2530:
osal_snv.c
OSAL_Math.s51.
I noted that OSAL component files are the same in all of sample application projects. And it made sense for me because I read in RemoTI developer's guide that only HAL component have to be modified to suit the hardware available on our device. So I built OSAL component as a black box.
1. Will OSAL component be the same for any RemoTI project?

For HAL component:
This part have been the most difficult part for me. I am a bit lost between all this HAL files.
2. Will HAL component be the same of Basic Remote Project, once I will use the same resources of hardware?

For Profile component:
3. I wanted to use only ZRC Profile, so that I dont need to include ZID and GDP files, do I?


These files rcn_config.c, rsa.h, rsa_main.c, rsa_osal.c which are included in common group in Application component of Basic Remote Project, they should be included in my project? Why?

I am sorry for this long post and those question, I would be happy if you could answer at least some of them.

Best regards,

Jessica Inocencio

  • 0
    TI__Intellectual 2980 points

    Hi Jessica,

    My apologies for the delay in my response. I think you are in the right track here. I would recommend that you keep looking at the Basic Remote Project for reference.

    About the key mapping, take a look at the rsa_basic_arc.c file in the Basic Remote Project. Starting at line 176 you can look at the rsaKeyMap array. That array basically defines what function is going to perform each button. Check this e2e thread about it (the thread is about the advance remote project using ZID but the concept is the same). http://e2e.ti.com/support/wireless_connectivity/f/159/t/353624.aspx.

    About your questions:

    1. The OSAL component is shared among RemoTI projects.

    2. The hal components are defined by the hardware and the peripherals that you want to use. It might help you to take a look at the target folder (components/hal/target).  Each target includes the necessary files for that particular board and desired functionality.

    For example: The CC2530EB target contains all the required files and configurations to initialize the CC253x 's hardware for the SmartRF05 board. So those hal files will configure the GPIO pins to be either input or output (to match the buttons or LEDs on the SmartRF05  board) etc.

    The CC2533EB_NPI will configure the CC2533E to work as an RNP on the SmartRF05. You will se that in that case the don't include hal_led.c because we don't care about using the LEDs on the board in that project.

    CC2533ARC_RTM configures the CC2533 to interact with all the buttons and leds on the Advance Remote Controller.

    And so on.

    3. It is really hard for me to tell you exactly which files do you need and which files you don't . On IAR, you can right click on files, select options and then select "Exclude from Build", and then you can build the project and check if that file contains dependencies that matter for the sample project. I quickly did this and you can see that rti.c and rti_testmode.c are required from the Profiles folder in IAR, but you will have to look carefully to see what can be remove and what cannot be removed. As long as FEATURE_ZID_CLD (CLD = Controller Device) and FEATURE_ZID are not defined, ZID will not be used. About rcn_config.c, rsa.h, rsa_main.c, rsa_osal I think that if you understand what they do then you will know why the project needs them.

    Regards,

    Jose