RE: aes crypt hangs

Matthew E. — Tue, 21 Jan 2014 16:12:01 GMT

Yes, sorry, I meant to delete this question, as I determined exactly as you wrote a few hours later. thank you!

RE: aes crypt hangs

Ole Morten — Tue, 21 Jan 2014 09:02:11 GMT

When using the softdevice, you need to make sure to not use blocks that are listed as restricted or blocked directly from your application. If you do, you'll see a HardFault. You can see a list of these peripherals in the SoftDevice Specification, and the ECB block is one of them. This is the reason taht the nrf_ecb_* functions fail. (If you halt the device with the debugger after having tried to call one of these functions, you should be able to easily see that it hangs in the HardFault_Handler of arm_startup_nrf51.s.)

As for the reason for sd_ecb_block_encrypt() "fails", I suspect that what you see is that debugging isn't really possible when any time critical activities have been started with the softdevice (advertising, connection). This has been discussed at length here previously, for example here and here. If however you run this AES code before starting advertising or a connection, you should be able to debug this code as you want.