Unable to flash s132 on nRF52832

[AmitChauhan]

I am using TAIYO-YUDEN EYSHCN, which is having Nordic-nRF52832 chip on it. As per document from TAIYO-YUDEN, recommended to flash s132-firmware on it. I downloaded s132_nrf52_3.1.0_softdevice.hex(size-342kb) from nordic site and flashing it using nRF-go studio on region-0, but after flashing it showing only 128kb on region-0.

[endnode]

Hi Amit,

It seems that SoftDevice is flashed. Where is the problem? What do you expect from the module with BT stack only? The vendor is pretty clear in special note (g) that you should write the application yourself.

Cheers Jan

[AmitChauhan]

Ok. But in current situation I need s132_nrf52_2.0.1_softdevice.hex, because by mistake I have overwritten with s132_nrf52_3.1.0_softdevice.hex. I downloaded one(s132_nrf52_2.0.1_softdevice.hex) from devzone.nordicsemi.com/.../c78ef12cb5441592e6d68af1f93779a2 ,but when I am trying to flash It's giving error "invalid softdevice, start address is not 0x00" . It seems, need to find correct softdevice compatible for this device. Because provided CD with the device also not having any firmware as a backup.

[endnode]

You can download any SoftDevice version from Nordic's web site, they are also attached with nRF5x SDK releases. The point is: SoftDevice itself is useless until you develop (= write source code and compile/link into binary) some "application" and flash it on top of SoftDevice. And because you can easily flash both SoftDevice and Application at the same time it doesn't matter what you have in the flash are at this moment. The reason why some vendors ship modules/chips with stack flashed in is that it can safe you some time during production (you just need to flash application binary) but for debugging/prototyping development it's useless.

[Sigurd]

You can download S132 V2.0.1 from here. It can also be found in SDK 11, in the in the folder SDK_folder\components\softdevice\s132\hex. Note that the size of the SoftDevice .hex file is not the same as the actual binary that is loaded onto the chip. The .hex file contains additional metadata about where to load the file, the length of the file, the type of stuff being loaded, etc.

[AmitChauhan]

Thanks For your reply, I did it already... now looking for app which can send and receive message from nRF Android app. Now I have two SDKs (11 and 13). There are multiple examples regarding this. Final objective of mine is... I will connect this BLE-Device with another development board which will send/receive data over UART. And this BLE-Device will send data to mobile phone and can take commands from phone. So currently I am working on to send Data or receive data to phone or receive command from phone using this BLE. Later we will connect with our development board.

[Sigurd]

Yes, there are multiple examples regarding this, the best one is maybe the ble_app_uart example. You can use this example with the nRF Toolbox app.