...
| Tip | ||||
|---|---|---|---|---|
To speed up the transfer of the OTAP file from the onto the target device, you can switch the network to backbone mode (see SmartMesh IP User's Guide) by entering the following commands on the SmartMesh IP Manager, and then resetting it:
|
...
| Code Block |
|---|
python OtapFile.py --verbose -i ocfdk_02_gpio_net.bin -o ocfdk_02_gpio_net.otap2 --partition 2 --app-id 254 --vendor-id 0 --start-addr 0x41020 --hardware-id 3 Creating OTAP file with the following parameters: - infile : ocfdk_02_gpio_net.bin - outfile : ocfdk_02_gpio_net.otap2 - is_executable : True - do_compression : True - skip_validation : False - hardware_id : 3 - verbose : True - input_file : ocfdk_02_gpio_net.bin - start_addr : 266272 - vendor_id : 10 - app_id : 0254 - partition_id : 2 - output_file : ocfdk_02_gpio_net.otap2 - version : [1, 0, 0, 0] - depends_version : [0, 0, 0, 0] Read input (binary) file ocfdk_02_gpio_net.bin... Stripping kernel header... Compressing data... Creating OTAP header... Writing output (OTAP) file ocfdk_02_gpio_net.otap2... done. |
This generates the ocfdk_02_gpio_net.otap2 file in the same directory.
IDs
The hardware_id, vendor_id, and app_id can be used to target the OTAP process at a subset of devices in the network. You may select your own app and hardware IDs, but to avoid collisions between vendors, Linear is currently managing assignment of vendor IDs. Contact Linear Factory applications (ksaxena@linear.com) for a vendor ID assignment. Devices should only have different IDs when their firmware differs, otherwise you will need to do an OTAP pass for each unique combination of vendor/app/hardware IDs in the network, or use the skip_validation flag to tell all devices in the network to accept the update - note that this could render devices with incompatible firmware inoperable.
Reprogram through OTAP
The OTAP procedure requires you to have the following installed on your computer:
...