Inspect the package before integrating
Obtain a verified C package and its matching feature/class manifest. Compilation and new package generation need the private FICUS service; the integration examples in Deploy are not substitute artifacts. Read the package header and README before selecting a call convention. A trained numeric, stateful or Instinct package can expose a different API from the standalone exact-ordinal Reflex described here.
| Standalone ZIP entry | Purpose |
|---|---|
| <runtime_name>_legal_flash.c | Generated C99 walker and tables; compile for your MCU. |
| <runtime_name>_legal_runtime.h | Actual exported declaration. |
| model.json / release.json / job.json | Graph, receipt and identity bindings. |
| host_only/*.o | Host verification object; never link into Nordic firmware. |
The reviewed standalone header exports no feature-count macro. Obtain the ordered feature count and labels from the matching manifest. Do not infer a path-ID API; its predictor returns a class only. A download’s self-consistent hashes establish content consistency, not independent authentication without a trusted release mechanism.
Add the Reflex to nRF Connect SDK
Use an nRF Connect SDK version supporting the actual nRF54LM20 DK revision. Confirm the qualifier with west boards. Current Zephyr documents nrf54lm20dk/nrf54lm20b/cpuapp; an A-revision board or older SDK can differ. Do not silently substitute another Nordic part and retain the measured-target label.
target_sources(app PRIVATE cards/ficus_card_legal_flash.c)
target_include_directories(app PRIVATE cards)
target_compile_options(app PRIVATE -fno-fast-math -ffp-contract=off)Copy the matching source/header into cards/ and use their real names. Enable FPU support for this target. UART class logs need serial, console and printk settings; floating printk also needs its explicit formatting option. There is no FICUS-specific Kconfig symbol in the standalone package. Choose stack reservation deliberately and then check high-water use: a configured reservation is not measured peak SRAM.
Call with the documented feature order
#include <math.h>
#include "ficus_card_legal_runtime.h"
/* Float32 inputs in the documented manifest feature order.
* Example names/order only: replace with your actual contract. */
const float features[] = { accel_x_rms, accel_y_rms };
/* Reject nonfinite inputs and check manifest count before this unchecked call. */
uint16_t class_id = ficus_card_legal_predict(features);
/* Bounds-check class_id before indexing the matching class-name table. */The standalone call has no length argument or status output. A short array is unsafe; nonfinite inputs violate the declared contract. Preserve the float32 convention and the exact preprocessing, scaling and feature order. In C++ or Arduino code wrap the generated header in extern "C", while compiling the generated source as C.
Use the session-specific integration skill and Deploy snippets to produce a named feature array and class table. The runtime stem must come from the actual package identity, not an arbitrary application nickname. Keep the generated files unchanged so their hashes remain useful.
Replay on the DK, then time the same build
Find the package’s probe vectors and expected classes in its validation artifacts or matching report. A separate probe header is not guaranteed. If vectors are missing, request them; do not invent an all-zero golden event. Replay every supplied vector on the actual DK, compare classes and preserve failures. Include threshold equality and adjacent-float32 probes where provided. This checks implementation parity, not prospective task accuracy.
uint32_t start = k_cycle_get_32();
uint16_t class_id = ficus_card_legal_predict(features);
uint32_t cycles = k_cycle_get_32() - start;
uint64_t us = k_cyc_to_us_floor64(cycles);
/* Keep cycles; integer microseconds truncate short calls. */Record the timer frequency and avoid a full counter wrap. Batch calls for short decisions and make outputs observable to the compiler. Flashing overwrites the current application; obtain authorization and record board, SDK, compiler flags and firmware hash. Measure the linked build rather than copying catalog figures. Release eligibility still needs application quality, resources, safety review and any required repeated charge evidence; exact compilation alone does not grant production approval.
Last reviewed .
Source of truth: published facts in content/public.ts; CURRENT_MEASURED_RESULTS.md; CONNECTED_BUILD_WORKFLOW.md; standalone C emitter and v3 endpoint contract. Reference examples are not physical-board test receipts.