No CPU load information QGControl

Hello. Im just starting with PX4 and during first arming procedure i run into a problem.
Trying arming a drone. Via telemetry i get this error every time “Critical: Fail: No CPU load information”. Maybe someone know where shearch cause of this problem, or is able to direct me where to look for a solution?
Zrzut ekranu 2021-08-25 161328

Hi @MSStukan, the CPU load is probably a module not running and/or present, you can check in your mavlink console and type top once to check cpu load (you can check the system modules here Commands · PX4 Developer Guide), most of the time it should be running upon powering up the FC, could you let us know

  1. What board you use?
  2. What firmware you are using?

I encountered the same problem when using a banggood pixhack 2.4.8 and running the v1.12.1 latest release. Downgrade to v1.11.1 solved the problem


Problem solved. I my case problem was in " version of bootloader in version firmware". What i mean …

In first circle we have main version in second circle we have bootloader version.
If we have newer version of pixhawk1 (2MB Flash) version v2 may not working but not always. In my case worked reload bootloader ->change variable SYS_BL_UPDATE to 1 and load again firmware which led to load v3 bootloader version.
Redirecting to latest version of document (main) :wink:

1 Like

@MSStukan @Zhengtian_Ma

I encountered this problem on a Pixhawk 1 vehicle controller version 2.4.8 as well. I had no issues though, operating this drone with a stable version of PX4 but from one test flight to the next, I started to get the error “No CPU load information.”

All that I had done from the UAV working fine to it producing this specific error was to remove the SD card so I could grab some log files and then I changed the SDLOG_PROFILE parameter setting from “default” to “default” and “high rate.”

This seemed to work and solve the CPU issue! but I was wondering what does this version (SYS_BL_UPDATE) of boot loader does that is different from the standard boot loader and if I’ll have to do this every time I flash my FMU? I find this so fascinating how it fixed the CPU load issue but have no idea how lol. Could the standard boot loader cause the CPU load problem or does something else like mechanical or software cause it? It would be cool if the boot loader works with all versions of PX4 (and what in the world is NUTTx OS version, does it matter?) but I wonder if it’s only certain ones.

Hey everyone, it looks like you all have one thing in common, which is older versions of hardware, you should update your bootloaders as instructed above, whenever there’s a new update, our bootloader updates are fairly stable and typically have security or performance updates to them which you might be benefiting from.


I encountered this problem recently and found another solution to the issue.

By default I was using the newer px4_fmu-v3_default.px4 boot-loader and also using PX4 FMU V2 build on an older Pixahawk and still running into issues. While I wouldn’t recommend this method if your board supports an easy way to collect CPU load information, I couldn’t for the life of me find out if my board had this feature let alone enable it (an older, proprietary board with limited info).

If you are able to connect your autopilot to a ground control station (e.g. QGroundControl), you should be able to find the COM_CPU_MAX parameter in your vehicle parameter page. Alternatively you can just search “CPU” on the same page. The description should say that the value can be set to something negative and this will disable the check.

Hopefully this helps if the issue keeps occurring.