nRF52 ANT DFU, hangs at wait_for_events()

RE: nRF52 ANT DFU, hangs at wait_for_events()

Petter Myhre — Fri, 22 Dec 2017 08:00:49 GMT

Were you able to resolve this?

RE: nRF52 ANT DFU, hangs at wait_for_events()

Petter Myhre — Thu, 21 Sep 2017 06:21:17 GMT

Are any modifications necessary to get the bootloader to work on the custom board? If it is, change it as little as possible. Can't you just use the working bootloader hex you are using on the nRF52 on the custom board? It should start in bootloader mode if no application is present. Don't bother with the application now, let's just get the bootloader to work first.

No, the ANT stack will not handle everything. The bootloader is handling the DFU process.

RE: nRF52 ANT DFU, hangs at wait_for_events()

DGraham — Wed, 20 Sep 2017 18:58:08 GMT

I've taken the modifications that were done on the nRF52 DK project and I've implemented them in my current project. If I run things on the nRF52 DK I can connect immediately, and I am able to initialize the upload less than a second after I press upload on the OTA program. On the custom board I can connect immediately,, and when I try to upload it sits at 0%. I tried to look at the logs and it doesn't really give any real information other than the timeout.

Just to clarify, once I'm able to connect via ANT-FS and the OTA Updater program and I click update, isn't everything supposed to be handled by the ANT stack? Even if I force the device into the DFU mode without ever entering the program application it doesn't work. I am still able to connect. Is this a settings issue? Something in the sdk_config.h?

RE: nRF52 ANT DFU, hangs at wait_for_events()

Petter Myhre — Tue, 19 Sep 2017 09:17:12 GMT

Not sure. You are able to do this on the nRF52 DK? With that hex?

RE: nRF52 ANT DFU, hangs at wait_for_events()

DGraham — Mon, 18 Sep 2017 17:02:56 GMT

You were correct, I needed to add the ANT_FS_NETWORK_KEY (and I added the ANT+ network key too). Now I am able to connect to the device, but I am unable to upload an image. It says I have 421888 free space, and my .hex is only 49152.

When I look at the ao_debug_ANTFSHost.txt file, it shows the device being found, has data, has upload enabled, is not in pairing mode, and is a match. It shows some pinging, downloads, and requests, and then it starts "Requesting Upload..." and continues to do so until it says:

" 36.156 { 2422468}: ANTFSHostChannel::Upload(): Timeout. 36.156 { 2422468}: ANTFSHostChannel::UploadLoop(): RETURN_FAIL - 2412937 36.281 { 2422593}: ANTFSHostChannel::Upload(): Tx error sending upload command."

At this point I lose connection and I am unable to reconnect without restarting the device and putting it back into bootloader DFU mode. What should I do to solve this?

RE: nRF52 ANT DFU, hangs at wait_for_events()

Petter Myhre — Mon, 18 Sep 2017 10:58:50 GMT

I'm not sure what those defines have to do with the network key? Have you defined ANT_FS_NETWORK_KEY? It will be all zeroes if not modified, and then I don't think it will work.

RE: nRF52 ANT DFU, hangs at wait_for_events()

DGraham — Fri, 15 Sep 2017 21:35:47 GMT

I haven't tried the bootloader without application code, no. I guess I can try that out here in a minute.

I am using the same bootloader, however I have ANTFS_CONFIG_AUTH_TYPE_PASSKEY_ENABLED set to 0 and ANTFS_CONFIG_AUTH_TYPE_PASSTHROUGH_ENABLED set to 1, so I don't think it's the network key.

I know my application code and my bootloader code have different sdk_config.h files, so is there some conflict I need to be resolving in there or something?

RE: nRF52 ANT DFU, hangs at wait_for_events()

Petter Myhre — Fri, 15 Sep 2017 09:18:49 GMT

I meant without the buttonless application. Only SoftDevice and bootloader. Then you should start in the bootloader directly, but as I said shot in the dark.

There is a trick you can do to be able do debug. If you set optimizations to 0, then increase the amount of flash set aside for the bootloader and set the new start address in UICR. I set the flash start to 0x77000 and size to 0x9000. Then you you can change the BOOTLOADER_REGION_START to 0x77000.

Have you checked with ANTware that the bootloader is actually broadcasting?

Are you using the exact same bootloader firmware on the nRF52 DK and the custom board? If not, could it be that you forgot to set the ANT-FS network key? ANT_FS_NETWORK_KEY

RE: nRF52 ANT DFU, hangs at wait_for_events()

DGraham — Thu, 14 Sep 2017 22:21:30 GMT

I received another one of my custom boards. Same symptoms on that board as the first one. I am able to do everything ANT I could want within the application, but I am unable to connect with the OTA DFU program when I put it into bootloader DFU mode.

RE: nRF52 ANT DFU, hangs at wait_for_events()

DGraham — Thu, 14 Sep 2017 17:15:41 GMT

Yes, I'm using an external crystal with a tolerance of 40ppm.

I don't really follow when you say use the bootloader directly as I am using the bootloader. I am able to parse an incoming ANT event, set a persistent flag, and read the flag in the bootloader. That's how I'm pushing to the DFU mode, but once I progress through that it hangs/times out as I described previously.

I'm going to get another one of my custom boards later today and I will try and investigate if it's a hardware issue, but I don't really understand how it could be.

RE: nRF52 ANT DFU, hangs at wait_for_events()

Petter Myhre — Thu, 14 Sep 2017 13:29:01 GMT

Just to confirm, you have a LFXO witha frequency tolerance less than 50 ppm? It is weird that it works in application code, and on the nRF52 DK as well.

Have you tried to use the bootloader directly? It is a shot in the dark though. Sounds to me like it is some kind of hardware issue, but I'm not sure what. Have you tested with several of these custom boards?

RE: nRF52 ANT DFU, hangs at wait_for_events()

DGraham — Wed, 13 Sep 2017 17:20:28 GMT

Quick update, when I try to debug the DFU stuff I am able to breakpoint up until it enters bootloader_dfu_start(), but I can't breakpoint within the bootloader.c code, so it's hard to get an idea of what is going on in the registers.

RE: nRF52 ANT DFU, hangs at wait_for_events()

DGraham — Wed, 13 Sep 2017 17:09:46 GMT

Hi Petter,

Yes, it works fine on the nRF52 DK. There are a bunch of hardware differences between my custom device and the DK, but ultimately I don't know how they would contribute to this issue. Both are using the nRF52832, but mine is on a custom board without any of the same buttons, LEDs, onboard programming. Mine is using an external crystal that meets ANT spec, uses a different VReg system, connects to peripherals over the TWI interface, etc. etc. Keep in mind, I am attempting to do this buttonless (which I've been able to do on the DK).

Again, the weird part is that I am able to broadcast ANT in the application code, so I don't understand why it wouldn't be able to do the DFU stuff in the bootloader code. Is there something on the hardware side of things that makes DFU possible? What else should I be looking at?

RE: nRF52 ANT DFU, hangs at wait_for_events()

Petter Myhre — Wed, 13 Sep 2017 10:50:57 GMT

So it works perfectly on the nRF52 DK? Any important hardware differences between the nRF52 DK and the custom board?