Firmware Fn db find node

db_find_node

Part of Firmware Reversing.

• String location: file offset 0x9073fd (plain debug-string scan, not the symbol table)
• Status: ⚪ Name only — no code address found
• Related debug strings: fp_db_find_node, fp_db_find_node_from_draw_map, fp_db_find_node_from_complete_parcel (variant accessors — one specifically for resolving a node "from the drawn map," i.e. a currently-loaded tile, another "from the complete parcel," i.e. a full, not partially-loaded, tile), plus a real runtime error-log context ("g: db_node(i_toNode, &vNode) != ARR_SUCCESS") confirming a real, live db_node() call site exists somewhere, loading the actual VNode structure once the right parcel is known.

Once db_vid_get_map_id_V000/ db_vid_get_pcl_id_V000 resolve which tile, this is the accessor named for actually loading the node from it — the step right before readNodeMP0/getNodeVidArmMP0 in the real pipeline.

Why there's no address

Same confirmed structural reason as the db_vid_get_* pair — see Firmware Reversing for the full writeup. Zero matches from either the lis/addi cross-reference scan or a whole-file literal-pointer scan.