Get: param 65535 invalid error

I’m creating a custom airframe for a custom board. All is going well except on startup I am blasted with many of these messages:
get: param 65535 invalid

I cannot figure out what is causing this. Any ideas on how to debug this?

ulog_messages:
0:29:30 INFO: [logger] logger started (mode=all)
0:29:30 INFO: [logger] Start file log (type: full)
0:29:30 INFO: [logger] [logger] ./log/2021-06-25/19_21_49.ulg
0:29:30 INFO: [logger] Opened full log file: ./log/2021-06-25/19_21_49.ulg
0:29:30 ERROR: [parameters] get: param 65535 invalid
0:29:30 ERROR: [parameters] get: param 65535 invalid
0:29:30 INFO: [ecl/EKF] reset position to last known position
0:29:30 INFO: [ecl/EKF] reset velocity to zero
0:29:30 INFO: [mavlink] using network interface eth0:0, IP: 192.168.0.2
0:29:30 INFO: [mavlink] with netmask: 255.255.255.0
0:29:30 INFO: [mavlink] and broadcast IP: 192.168.0.255
0:29:30 INFO: [px4] Startup script returned successfully
0:29:30 INFO: [mavlink] partner IP: 192.168.0.1
0:29:30 ERROR: [parameters] get: param 65535 invalid
0:29:30 ERROR: [parameters] get: param 65535 invalid
0:29:30 ERROR: [parameters] get: param 65535 invalid
0:29:30 ERROR: [parameters] get: param 65535 invalid
0:29:30 ERROR: [parameters] get: param 65535 invalid
0:29:30 ERROR: [parameters] get: param 65535 invalid
0:29:30 ERROR: [parameters] get: param 65535 invalid
0:29:30 ERROR: [parameters] get: param 65535 invalid
0:29:30 ERROR: [parameters] get: param 65535 invalid
0:29:30 ERROR: [parameters] get: param 65535 invalid
0:29:30 ERROR: [parameters] get: param 65535 invalid
0:29:30 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:31 ERROR: [parameters] get: param 65535 invalid
0:29:32 ERROR: [parameters] get: param 65535 invalid
0:29:32 ERROR: [parameters] get: param 65535 invalid
0:29:32 ERROR: [parameters] get: param 65535 invalid
0:29:32 ERROR: [parameters] get: param 65535 invalid
0:29:32 ERROR: [parameters] get: param 65535 invalid
0:29:32 ERROR: [parameters] get: param 65535 invalid
0:29:32 ERROR: [parameters] get: param 65535 invalid
0:29:32 ERROR: [parameters] get: param 65535 invalid
0:29:32 ERROR: [parameters] get: param 65535 invalid
0:29:32 ERROR: [parameters] get: param 65535 invalid
0:29:32 ERROR: [parameters] get: param 65535 invalid
0:29:32 ERROR: [parameters] get: param 65535 invalid
0:29:33 INFO: [ecl/EKF] 1773427886: EKF aligned, (baro hgt, IMU buf: 12, OBS buf: 9)
0:29:34 INFO: [commander] Failsafe mode activated
0:29:42 INFO: [ecl/EKF] GPS checks passed
0:29:42 INFO: [ecl/EKF] reset position to GPS
0:29:42 INFO: [ecl/EKF] reset velocity to GPS
0:29:42 INFO: [ecl/EKF] starting GPS fusion
0:29:43 INFO: [commander] Failsafe mode deactivated

I’m still unable to determine why this is happening - any ideas here?

Maybe “make clean” and then “make parameters_metadata” before building the firmware would help.

This is related issue: Error with invalid parameters for rovers · Issue #16843 · PX4/PX4-Autopilot · GitHub

To copy the answer: “It’s an uninitialized param handle that was failing silently before. Only the error message is new. I’ll track it down.”