I just got a EVKB board and have had great troubles getting a new project to run on the board. After a few hours of swearing, trying different debug probes, trying different PCs and general gnashing of teeth I think I have tracked down the issue.
Something is bad in the default clock_config.c. This is easy to replicate just create a new project, default everything then debug it. It never returns from BOARD_BootClockRun() and the board is also now toast the debugger will not connect to it again, the only way to get it back is to erase the flash and start again:
MCUXpresso RedlinkMulti Driver v10.1 (Dec 19 2017 17:02:15 - crt_emu_cm_redlink build 390)
Found chip XML file in /Development/Teensy/NXP/MCUXpressoIDE_10.1.1/1050/workspace/evkbimxrt1050_driver_examples_gpio_igpio_led_output/Debug/MIMXRT1052xxxxx.xml
Reconnected to existing redlink server (PID 4294967295)
Connecting to probe 1 core 0 (server PID unknown) gave 'OK'
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.183 (NXP Semiconductors)
Serial Number: I3FUJYIR
USB Path: USB_1fc9_0090_222000_ff00
debug interface type = <unknown> (DAP DP ID 0BD11477) over SWD
processor type = Cortex-M7 (CPU ID 410FC270)
number of h/w breakpoints = 8
number of flash patches = 0
number of h/w watchpoints = 4
Probe(0): Connected&Reset. DpID: 0BD11477. CpuID: 410FC270. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE E00FD000: CID B105100D PID 000008E88C ROM dev (type 0x1)
ROM 1 E00FE000: CID B105100D PID 04000BB4C8 ROM dev (type 0x1)
ROM 2 E00FF000: CID B105100D PID 04000BB4C7 ROM dev (type 0x1)
ROM 3 E000E000: CID B105E00D PID 04000BB00C ChipIP dev SCS (type 0x0)
ROM 3 E0001000: CID B105E00D PID 04000BB002 ChipIP dev DWT (type 0x0)
ROM 3 E0002000: CID B105E00D PID 04000BB00E ChipIP dev (type 0x0)
ROM 3 E0000000: CID B105E00D PID 04000BB001 ChipIP dev ITM (type 0x0)
ROM 2 E0041000: CID B105900D PID 04001BB975 ARCH 23B:4A13r0 CoreSight dev type 0x13 Trace Source - core
ROM 2 E0042000: CID B105900D PID 04004BB906 CoreSight dev type 0x14 Debug Control - Trigger, e.g. ECT
ROM 1 E0040000: CID B105900D PID 04000BB9A9 CoreSight dev type 0x11 Trace Sink - TPIU
ROM 1 E0043000: CID B105F00D PID 04001BB101 System dev (type 0x0)
Inspected v.2 External Flash Device on SPI using SPIFI lib MIMXRT1050-EVK_S26KS512S.cfx
Image 'MIMXRT1050-EVK_S26KS512SFeb 21 2018 17:40:48'
Opening flash driver MIMXRT1050-EVK_S26KS512S.cfx
Sending VECTRESET to run flash driver
target failed to halt after flash driver reset
core registers failed - rc Ee(FF). Redlink interface error 255.
chip initialization failed - Ee(FF). Redlink interface error 255.
failed to find a target memory area to use to test the Debug Access Port
required information about vendor NXP chip MIMXRT1052xxxxx not found
Failed on chip setup: Ec(01). Invalid part, XML, or configuration.
error closing down debug session - Ee(FF). Redlink interface error 255.
I have tried this with a machine that has never had MCUXpresso installed before with the new EVKB sdk and get exactly the same problem so I am guessing it is nothing to do with having the EVKA sdk installed previously.
If I use the clock_config.* from the led_gpio example, overwriting the generated one in the new project then everything works fine.