quicklogic eos s3 feather Jlink VSCode Question(s)

I currently use the PSOC5. As you are well aware, Infineon has not produced the PSOC5 for the general market for about 2 years. I have been looking for replacement possibilities. I have a blog at socmaker.com. I try to write for the weekend engineer. For them, it ends up being about cost. The cheaper the better.

Tools have to be available to allow any product to be used in the next weekend project (think 3d printer, or anything else in the maker sphere), and building the debugging environment from scratch before you can do any useful work is a nightmare for part timers. Especially when things are documented by hand-waving.

I would like to replace the PSOC5 CY8CKit-059 with something similar, and the QuickLogic EOS S3 might do the work quite often for very low power i/o. However, DEBUG support for the arm M4F processor is a must. At this point, I am very lost regarding that possibility. I expect to have to connect the SWD lines to an old Segger for ARM (or a CMSIS-DAP OpenOCD Device) I have floating around, but this is looking impossible right now. Let me explain…

I recently picked up a Sparkfun quicklogic board from Mouser. (Dev-17273) I have not tried to reprogram it via usb, not there yet. I doubt I could send it back if it is defective (based on feedback I just read on your forums) due to having purchased from Mouser, but that is life.

I have a real Segger j-link for ARM Version 8.0, with firmware I updated yesterday. A new segger at $500 is too much, for a product that may not even work. If that is required, I will have to stop.

I would like to hook the v8 segger up to the board, but the connector on the board is not JTAG, it is SWD. I cannot find a matching cable for it anywhere, not even on your site. I would need an adaptor, and if necessary I can create one, but I can’t find the right cable to your board. (google and bing and mouser search are no help)

The cable does not appear to be a 0.05" pin spacing like you have on your website. The pin spacing is MUCH smaller than 0.05, it appears to be 0.005 (per my micrometer). I have yet to locate such a cable. Can you help?

Once I have the right cable and matching socket, I could probably create a board to marry the two different sizes using OSH Park and Eagle. The $40++++ segger adapter boards I have found appear to not be right even though the price can be accepted (but irritating).

Even if that does/does not work, I would like to take a KitProg3 in CMSIS-DAP mode and, using OpenOCD, attempt to make a debug connection. If that works, it plays to my readers. However, I am again at a 0.1" connector to 0.005" connector dilemma. However, that board stub debugger unit can be had from several CY8CKits or Cy8CProtos still available.

Finally, has anyone brought up VSCode for the EOS S3? With, or without debugging. Has anyone brought up anything for debugging the EOS S3 M4F C/C++ code? Based on my reading, and the silence from Quicklogic when asked, the answer seems to be no.

Someone on Twitter created an SVD file, not sure if it works yet, I have to get through the cable problem.

If we can bring this up some how, I will document it on socmaker, and perhaps someone else will be able to jump on board.

thanks!

I found a cable that can plug into the QuickLogic board from an old Cypress dev kit. Now I need to locate a socket to create a plugin board.

I also found a video on youtube. unbrick Quickfeather. or on youtube: www.youtube.com/watch?v=Q5GIZUsXb3I

at 5:30 it will show you how to start the unbricking process. I am waiting on an adapter board from ebay. you can follow on socmaker.com

I finally resolved unbricking my quicklogic feather board.

I put the solution on socmaker.com

Basically, I was able to use an XMC-Jlink and just select a coretex-m4. Then following the video previously referred to, and downloading from github the qf-initial-bins, and using --mfgpkg in the qfprog alias for the tiny fpga programmer, you can unbrick the quickfeather board.

Read the socmaker blog to get the full scoop. VSCode is next, at some point in the future.