Does the PC app “RemoTI_OadDemo.exe” only accept Vendor ID '0x0007' (= TI) ?

Hi William,

The OAD protocol is a TI vendor specific protocol. We transmit using the ZRC vendor specific packets. These are identified by the Vendor ID and the vendor specific flag. It can be modified to work with other Vendor IDs, but the OAD PC Server will only support TI.

You can use TI's vendor ID in a vendor specific packet without the stack being configured to use that. At least our API supports that.

void RTI_SendDataReq(uint8 dstIndex, uint8 profileId, uint16 vendorId, uint8 txOptions,
uint8 len, uint8 *pData);

Hi Torbjorn,

Noted with thanks.

[Q1]: If I want to use specific VendorID (other than 0x0007), is it mean that need to modify the PC's RemoTI_OadDemo.exe ?

[Q2]: any access to source code or example for application similar to RemoTI_OadDemo.exe ?

Thanks & Best Regards,

William

Hi William,

We have a Linux OAD server that is easily modifiable.

4314.oad_v1.0.17.zip

Installation instructions:

Place both *applicationName* files in an empty directory in your Linux environment, e.g. <installDir>, then:

$ cd installDir
$ ./install_applicationName_v1.0.11.sh
$ cd RemoTI-Linux/Projects/tools/LinuxHost/application/applicationName
$ make
$ ./out/MSO_lnx_x86_client –D 127.0.0.1:2530

Notes:
- The make step will attempt to cross compile for two armv7 platforms. It will exit with an error if those cross compilers are not found. This is not an issue, as the x86 version will still be built. You may modify the makefile to use your cross compilation tool instead, and hence you will compile the application to run on your platform.
- To run the application at least one NPI Server must be running on the network. The NPI Server is the Linux driver for TI LPRF. It translates the serial interface into a socket interface. NPI Server is part of what is being installed when you run the installation script as shown above. You may try out on a computer by programming a CC2531 USB Dongle with an MSO RNP image. Then connect the dongle to the computer. Find how the dongle enumerated by running ls /dev/tty*. Based on this select the proper configuration file. The following steps assumes that the dongle enumerates as device /dev/ttyACM0:
$ cd <installDir>
$ cd RemoTI-Linux/Projects/tools/LinuxHost/
$ make
$ ls /dev/tty*
$ ./out/NPI_lnx_x86_server configuration/x86/RemoTI-RNP_ACM0.cfg
- The -D option takes <IP Address>:<Port> as argument. If you are running the application on the same device as the NPI Server is running then you may use the loop back address 127.0.0.1. The port is selected when running the NPI Server, it is defined in the configuration file NPI Server takes as argument. In the example above the port was set to 2530.

Hi Torbjorn,

Thank you for posting the Linux based OAD code.

But, our customer is using Windows OS based PC for the code upgrading via OAD.

Can you also provide the Win7/8 based RemoTI_OadDemo.exe source code + library to us ?

Thanks & Best Regards,

William

Hi William,

I can provide this source directly, not via E2E. Please send me an email, or provide yours.