Modifying ble_app_uart from pca10028 to pca20006

[Johnson]

I have customised the ble_app_uart example for my application and the modified code works with the DK board. When I wanted to deploy this to the beacon board (pca20006), I only changed BOARD_PCA100028 to BOARD_PCA20006 in Flash > Configure Flash Tools > Tab C\C++. And it worked immediately on the beacon.

I did not need change the device type to nRF51822_xxAA in tab Device. In fact, when I did, the libraries were marked red and the compiler threw lots of errors.

Why did that happen? I thought the beacon uses nRF51822.

[Johnson]

Yes, I use CMSIS. When I switched to a new device, it created a new folder, s110\arm5\RTE\nRF_Drivers\nRF51822_xxAA, that contained nrf_drv_config.h with GPIOTE_ENABLED disabled. When switching to a new device, the RTEs had red-circles with white x. I had right-click on each h and s file and selected Update Config File (ver 0.0.0 -> ver ..*) to make the red-circles go away. This is a rather long painful process which is more like Keil's problem, not nRF. In the nutshell, what is the proper/correct way of switching to a new device?

[Jørgen Holmefjord]

I guess this is the reason why we stopped supporting CMSIS. If you switch to the no-pack SDK version (you will have to do this eventually if you want to mirate to a newer SDK version), you should be able to switch device without getting these errors. Then you should only need to set the correct RAM/ROM settings.