Debugging build after flashing on Mac OS #55
Replies: 1 comment 3 replies
-
|
Did you ever find a solution to this? |
Beta Was this translation helpful? Give feedback.
-
|
Hey, you are right that there is no serial support for Docker on Mac. Flashing the hex file has worked for us, but the problem is with debugging. I got some pointers on the debugging problem but I haven't worked on this yet: https://blog.golioth.io/taking-the-next-step-debugging-with-segger-ozone-and-systemview-on-zephyr/ https://blog.golioth.io/remote-zephyr-development-using-segger-tunnel-and-a-raspberry-pi/ https://blog.golioth.io/we-tried-to-debug-a-microcontroller-from-our-browser/ |
Beta Was this translation helpful? Give feedback.
-
|
I ended up just running a full Linux VM using parallels, then using Docker inside of that to build the nrf-connect image. I then just passed thru the USB debugger to Parallels, and ran VSCode inside parallels. So it does mean have to work inside of that but it worked fine for me |
Beta Was this translation helpful? Give feedback.
-
|
Aha that sounds like a good idea... If I ever choose to do this do you mind if I reach out for any questions? |
Beta Was this translation helpful? Give feedback.
-
Hi, I've set up working containers for my team to build and flash programs to our dev boards, but am getting stuck on debugging. We mostly use nRF Development Kits like nrf52840DK, nordic tools (VS Code extensions, nrf Connect), and JLink while developing. However, after building and flashing, when I try to do west debug or attach, the program seems to be looking for files from the container (/workdir/...), which isn't present on the local side since we are using Macs and cannot flash inside the container. I'm wondering if anyone has done similar things and could offer some help, or if there's a guide on debugging with the nrf docker. Thanks a lot!
Beta Was this translation helpful? Give feedback.
All reactions