How to get pan ID and short id without Target Emulator?
because, i failed to pair the target board to remote control without target emulator after i downloaded the target board. So, if i want to pair remote and target board, i had to get the pan id and short id with target emulator first. and then i could pair remote and target board without target emulator.
thanks in advance
The Target Board is usually mounted with a device running an RNP (RemoTI Network Processor). Whenever a device is power cycled it needs a call to RTI_InitReq() to initialize and start the stack. On an RNP this is called by the host, e.g. Target Emulator, over the serial communication, e.g. UART.
If you do not want to use Target Emulator to generate and send the RTI_InitReq you may use any other tool, like HyperTerminal. The format of the RTI_InitReq() is:
FE 00 4A 03 49
Hope this helps,
Helps us tracking and improving the quality of our support to the community:
if you were satisfied with the answer and of the support, could you please click on 'Verify this post'?
thx for the answer Torbjorn,
i want to ask u again. is it possible if i want to send "FE 00 4A 03 49" without external device? i mean, is it possible if i send it via remote, so i dont need the computer to get the pan ID and short address?
The idea is that this command initializes the stack. The initialization process on an RNP (RemoTI Network Processor) is called by the host over the serial communication chosen. The example I gave is using UART. Since the stack is not initialized; the radio is not on, and the device cannot respond to OTA (over the air) messages.
You could have had a button on the device running the RNP, and have this button press generate a call to RTI_InitReq(). This does however require a modification of the firmware. You could even have it initialize as part of the power-on sequence, again this requires changes in the firmware. Since you have access to the code, the modifications can be done easily. The BasicRemote project initializes the stack this way.
I want to know about this hex code FE 00 4A 03 49? because in RNP interface spec document, it only says 00 4A 03. so what are FE and 49?
still about hex code,
I tried to trace hexs codes that was transferred from remote to Target Board. The Hexs that I found when pressing the play button are:
‘FE 09 4A 05 00 01 FF 8B C0 02 02 02 44 CB’ can you tell me what FE and CB codes are? is this similar case with my question above?
And why the vendor ID always appear as ‘FF 8B’ because TI ID is 0x0007?
Here is the decode:
FE - SOF - Start of Frame CB - FCS - Checksum
Take a look at the RemoTI Interface specification. The document can be found at the following default installation folder:
[C:\Texas Instruments\RemoTI-CC253xDK-1.3\Documents\API\RemoTI Network Processor Interface Spec.pdf]
This is a great document if you are developing with RNP.
LPRF Rocks the World
"Customer Centricity, Enthusiasm, Mass collaboration and Great minds are the best path towards great products"
“Victory awaits him who has everything in order – luck people call it. Defeat is certain for him who has neglected to take the necessary precautions in time; this is called bad luck.” Roald Amundsen, The South Pole
Note; from RemoTI API
Configuration Parameters4.3.1 OverviewThe Configuration Parameters table contains parameters that are configured by the applicationlayer prior to starting the RTI stack. The RTI stack reads these parameter values during theinitialization API call. Any modification of these values while the RTI stack is operational will nottake effect until the next RTI stack initialization.
So, after you have written your configuration values; in your case PAN ID and short address, be sure to call RTI_InitReq(). Please refer to [C:\Texas Instruments\RemoTI-CC253xDK-1.3\Documents\API\RemoTI Network Processor Interface Spec.pdf] for detailed explanation of the RPC calls.
Ok, I got it. but, I am not really sure if i have to write the value of PAN ID and short address for configuration since they will be configured by system randomly (CMIIW) refer to RemoTI API section 4.4. Thanks to you Torbjorn this problem has been solved. I configured StartupOption, DeviceTypeList, FrequencyAgility then I called RTI_InitReq().
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.