Migrating to sysbuild with custom board - Hangs in vector table

[siliconwitch]

I'm trying to move my nrf9151 project over to sysbuild (SDK v2.9.1) but when I try to use a custom board definition, the code fails to start up.

So far I've tried debugging this by creating a fresh the zephyr/hello_world example and selecting the nrf9151dk/nrf9151/ns as the target. In this case, everything works fine.

After that, I created a new board using the board creation tool in nRF connect for VSCode, however this version fails to start.

Nothing edited within the new board files. I simply selected nRF9151 and gave it a name.

I compared the new board files to the ones in the <ncs>/zephyr/boards folder, but aside from some uart and io configuration, I don't see any difference. I even commented out the printk, in case it was somehow trying to call a uart handler, but both the proj.conf and sysbuild.conf are empty so I presume logging should be disabled.

Is there something else which I could be missing?

[siliconwitch]

Ah! Found the problem. The nrf9151dk/nrf9151/ns target selects:

board_runner_args(jlink "--device=nRF9160_xxAA" "--speed=4000")

inside board.cmake, whereas when creating a new nRF9151 based board, this becomes:

board_runner_args(jlink "--device=nRF9151_xxCA" "--speed=4000")

Changing this back to 9160_xxAA fixed the issue. Not sure if this is bug, or just not supported yet, but everything seems to be working again