Remora - ethernet NVEM / EC300 / EC500 cnc board

Thank you for the quick reply.

The log you shared is from the Python script, but the important part happens on the EC300 board side.
Could you connect an RS232 interface and check the board's response when receiving the new configuration?

Thanks

I seem to of been wrong about converting the ST-link to DAP. I just went back and watched the video again and there were originally 2 steps in doing the conversion, but there is the post below that video - forum.linuxcnc.org/18-computer/44828-rem...rd?start=2050#321860 - that says to just use that one file?

I am now very confused and the computer says the converted ST link is an unrecognized device and it does not show up. I can not communicate with the link plugged into the USB

At this point I truly do not know what to do.

Attis92 wrote:

Thank you for the quick reply.

The log you shared is from the Python script, but the important part happens on the EC300 board side.

I can do it, but I need to get hold of a USB to RS232 adapter first. Should have it next week

Spyderbreath wrote:

I seem to of been wrong about converting the ST-link to DAP. I just went back and watched the video again and there were originally 2 steps in doing the conversion, but there is the post below that video - forum.linuxcnc.org/18-computer/44828-rem...rd?start=2050#321860 - that says to just use that one file?

I am now very confused and the computer says the converted ST link is an unrecognized device and it does not show up. I can not communicate with the link plugged into the USB

At this point I truly do not know what to do.
 

It might be easiest to buy one for a few $$ on Amazon or Ebay. 

OK, so no one actually knows exactly how to make this work for the current state of the software, or if they do, it must be way to difficult to explain the current process in a single post. Tragic, but I will have to accept it. I think I will cut my losses at this point and purchase a MESA 7I96 or some such. They seem to be only a few $$ these days anyway and they are in country, (less expensive than some of those DAP units on Amazon).

Thank you for your attempt to help, it has been appreciated. It all looked to be so straight forward at first glance and it probably was at one point.

It just seems hard to comprehend how the current process of converting an ST-link to a DAP-link has become so complex that it can not be explained in a single post, but here we are.

Hi Spyderbreath,I'll write down the steps I followed to create the DAPLink. I worked on Linux, so some parts may differ on Windows.1. I bought ST-Link devices.
2. I prepared the hardware based on the first part of Scott3D’s YouTube video :
It clearly shows the soldering process.
He uses the ST-Link Utility, but since it's not available on Linux, I used STM32CubeProgrammer, which works on both Linux and Windows:
I connected the four soldered wires to the ST-Link as follows:
3V3 → 3V3
GND → GND
SWCLK → CLK
SWDIO → DO
(The rest of the video is not relevant for this process.)

3. I downloaded (or cloned) the Remora-RT1052 repository.
It contains a CMSIS-DAP folder, and inside it, the CMSIS-DAP-STLINK21.hex file.

4. I opened STM32CubeProgrammer, plugged in the ST-Link device,
clicked “Connect” (top right corner), and once connected, the left-side menu became available.
Then:
Clicked the “OB” (Option Bytes) button
Under Read Out Protection, I unchecked the “RDP” flag.

5. I went back to the main menu (Memory & File Editing):
Clicked “Open File” → selected CMSIS-DAP-STLINK21.hex
Clicked “Download” to flash the firmware.
Now the DAPLink is ready to use. (Note: This version of DAPLink doesn't support drag-and-drop (MSC), so we’ll flash the RT1052 using pyOCD instead.)

6. I created a temporary folder (e.g., remora_flash) and set up a Python virtual environment inside it:

Plug in the DAPLink via USB and check if it's detected:
Example output:
7. Finally, I flashed the firmware to the RT1052.
Clone or download the Remora-RT1052-cpp repository.
In the Firmware folder, you’ll find the binary image: remora-rt1052-3.1.3.bin.

Connect the board via DAPLink and flash it using:
8. Configuration upload is described in Daz’s post.

Hope this helps!

I'm having the same problem

Wow, yes that does help immensely. Fortunately I was up early enough this morning to retrieve the hardware from the trash before the truck came down the road to hall it away. Unfortunately, not before I ordered a 7I96S, but I'll find a use for the both of them as I have a Emco 120P to retrofit after I get this mill up and running.

The info in 3. is the first time I have seen any reference to that file.

About 8. ? The post that Daz made if you are referring to this one - forum.linuxcnc.org/18-computer/44828-rem...rd?start=2140#327240 - is for an EC300, not an NVEM. From what I am seeing I will need to follow to the letter up to step 8, then use the nvem-rt1052.txt instead of the ec300-rt1052.txt linked to in that post. Is that correct?

cakeslob post=326968 userid=25269

Are all the drivers the same, or did you do your check all axis with the same drive

 jjdege post=326970 userid=32556

hi
the same driver for all axes.
I tried to unsolder the chip, without success
the board does not respond, for now I do not think I will buy another
thanks for the support
 

Hi guys

I couldn't resist and bought a new board, this time I opted for a 3-axis EC500,
it has LEDs that indicate the I/O status, I think it's more complete.

I tested it with Mach3 to make sure it was working well, given the previous ones,
and it worked on all three axes.

When loading the firmware, it got to 29% and timed out and everything froze,
the DAP wasn't receiving signals.
I reread page 115 of the thread that talks about how to unlock and after having
bridged BOOT_MO and 3V3 I managed to delete and write the new firmware!!

Now all 6 axes work.

Thanks again to Scott and to whoever made all this possible.

Yes, correct!
But I’m still having some issues with the config upload, which I’m currently investigating on the EC500 board.
If you're unable to change the config, you may need to erase the entire chip first:

Then flash the firmware again and upload the new config.

This worked for me, but it's definitely not an ideal solution...