Hello, From nrfxlib\bsdlib\include\nrf_errno.h
#define NRF_EINVAL 22 /**< Invalid argument */
I've had no issues with the AWS FOTA sample (tested yesterday). Can you please provide the output from i.e. LTE Link Monitor? Kind regards,Øyvind
OK, here's the output
Ok, that did not give much more information on how to solve this.
Did you try to revert back to the original project? Were you trying to download from S3 bucket?
Please confirm all settings in AWS given in the documentation
"git diff" only shows the changes to prj.conf that I showed above and certificates.h, which are necessary to get it to work.
I am using an S3 bucket for the update and the job file but mqtt_connect is before it gets to that point.
1. Yes, the client ID on AWS is also "nrf9160dk"
2. Yes, I am using the sample policies from https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/nrf9160/aws_fota/README.html#nrf9160-aws-fota for both the thing and the S3 bucket
3. Yes, the endpoint at AWS IoT -> Test -> View Endpoint is also "ahykgwaormc93-ats.iot.us-west-2.amazonaws.com".
The device was able to connect to AWS MQTT before, and I haven't changed anything, so the client ID, hostname, and certificates should work.
icampbell said:The device was able to connect to AWS MQTT before, and I haven't changed anything, so the client ID, hostname, and certificates should work
It the device was able to connect before, then you must revert any changes done before losing connection.
At first, the device got stuck as it was downloading the firmware update, at 2%. I was able to fix this by setting CONFIG_DFU_TARGET_MCUBOOT_SAVE_PROGRESS=n. After that, the download got stuck at around 11%, though that number changed a bit each time I ran it. While I was trying to fix that, the device stopped being able to connect to AWS at all, even though I didn't change anything.
I suggest reverting the sample to the original git hash and provide information on what happens when the download gets stuck. Are you using NB-IoT or LTE-M?