Searched full:rom_report (Results 1 – 12 of 12) sorted by relevance
37 :goals: rom_report50 :goals: rom_report63 :goals: rom_report76 :goals: rom_report89 :goals: rom_report
14 foreach(report ram_report rom_report footprint)33 foreach(report ram_report rom_report footprint)52 foreach(report ram_report rom_report footprint)
59 west build -b frdm_k64f tests/benchmarks/footprints -t rom_report65 west build -b frdm_k64f tests/benchmarks/footprints -t rom_report
100 Build Target: rom_report107 Use the ``rom_report`` to get the ROM report:113 :goals: rom_report
420 ``rom_report``, ``footprint``, ``puncover`` and ``pahole`` are not exposed.433 location, the ``rom_report`` build target for ``mcuboot`` can be ran438 west build -d build/mcuboot -t rom_report443 using ``ninja`` using sysbuild with mcuboot enabled, the ``rom_report``448 ninja -C mcuboot rom_report453 using ``make`` using sysbuild with mcuboot enabled, the ``rom_report``458 make -C mcuboot rom_report
29 message(" rom_report - Build and create ROM usage report")
7 # size_report. When you call call the ram_report or rom_report targets you
343 * :github:`5348` - rom_report is broken for some environments422 * :github:`5784` - make rom_report fails for qemu_x86 (not finding zephyr.bin)429 * :github:`5853` - Using newlibc in a project breaks 'rom_report' and 'ram_report' targets.
1816 * :github:`15968` - rom_report very imprecise
1465 * :github:`44940` - rom_report creates two identical identifier but for different path in rom.json
2212 * :github:`8108` - make 'rom_report' misreports _sw_isr_table
516 match exactly to the final elf file. See also rom_report,
