Lines Matching full:descriptors

3 Binary Descriptors
6 Binary Descriptors are constant data objects storing information about the binary executable.
7 Unlike "regular" constants, binary descriptors are linked to a known offset in the binary, making
9 A few examples of constants that would make useful binary descriptors are: kernel version, app vers…
12 Binary descriptors are created by using the ``DEFINE_BINDESC_*`` macros. For example:
35 Binary descriptors are implemented with a TLV (tag, length, value) header linked
37 but generally the descriptors are linked as close to the beginning of the image as
39 ARM), the descriptors are linked right after the vector table. The reset vector points
40 to the beginning of the text section, which is after the descriptors. In architectures
42 the beginning of the image, in order to skip over the binary descriptors, which are right
70 Binary descriptors are always created by the ``BINDESC_*_DEFINE`` macros. As shown in
78  3. It allows upstream-ability of descriptor generation (see Standard Descriptors)
88 Standard Descriptors
90 Some descriptors might be trivial to implement, and could therefore be implemented
98    # Enable binary descriptors
101    # Enable definition of binary descriptors
104    # Enable default build time binary descriptors
108 To avoid collisions with user defined descriptors, the standard descriptors were allotted
116 Reading Descriptors
118 It's also possible to read and parse binary descriptors from an application.
119 This can be useful both for an image trying to read its own descriptors, and for
120 an image trying to read another image's descriptors. Reading can be performed through
123  #. RAM - assuming the descriptors have been copied to RAM (e.g. by a bootloader), they
129     and is not recommended to read a bootloader's descriptors for security concerns.
131  #. Flash - Using an internal buffer, the descriptors are read one by one using the flash API,
134 To enable reading descriptors, enable :kconfig:option:`CONFIG_BINDESC_READ`. The three backends are
138 To read the descriptors, a handle to the descriptors should first be initialized:
144    /* Assume buffer holds a copy of the descriptors */
159 ``west`` is able to parse and display binary descriptors from a given executable image.