Welcome to the Wireless FRDM Embedded World Workshop

[charlieice]

Welcome to the community page for the March 2025 Wireless FRDM Workshop at Embedded World! This page is where you'll go to post questions if the on-site NXP team is unable to answer your question.

You can also find the pre-work for the Workshop and the binary files required for some of the labs in the Knowledge Base here: https://community.nxp.com/t5/Embedded-World-NXP-Connectivity/tkb-p/embedded-world-connectivity-works...

Thanks for joining us! 

[richard4]

day 2: the eIQ Toolkit in version 14.0 and 13.1 worked.

starting eIQ Toolkit does not work -> splash screen appears, then terminates/crashes.

how to fix

this is a software development machine with lots of tools installed 
it uses ubuntu 22.04. specifically kubuntu.
ubuntu 20.04 eol is may 2025. 

[MartinHerren]

Was the same on Debian for me. Set up a ubuntu 20.04, as you said deprecated, virtual machine for eIQ.

Especially as NXP claims Debian support on their boards, would be nice to support it for the dev environment as well🥰

[MartinHerren]

Hej,

Made some progress on my FRDM-MCXW71 board were I had issues with recognizing the device and flashing the radio firmware from within a virtual machine (it worked for the RW612).

Managed to install most of the mcuexpresso components natively on a bleeding edge Debian install.

Device now properly recognized and successfully flashed the radio firmware.
Also the lab 3 app built successfully.

Now new things to tackle:

Run in debug mode doesn't work:
```
Launching GDB: /home/martin/.mcuxpressotools/arm-gnu-toolchain-13.2.Rel1-x86_64-arm-none-eabi/bin/arm-none-eabi-gdb -q --interpreter=mi2
IMPORTANT: Set "showDevDebugOutput": "raw" in "launch.json" to see all GDB transactions.
/home/martin/.mcuxpressotools/arm-gnu-toolchain-13.2.Rel1-x86_64-arm-none-eabi/bin/arm-none-eabi-gdb: error while loading shared libraries: libncursesw.so.5: cannot open shared object file: No such file or directory
ERROR: GDB not started within the expected 5 seconds. Make sure you can start GDB from the command-line and run any command like "echo hello".
On Linux-based operating systems, ensure "libncurses" and "python" dependencies are satisfied.
GDB session ended unexpectedly: exit code: 127
Launching GDB server: /usr/local/LinkServer_24.12.21/LinkServer -l5 gdbserver "MCXW716CxxxA:FRDM-MCXW71" --probe QDRSKIF0QBZRM --gdb-port 2332 --no-boot --redlink-port 2440 --core primary
Please check TERMINAL tab (GDB server console) for output from "/usr/local/LinkServer_24.12.21/LinkServer"
GDB did not respond to target suspend request. Attempting to end debug session anyway.
```

Little issue as on my laptop I'm already on libncursesw.so.6.... will probably find a solution for this, otherwise I might need to install some legacy laptop on ubuntu 22.04.


Trying to flash the app to the board is more puzzling:
```

INFO: Exact match for MCXW716CxxxA:FRDM-MCXW71 found
INFO: Selected device MCXW716CxxxA:FRDM-MCXW71
INFO: Getting available probes
INFO: Selecting probe by serial substring
INFO: Selected probe #1 QDRSKIF0QBZRM (MCU-LINK on-board (r0E3) CMSIS-DAP V3.117)
INFO: MCU-Link firmware update `check`: not supported on probe ([QDRSKIF0QBZRM] [MCU-LINK on-board (r0E3) CMSIS-DAP V3.117]). Only probes running firmware V3.122 or later can be updated automatically
CRITICAL: Critical error
ERRMSG: Exception: Flash operation exited with code
```

At least i got further ! Best is probably to set up a dedicated laptop for this using the supported ubuntu version.

Thanks again for the interesting workshop and i'll keep playing on those boards !

[richard4]

installing the expresso sdk developer leads to

a) *** Installation completed successfully *** in log

b) sdk not marked as installed in the installer tool

c) the install progress bar nicely goes back to zero after a)

[richard4]

it complains about python missing

anyway the build and debug worked  in the workshop

btw: concerning the labs: the lab 3 for FRDM-MCXW71 failed where the blue led should flash. the instructors said that this should be a error in the example code.

[lorena_lazar]

Hi Richard,

Could you please also attach the log files from  $HOME/MCUXpressoInstaller/logs?

Hopefully, the log files will help us to understand why the python modules are not successfully installed or seen in your setup.

Regards,

Lorena

[kyledando]

@richard4 can you float over the SDK "x" and see the reported issues that render the "x"?
It will include information on the installed tools.  Versions that are found in conflict with the required values to get the Green check mark.

We will review once you provide this information.  Thanks for your patience.

[richard4]

see above

[MartinHerren]

Did you try to restart visual code or the computer after install ?

The installer also let my computer's package manager in a broken state and i had to run `sudo apt --fix-broken install` to get it on track again before managing to finish the install.

[richard4]

hi, i tried several times yesterday and today, the 
sudo apt --fix-broken install  
doesn't fix it

[gebi0207]

Hello - thanks for this nice document - I´ve one problem-during the insatallation there is virus warning:
pegdbserver_console.exe - IDP.Generic is a virus. Norton!
Did you check IDP.Generic? Best regards - gebi0207

[MYBLtd]

Cannot find Matter Chip-tool Smartphone App in ios app store?

[charlieice]

You can also find the lab guides and the binaries for the Matter lab on the Knowledge Base page as well.