nRF51 Dongle to Taiyo Yuden EBAGJNZXX eval board

Question

I have a working/functioning project running on the nRF51 dongle that I want to develop for production. To save a step in FCC certification I am developing on an FCC approved module from Taiyo Yuden, EBAGJNZXX.

The dongle has a 16MHz crystal and the TY board has a 32MHz crystal.

I have changed:

system_nrf51.c

#define __SYSTEM_CLOCK (32000000UL) /*!< nRF51 devices use a fixed System Clock Frequency of 16MHz */
//#define __SYSTEM_CLOCK (16000000UL) /*!< nRF51 devices use a fixed System Clock Frequency of 16MHz */

skd_congif.h

#if CLOCK_ENABLED
// <o> CLOCK_CONFIG_XTAL_FREQ - HF XTAL Frequency

// <0=> Default (64 MHz)
// <255=> Default (16 MHz)
// <0=> 32 MHz

#ifndef CLOCK_CONFIG_XTAL_FREQ
#define CLOCK_CONFIG_XTAL_FREQ 0
// #define CLOCK_CONFIG_XTAL_FREQ 255

which was all I could find that was relevant to the XTAL change.

The firmware uploads suceesfully but doesn't run:

openocd programming logs:(chip erased before writing as this seems to effect the radio functionality on the dongle)

DONGLE:

Flash app with softdevice
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
   openocd.org/.../bugs.html
cortex_m reset_config sysresetreq
adapter speed: 1000 kHz
adapter speed: 3000 kHz
Info : No device selected, using first device.
Info : J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 12 2018 16:05:20
Info : Hardware version: 1.00
Info : VTarget = 3.300 V
Info : Reduced speed from 3000 kHz to 1000 kHz (maximum).
Info : Reduced speed from 3000 kHz to 1000 kHz (maximum).
Info : clock speed 3000 kHz
Info : SWD DPIDR 0x0bb11477
Info : nRF51822.cpu: hardware has 4 breakpoints, 2 watchpoints
    TargetName         Type       Endian TapName            State
-- ------------------ ---------- ------ ------------------ ------------
0* nRF51822.cpu       cortex_m   little nRF51822.cpu       halted
auto erase enabled
Info : nRF51422-QFAC(build code: A1) 256kB Flash
Info : Padding image section 0 with 2112 bytes
Warn : not enough working area available(requested 32)
Warn : no working area available, falling back to slow memory writes
wrote 110592 bytes from file s130_nrf51_2.0.1_softdevice.hex in 17.862696s (6.046 KiB/s)
auto erase enabled
Warn : not enough working area available(requested 32)
Warn : no working area available, falling back to slow memory writes
wrote 79872 bytes from file Debug/kbd.bin in 12.884310s (6.054 KiB/s)
shutdown command invoked

TY eval board:

Flash app with softdevice
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
   openocd.org/.../bugs.html
cortex_m reset_config sysresetreq
adapter speed: 1000 kHz
adapter speed: 3000 kHz
Info : No device selected, using first device.
Info : J-Link Lite-Cortex-M V9 compiled Feb 2 2018 18:14:01
Info : Hardware version: 9.00
Info : VTarget = 3.324 V
Info : clock speed 3000 kHz
Info : SWD DPIDR 0x0bb11477
Info : nRF51822.cpu: hardware has 4 breakpoints, 2 watchpoints
    TargetName         Type       Endian TapName            State
-- ------------------ ---------- ------ ------------------ ------------
0* nRF51822.cpu       cortex_m   little nRF51822.cpu       halted
auto erase enabled
Info : nRF51422-CFAC(build code: A0) 256kB Flash
Info : Padding image section 0 with 2112 bytes
Warn : not enough working area available(requested 32)
Warn : no working area available, falling back to slow memory writes
wrote 110592 bytes from file s130_nrf51_2.0.1_softdevice.hex in 33.366196s (3.237 KiB/s)
auto erase enabled
Warn : not enough working area available(requested 32)
Warn : no working area available, falling back to slow memory writes
wrote 79872 bytes from file Debug/kbd.bin in 24.108545s (3.235 KiB/s)
shutdown command invoked

I noticed there is a difference in the device name and the "build code" but couldn't find any information on how that might effect things.

Any help would be much appreciated.

Note: that device is basically a keyboard, with a few little changes

Thanks!