FUOTA with periodical uplink example frequently fails

[jonghao112-design]

success log.txt

fail log.txt

Hi,

I'm having trouble with frequent failures when running a simple FUOTA campaign. Here are my setup details:

I'm using an STM32 L476 with an SX1262 shield and a Multitech gateway (US915 region). The application is the "periodical uplink" example, with all FUOTA macros enabled as instructed in the README.md. The FUOTA version is 1.0, and the device is configured for Class C.

My main issue is that the FUOTA process often fails, printing the error: "class C[0] BAD DevAddr=0xf0da90f4 instead of 0x1eaf013". I have attached two log files—one from a run that seemed normal and another from a failed attempt.

Is there a known issue or a specific configuration step I might have missed? I would greatly appreciate any guidance or clarification on what could be causing this DevAddr mismatch and how to resolve it.

Best regards,
hjing

[lbm-team]

Hi,
Could you please precise which LBM version you are using ?
Many thanks,
Best regards

[jonghao112-design]

Hi, Could you please precise which LBM version you are using ? Many thanks, Best regards

Hi,
The attached logs were captured during testing based on LBM version 4.8.0. Later, I also tested with the latest LBM version 4.9.0, but the same upgrade failure issue still occurred for some unknown reason.

[jonghao112-design]

It seems that the FOTA process of the Multitech gateway differs from the standard one. As shown in the image, here is the reply from their technical support, which mentions the use of an all-zero McKEKey. As far as I understand, a normal McKEKey should be calculated through GenAppKey, right? How should I modify it to adapt to their logic?