HCI Driver open failed - NRF5340

RE: HCI Driver open failed - NRF5340

Susheel Nuguru — Thu, 22 Feb 2024 07:33:08 GMT

Great to know that changing the speed of debug clock worked. Now back to you initial problem.

[quote user=""]

One (potentially) important point - we recently tried implementing a shutdown feature that calls:

pm_state_set(PM_STATE_SOFT_OFF, 0);

After this was called is when the problem started.

[/quote]

Did you configure a wakeup source? Without a wakeup source and making the chip go to system off will cutoff the debugger access well. System off is the deepest sleep state where most of the regulators are turned off including the one for the debugger clocks.

RE: HCI Driver open failed - NRF5340

jmilliken — Thu, 22 Feb 2024 00:16:29 GMT

Update - I managed to change the debug speed based on this answer and that was worked. I'm all set there, thank you for the help. I would like to go back to the other problem of not being able to use the most up to date SDK and toolchain to see if we can fix that as well.

RE: HCI Driver open failed - NRF5340

jmilliken — Wed, 21 Feb 2024 15:08:18 GMT

Thanks. Regarding the debug link, it does sound like this could be the problem. The J-Link speed is set to 12MHz. I will try Ozone, but for VS Code debugging, how to do I specify the J-Link speed in the launch json?

RE: HCI Driver open failed - NRF5340

Susheel Nuguru — Wed, 21 Feb 2024 06:35:41 GMT

[quote user="jmilliken"]Okay - sorry for all the updates, but this one is probably the biggest clue yet. We had updated the toolchains for this latest build and that seems to be the actual root of the problem. I downgraded to toolchain and SDK v2.0.2 (which was our standard for all previous development), now the BLE is working again. However, I am still not able to get into debug mode.[/quote]

First of all you should not be using such an old SDK for development. It looks like you have some porting issues in your code that compiles OK but seems like not compatible with the changes required for the newer SDK.

[quote user="jmilliken"]

However, I am still not able to get into debug mode. Still getting the SIGTRAP before I get to main. So not completely solved yet. Any ideas?

This is my debug configuration:

[/quote]

Can you check the speed of the debugger, it looks a bit similar to this thread, Can you try debugging with Ozone and see if it works and if nrf-connect is trying to clock the debugger with really high speed. If so, we can change the debugger speed with which nrf-connect ide start to something lower in the configuration file.

RE: HCI Driver open failed - NRF5340

jmilliken — Tue, 20 Feb 2024 15:34:13 GMT

Okay - sorry for all the updates, but this one is probably the biggest clue yet. We had updated the toolchains for this latest build and that seems to be the actual root of the problem. I downgraded to toolchain and SDK v2.0.2 (which was our standard for all previous development), now the BLE is working again. However, I am still not able to get into debug mode. Still getting the SIGTRAP before I get to main. So not completely solved yet. Any ideas?

This is my debug configuration:

{
	"version": "0.2.0",
	"configurations": [
		{
			"type": "nrf-connect",
			"request": "launch",
			"name": "Launch build",
			"config": "${workspaceFolder}/build",
			"runToEntryPoint": "main"
		}
	]
}

RE: HCI Driver open failed - NRF5340

jmilliken — Tue, 20 Feb 2024 15:03:02 GMT

In general, I am getting a SIGTRAP error now when I try to debug:

This is happening even after reverting to an older branch of code that does not use the power down function.

RE: HCI Driver open failed - NRF5340

jmilliken — Tue, 20 Feb 2024 14:24:36 GMT

I did not have that enabled. However, when I enabled it, the application code would not start at all. Without this option, the main app is still running, just no BLE. Another interesting thing happened - when I had this enabled, I was unable to debug. The J-Link connected but the main thread never got to the main() function entry point.

RE: HCI Driver open failed - NRF5340

Susheel Nuguru — Tue, 20 Feb 2024 09:47:53 GMT

The issue seems to be similar to what was described here.

Can you see if you have enabled CONFIG_BT_RPC_STACK=y in prj.conf, prestine build and see if that could be the source of the issue.