Good afternoon all, I have been using the MCUXpresso IDE with no issue on a Windows 10 system however, I recently installed this IDE on a Linux computer (Ubuntu 18.04.3 LTS) and found an interesting issue! At first, I thought it was a simple debug configuration issue, verified debug configuration against the Windows machine nothing too obvious was found. Here is my summary so far:
- ok - Installed MCUXpresso IDE v11.1.1 [Build 3241] [2020-03-02] on Elementary OS
- ok - Installed CMake
- ok - Installed gcc-arm-none-eabi-9-2019-q4-major (to troubleshoot)
- ok - Installed SDK_2.x_FRDM-KE06Z (2.7.0 Mcuxpresso 303 2019-12-19)
- ok - Installed PEMicro linux driver for FRDM board (linux_drivers_64bit_58_b181128)
- ok - added read/write rights to serial connection (ttyACM0 and ttyACM1)
- Open blinky example from SDK
Issues --> - built project
19:09:29 **** Incremental Build of configuration Debug for project frdmke06z_led_blinky_1 ****
make -r -j8 all
make: Nothing to be done for 'all'.19:09:29 Build Finished. 0 errors, 0 warnings. (took 621ms)
- failed debug using default PEMicro launch setting
P&E Semihosting Console. Connection closed by the GDB server.- debugger console reads "monitor setexceptioncatching 2033
- monitor selectcore 0
- Ignoring packet error, continuing...
- modifying GDB settings with
${cross_prefix}gdb${cross_suffix}
gets a little farther but still fails to initiate the breakpoint and step throug debug mode
I read through Connection closed by the GDB server and Eric's awesome mcuoneclipse tutorials and not having success! I am suspecting a serious GDB configuration issue I am missing here!
I appreciate anyone's help!
Thank you for the suggestion, I tried this:
changed it to path in /ide/tools/bin and that did not work either. See errors below:
Could not determine GDB version after sending: /home/michael/Downloads/mcuxpresso-ide/pkg/mcuxpresso-ide/usr/local/mcuxpresso-ide/ide/tools/bin/arm-none-eabi-gdb --version, response:
Thank you for that note. I went back and changed it only in the debugger tab, the error is the same now.
Initially, this was the same error I got when I first installed the IDE. After installing arm-none-eabi-gdb manually in linux path /usr/bin/ then the GDB version was found. From the looks of this, there are two problems on using IDE on linux, 1) installing the IDE does not link the arm-none-eabi-gdb path properly and 2) the GDB configuration produces a "connection closed due to timeout" error.
Great Idea Alexis! I have success with debugger using Segger JLink firmware. One caveat though, I still had to manually install GDB in linux path because during IDE install, I think it wasn't linked correctly. See below:
However, I'm still scratching my head on PEMicro issues. I would say, I can close this post as answered but there is surely another user out there wondering why it doesn't work with default firmware.
Thank you again!
