This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

how to run the experiment nrf52-ble-image-transfer-demo?

Hello dear community !!! I have long wanted to try the nordic chips. I took nrf52840 -preview dk and arducam. I'm still not very familiar with working with the nordic chips. But I wanted something impressive!)). So I decided to try to run the example nrf52-ble-image-transfer-demo. I did everything according to the manual github.com/.../nrf52-ble-image-transfer-demo. I have Arducam 5 MP (but the code did not seem different or am I wrong?) I installed it on nrf52840 -preview dk. Not to join, split solder joints I chose the lateral location of the arducam and connected a wire powered with 5 V. arducam In the post devzone.nordicsemi.com/.../ it is said that you need to connect P0.27->P1.12 on header P4 is it? Because the description did not seem to say anything about it. I tried to flash example nrf52840_xxaa_side_header.hex but nothing happened (I used nRF5_SDK_13.0.0_04a0bfd.zip is taken from here developer.nordicsemi.com/.../ and pre-flashed Board s140_nrf52840_5.0.0-2.alpha_softdevice.hex from this sdk) Then I tried a self build project for this, I installed it on Windows 10 64 bit IAR 8.11.2.13606 and Keil V5.24.2.0. then as it says in the manual I copied the folder nrf52-ble-image-translation-demo-master folder nRF5_SDK_13.0.0-1.alpha_055eef3 ->examples->ble_peripheral.In IAR I opened the project ble_app_uart.eww and the compiler gave me the following errors

Error[Pe235]: variable "__stdout" was declared with a never-completed type C:\Users\kordi\Downloads\nRF5_SDK_13.0.0_04a0bfd\components\libraries\uart\retarget.c 64 Error[Pe235]: variable "__stdin" was declared with a never-completed type C:\Users\kordi\Downloads\nRF5_SDK_13.0.0_04a0bfd\components\libraries\uart\retarget.c 65 Error while running C/C++ Compiler

Keil generally not compiled, wrote that the need softdevice Can you something to help to fix this? More thanks Your great example and all the work. Very nice to write code and to debug.

Parents
  • Unfortunately, support for other camera modules was removed when porting the library to work with our board. Other users have tried this as well without success. You could try adding support for OV5642 from the original library, but I will most likely not work without modifications. The simplest solution would be to get the camera module used by the example. Currently only Keil is supported, but IAR/GCC support might be added in the future. You can also try porting the Keil example to Segger Embedded Studio using this blog post tutorial.

Reply
  • Unfortunately, support for other camera modules was removed when porting the library to work with our board. Other users have tried this as well without success. You could try adding support for OV5642 from the original library, but I will most likely not work without modifications. The simplest solution would be to get the camera module used by the example. Currently only Keil is supported, but IAR/GCC support might be added in the future. You can also try porting the Keil example to Segger Embedded Studio using this blog post tutorial.

Children
No Data
Related