Remora - ethernet NVEM / EC300 / EC500 cnc board

Thanks Cakeslob, I'll have a look at this again in a couple of weeks as I'm away with work. 

    I did the whole process to change the firmware of the stlink, it was successful, but it does not appear on my PC, the only difference is that I did not find the blue stlink so I did it in a green one, I used two green stlinks, would there be any difference? If so, how do I find the blue stlink, when I go to buy the cover and everything is the same

External e-stop (fault) on EC500 input.  

I have 8 ST link V2 and they are all 128kb. How can I put the remora-rt1052-3.1.3.bin firmware on them when they are 350kb?

um... good question...

you dont actually load the stlinks with remora firmware. stlinks probably need the daplink firmware or something, and then the stlink passes the firmware from the computer to the NVEM

stlinks probably need the daplink firmware or something

No. The ST-Link works without any modifications.

yes?how?

Thayloreing  i have the same problem

Domi wrote:

yes?how?
 

pyocd reset --target mimxrt1050_quadspi
pyocd erase --chip --target mimxrt1050_quadspi
pyocd reset --target mimxrt1050_quadspi
pyocd flash remora-rt1052-3.1.3.bin --target mimxrt1050_quadspi
pyocd reset --target mimxrt1050_quadspi
 

Hey brains trust!

I'm working on converting an NVEM v5 board (says IMXR_NVEM_V6   2022-08-11 on the silk screen) to use Remora. I managed to get the firmware uploaded to the board, thank you Scott for the great vid. The board uses RT1052 chip and I was able to make a donor STLink into a DAPLink and upload the firmware by compiling the latest Remora-RT1052-cpp from source. I could initially see it working by toggling the eStop in software and seeing the LED light up on the board so I know it was responding to LinuxCNC at first. I basically just followed the steps in the video. 

I got the static IP set up, did the Halcompile of the ethernet component, and then successfully uploaded an unmodified full_config.txt with the upload_config.py script, I managed to get past needing to install the TFTP package via PIP successfully as it wasn't included on my machine by default. This is where I'm now running into issues. After installing the config, LinuxCNC will no longer allow me to get the machine out of eStop, where it did before. Clicking the button does nothing and the LED on the board no longer toggles. It no longer lets me upload new configs, and pinging 10.10.10.10 now no longer responds (it did before I uploaded the config. This happened once already and re-flashing the chip got me back to being able to ping, get the machine out of eStop and upload new configs, none of which I can do anymore after uploading the config. The chip definitely isn't bricked as I can erase, reupload and step over code using the makeshift DAPLink as a debugger. 

I've tried wiring up a serial connector for the little port in the corner, but I'm not even sure that works to begin with - I've only seen Scott do it to an EC500 board so this potentially could help in troubleshooting. Seems I can read serial with a loopback and I know the wiring pinout, baud rate, comms settings etc from the pic on page 1 of this thread, none of that has output any data to any of the serial terminals I've tried on both of my machines.

I'm using the latest LinuxCNC version which I believe is now using Debian Bookworm which now uses NetworkManager so some of the instructions used in the video are now slightly different. I've fiddled with firewall and port settings but I'm not sure that's it because uploading and connecting works the first time just fine - port 69 is definitely open for SFTP.

Hope that's a good enough starting point for troubleshooting, let me know what other details I can provide to help troubleshoot this one? It's an odd one!