- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 1989036_en-US
1989036_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
1989036_en-US
1989036_en-US
I am trying to get a debug connection to the Cortex-M33 on the iMX93EVK board, using a SEGGER J-Link. I want to be able to debug while Linux is running on the A55.
I tried debugging the hello_world demo app on the M33 while the A55 is in U-Boot, following the instructions in AN14120. The U-Boot commands:
fatload mmc 1:1 80000000 sdk20-app.bin
cp.b 0x80000000 0x201e0000 0x10000
bootaux 0x1ffe0000
start the firmware and the output shows up on the serial port. But when I try to connect using the SEGGER JLinkGDBServerExe it fails to find the device. The log shows this:
02-00000000-00-00000041-004D: TB9DF640 005:451.096 ******************************************************
02-00000000-00-00000041-004A: TB9DF640 005:451.097 J-Link script: i.MX93 Cortex-M33 core J-Link script
02-00000000-00-00000041-004D: TB9DF640 005:451.098 ******************************************************
02-00000000-00-00000042-0034: TB9DF640 005:451.523 InitTarget() end - Took 426us
02-00000000-00-00000042-004D: TB9DF640 005:452.146 TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
02-00000000-00-00000044-005B: TB9DF640 005:453.793 Failed to identify target. Resetting via Reset pin and trying again.
It uses the iMX93 J-Link script but fails to connect to the target. Attach from VS Code (with MCUXpresso extension) also does not work.
I get the same result when I try to debug while the A55 is in Linux (after changing the kernel DTS to disable lpuart5).
Only when I put the BOOT_MODE to Cortex-M33 (Infinite Loop) can the J-Link find the device, and I can debug the demo app using VS Code.
Why doesn't the J-Link detect the target with the A55 in U-Boot or Linux?
Regards,
Sander
The solution to this problem was to switch off the UART5 from JTAG on the board with the DIP switches SW101.
The kernel version we build is imx-6.6.36-2.1.0.
I do not know which pre-build image, it came pre-installed when we bought the EVK. It prints "NXP i.MX Release Distro 6.6-scarthgap imx93evk ttyLP0" on startup, and "Linux version 6.6.36-lts-next-gd23d64eea511" on /proc/version
Under which name would the UART5 show up in /dev? There is a /dev/ttyLP0, would the UART5 show up as /dev/ttyLP5 or some other number?
HI @Sander-ET!
What kernel version are you compiling in Yocto and what pre-build image are you using?
You can corroborate if the UART5 is not working if the UART is not listed in the folder /dev/ of the iMX
For the Cortex-M33 we are using the MCUXpresso SDK from git (MCUX_2.16.100). We try to start the debugger from Visual Studio Code, using the MCUXpresso extension. We tried the right-click Attach and Debug, both fail to connect but reset the board.
For the Cortex-A we build an image using imx-docker (MACHINE="imx93-11x11-lpddr4x-evk", DISTRO="fsl-imx-xwayland", IMAGES="imx-image-core"). We boot this from SD card. The device tree has been modified to disable lpuart5. Is there a way to verify from Linux that lpuart5 really is disabled?
We also tried to debug booting the original (demo) image in eMMC with the A55 in U-Boot. We get no JTAG connection with this image either.
The suggested change of the u-boot environment did not help.
Regards,
Sander
HI @Sander-ET!
What BSP are you using?
Do you tried to right-click the project in the MCUXpresso for VS Code and choose "Attach to debug the project"?
Also you can update the environment of u-boot like we recommend in this post.
Best Regards!
Chavira