The internal flash layout can be rearranged, but this breaks compatibility withīLE and EasyLink OAD. When TI-RTOS is running from ROM it assumes that there isĬonstant data placed at the beginning of page 1 (0x1000), which means a linkĬonflict occurs when using the default flash layout. Only method being used, then an addition 5.5KB of flash can be saved by using If interoperability is not a requirement and native TI 15.4-Stack OAD is the Default Internal Flash Layout of an OAD Client ¶ Section The default configuration is common across BLE, therefore a CC1350Ĭan be update via BLE OAD or TI 15.4-Stack native OAD.
In addition to this CRC, all data transfers in TI 15.4-Stack are protectedīy a CRC on the link layer so the risk of an undetected data corruption is even The algorithm selected for CRC calculations is the CRC-16-CCITT, it is aġ6 bit CRC calculation that has a 99.9984% error detection rate in Image was not corrupted while sending over the air. If the CRC and CRC shadow are equivalent, the target can assume that the In the CRC shadow field of the metadata vector. The target will re-calculate the CRC of the downloaded image and store the result Later, once the target has received the OAD image, CRC shadow will beĬalculated to determine if the image has been corrupted during transfer. This initial CRC will be sent over the air via the OAD Protocol. Is generated from the toolchain, this will be stored in the CRC field within the First the CRC must be calculated when the image The cyclic redundancy check (CRC) is a means to check the integrity of an image.
This OAD word size isĭefined by EFL_OAD_ADDR_RESOLUTION for off-chip OAD These fields are measured in 32-bit words.ĭescribes an image that is 1024 bytes in size. TI provides a tool to generate an OAD ready image, which contains a metadata Most metadata checking is done in OADTarget_validateNewImage(). This section explains the various fields within the metadata Is embedded at the beginning of the image, occupying the first 16 bytes before In order to prevent this information from being calculated multiple timesĪll TI OAD images use a standard 16-byte metadata vector. The BIM to determine which image should be loaded/executed in the main systemįlash.
To determine whether or not an image is acceptable for download or by Metadata header The information in the metadata header is used by the OAD service All firmware images delivered via OAD are in binary format and contain an image
0 kommentar(er)
