Add support for NXP S32K148 evaluation board

[marcin-wierzbicki]

Add support for NXP S32K148 evaluation board.

The board can be debugged using "west debug" command (see boards/nxp/s32k148_evb/doc/index.rst).

Adapt samples: adc_dt, adc_sequence.
Adapt tests: adc_api, gpio_basic_api, gpio_hogs.

See Add support for S32K148 SoC

[manuargue]

See zephyrproject-rtos/hal_nxp#509

@marcin-wierzbicki please update the hal_nxp entry in the west manifest to point to that pr

[manuargue]

Add driver for TJA1101 PHY device.

I'd recommend to keep this first PR smaller including basic enablement of the SoC and board, and split the PHY driver into another PR for easier review. This will likely also help you to move the prs faster. This is not mandatory, but in general a good practice.

[marcin-wierzbicki]

Add driver for TJA1101 PHY device.

I'd recommend to keep this first PR smaller including basic enablement of the SoC and board, and split the PHY driver into another PR for easier review. This will likely also help you to move the prs faster. This is not mandatory, but in general a good practice.

Sure. Thank you.

[marcin-wierzbicki]

Updated the hal_nxp entry in the west manifest to point to nxp_hal PR.
Moved changes related to nxp_pedbg runner to separate commit.

Please review the PR.

[kartben]

+1 for docs

[manuargue]

As far as I understand, you are proposing a west runner for P&E micro multilink debug probe to be used for NXP S32K1 devices through NXP S32DS IDE... If you plan to support P&E micro debug probe it would make more sense to create a generic runner for it that can work with any chip supported by the probe. Also note that P&E micro multilink debug probe is not from NXP.

If you want to enable a runner for this specific chip, I'd suggest for this first enablement PR to only enable JLink which supports this chip (https://www.segger.com/supported-devices/jlink/nxp/s32k1) and that there's already a west runner for it and move P&E micro multilink support to a separate PR. You can find a reference on how to enable JLink here: https://github.com/zephyrproject-rtos/zephyr/blob/main/boards/nxp/ucans32k1sic/board.cmake#L4-L9

[marcin-wierzbicki]

As far as I understand, you are proposing a west runner for P&E micro multilink debug probe to be used for NXP S32K1 devices through NXP S32DS IDE... If you plan to support P&E micro debug probe it would make more sense to create a generic runner for it that can work with any chip supported by the probe. Also note that P&E micro multilink debug probe is not from NXP.

Right. Let me implement that in a more generic way.

If you want to enable a runner for this specific chip, I'd suggest for this first enablement PR to only enable JLink which supports this chip (https://www.segger.com/supported-devices/jlink/nxp/s32k1) and that there's already a west runner for it and move P&E micro multilink support to a separate PR. You can find a reference on how to enable JLink here: https://github.com/zephyrproject-rtos/zephyr/blob/main/boards/nxp/ucans32k1sic/board.cmake#L4-L9

We tried jlink with these params:

board_runner_args(jlink
  "--device=S32K148"
  "--speed=4000"
  "--iface=jtag"
  "--reset"
)

Both, "west debug" and "west flash" are working. However, "west flash" waits for an input on stdin. After pressing Enter, it finishes about 1 second later and the board is flashed:

-- west flash: rebuilding
ninja: no work to do.
-- west flash: using runner jlink
-- runners.jlink: reset after flashing requested
-- runners.jlink: JLink version: 8.24
-- runners.jlink: Flashing file: ../zephyr/build/zephyr/zephyr.hex

[manuargue]

I don’t have the hardware to test it unfortunately. Judging by https://kb.segger.com/NXP_S32K148#Connect:

The J-Link determines the security state as part of the connect sequence. If a secured device is detected, an un-secure is offered via dialog

You can try adding board_runner_args(jlink "--tool-opt=-autoconnect 1") or else run west -v flash and share the logs to have a look.

For the PEmicro west runner, please do it in a separate PR because is not going to be specific to this device and this PR is getting already too large for a "adding support for NXP S32K148 evaluation board" :)

[marcin-wierzbicki]

You can try adding board_runner_args(jlink "--tool-opt=-autoconnect 1") or else run west -v flash and share the logs to have a look.

We confirmed that these params are correct - no more ENTER needs to be pressed:

board_runner_args(jlink
  "--device=S32K148"
  "--speed=4000"
  "--iface=jtag"
  "--reset"
  "--tool-opt=-jtagconf -1,-1"
)

For the PEmicro west runner, please do it in a separate PR because is not going to be specific to this device and this PR is getting already too large for a "adding support for NXP S32K148 evaluation board" :)

Of course.