nRF Command Line Tools: nrfdfu.dll 32bit version problem when updating nRF9160 firmware

Dear support team,

we use the Nordic nrfdfu.dll (64bit) in our Win11 C#/.Net application for modem update which works fine.
When we switch our application to 32bit process and change to the Nordic nrfdfu.dll (32bit) the modem update functionality no longer works. The communication start between PC application and nRF9160 modem seems to fail and the application hangs until we stop it after some minutes.


Via DllImport we use the following methods of the nrfdfu.dll: 

        [DllImport(nrfDfuDllName, EntryPoint = "NRFDFU_connect_to_mcuboot_target", CallingConvention = CallingConvention.Cdecl)]
        [DllImport(nrfDfuDllName, EntryPoint = "NRFDFU_connect_to_modemdfu_target", CallingConvention = CallingConvention.Cdecl)]
        [DllImport(nrfDfuDllName, EntryPoint = "NRFDFU_program_package", CallingConvention = CallingConvention.Cdecl, CharSet = CharSet.Ansi)]
        [DllImport(nrfDfuDllName, EntryPoint = "NRFDFU_close_connection", CallingConvention = CallingConvention.Cdecl)]
        [DllImport(nrfDfuDllName, EntryPoint = "NRFDFU_verify_package", CallingConvention = CallingConvention.Cdecl, CharSet = CharSet.Ansi)]

Do you have any idea what the reason could be?

Best regards,

Peter   

Parents
  • Hello,

    There is some confusion in the logs you have shared.

    When we look at the logs you posted earlier, the behavior is not the same. There was a failed serial port open call, but the logs you have shared now do not fail at the serial port open call and instead fail later. So, are we looking at two different issues now?

    Also, it seems that you had some log callbacks enabled that printed log messages. Are those enabled here as well?

    Kind Regards,

    Abhijith

Reply
  • Hello,

    There is some confusion in the logs you have shared.

    When we look at the logs you posted earlier, the behavior is not the same. There was a failed serial port open call, but the logs you have shared now do not fail at the serial port open call and instead fail later. So, are we looking at two different issues now?

    Also, it seems that you had some log callbacks enabled that printed log messages. Are those enabled here as well?

    Kind Regards,

    Abhijith

Children
No Data
Related