peripheral_hids_keyboard sample: Different flashing behaviour in Vscode vs Ozone

RE: peripheral_hids_keyboard sample: Different flashing behaviour in Vscode vs Ozone

Benjii519 — Sat, 01 Jun 2024 01:31:25 GMT

Ok! I had some time to dig further into this over the last few days and I've figured it ou.

There were two issues.

The first issue: vscode was not flashing correctly over jlink (and Ozone was). This was due to the default board settings. Updating the config with these settings resolved that:

CONFIG_BUILD_OUTPUT_UF2=n

CONFIG_USE_DT_CODE_PARTITION=n

The second issue: Ozone hard fault after resuming a breakpoint. This was the issue that you pointed out. It doesn't happen in VCS because monitor mode debugging is used. If I enable that in Ozone, I get the same behavior (no hard fault)

Exec.Command ("SetMonModeDebug = 1");

RE: peripheral_hids_keyboard sample: Different flashing behaviour in Vscode vs Ozone

Charlie — Thu, 30 May 2024 13:39:46 GMT

Hi Benjii,

[quote user="Benjii519"]But then why do breakpoints in vscode work? How are the two setups different?[/quote]

This depends on where you set the breakpoint. If you set it into time sensitive tasks, for example

err = bt_le_adv_start(adv_param, ad, ARRAY_SIZE(ad), sd,

ARRAY_SIZE(sd));

you will get hard fault.

[quote user="Benjii519"]Where working state is: I can see the LED flashing, attach VScode debugger + verify),[/quote]

Do you define working as programming firmware into a device? LED means LED5 here?

For VS Code debugger, when you start the debugger, it will start download immediately. Make sure there is no another debugger already running.

For debug with Ozone, it supports download a firmware to do debugging(Debug->Start Debug Session->Download & Reset Program) or you can "Attach to running program" already start by VS Code debugger.

Just let me know if I have any misunderstanding. I can try to repeat the issue on my side.

Best regards,

Charlie

RE: peripheral_hids_keyboard sample: Different flashing behaviour in Vscode vs Ozone

Benjii519 — Tue, 28 May 2024 09:54:11 GMT

The other odd thing here (and I can open another ticket if thats helpful) is that flashing the sample isn't quite working.

It seems like Ozone and VsCode are each doing something slightly different, but both are required to get the sample in a working state.

eg:

- if I flash with Ozone alone -> not working

- if I flash with vscode alone -> not working

- if I flash with Ozone and then vscode -> working (as long as I don't do a full erase)

Where working state is: I can see the LED flashing, attach VScode debugger + verify),

I'm guessing Ozone is flashing some piece than VScode is missing and vice-versa

RE: peripheral_hids_keyboard sample: Different flashing behaviour in Vscode vs Ozone

Benjii519 — Tue, 28 May 2024 02:14:11 GMT

But then why do breakpoints in vscode work? How are the two setups different?

RE: peripheral_hids_keyboard sample: Different flashing behaviour in Vscode vs Ozone

Charlie — Tue, 07 May 2024 11:54:18 GMT

Please see this discussion:

(+) Ozone debugger causes hardfault - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)