migrating to S310

Question

What I'm using: PCA10028 (nRF51422), SDK 7, Keil uVision 5, moving SD S110 v7.1 to SD 310 V2 
 I used the ble_app_lbs project as a template. Being a newbie to both BLE and ANT - the ble_app_lbs project turned out to be a very good starting point for me. This project used the S110 stack, so that's what I've been running. 
 I'm far enough along, that I now need to start implementing ANT. I assumed all I would need to do is reprogram my board with the S310 stack, and in Keil go into the Options Panel/Device Tab and select the nRF51422 device. With these settings, I get a Flash Download Failed - "Cortex-M0" error. 
 I'm sure the problem is how the project is set up. Keil's device drop down menu bar is still showing: nrf51822-xxaa_s110 (256K). The only other device listed in the 128K version of the 822. 
 So... Is there any easy way to migrate a Keil project from the s110 stack, to the s310? 
Thanks

c cook · Accepted Answer

Stefan - I edited my original post. Yesterday I aquired a PCA10028, board. Installed SDK 7, and I'm using S310 version 2 stack. I also set my memory options as described in the S310_nrf51422_2.0.0_migration_guide PDF 
 as the user in your post I'm getting some errors that I can't seem to fix:
ble_gatts_enable_params_t; and ble_enable_params_t; were undefined I copied their definitions over from my original project, but I don't know if that was the correct thing to do, or why they are no longer defined. 
 sd_ble_enable(...); is now declared implicitly - What header file is it found in? S310 documenation lists the this call. 
 sd_ble_gap_address set (...) says I have too many arguments - I still have the same two I was using from the s110 stack and the S310 documentation shows the same parameters 
 BLE_GAP_ADDR_CYCLE_MODE_NONE is no longer defined. 
 ~~~~~~~~~~~~~~~~~~~~~~~~ Resolved ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SDK 7 gets installed in the Keil directory. After adding the new paths, so my code was looking in the Keil directories - instead of the SDK 6 directory, my errors went away.