Remora - ethernet NVEM cnc board

So EC500 programmed with MCUXpresso and working! So just need to work out the additional IO and we'll have the NVEM, EC300 and EC500 for LinuxCNC use.

With Remora firmware on the EC500, drag-and-drop programming with the DAPLink works. So for the moment it looks like the initial programming will still need to be done with MCUXpresso and then updates can be done with drag-and-drop.

tried flashing few more times the _bl file. Same behavior. After mounting the maintenance drive and waiting some time ~60secs after placing the _qspi_if.bin file on the Maint drive a FAIL.txt message pops up:

Contents of which say:
error: The transfer timed out.
type: transient, user

Details.txt says:
# DAPLink Firmware - see daplink.io
Build ID: v0257-15-gd2db0d5b (gcc, local mods)
Unique ID: 0000000000390061520000104e52504ea5a5a5a597969908
HIC ID: 97969908
Auto Reset: 0
Automation allowed: 1
Overflow detection: 0
Incompatible image detection: 0
Page erasing: 0
Daplink Mode: Bootloader
Bootloader Version: 0258
Interface Version: 0258
Git SHA: d2db0d5b6f8857aa2106dfc0f5c25ce9b26387f1
Local Mods: 1
USB Interfaces: MSD
Bootloader CRC: 0xd5180591
Interface CRC: 0xc9e070d0
Remount count: 1
URL: daplink.io

onething that I just noticed in the ST-Link utility it lists my target flash size of 128KB, i see the bl itself is 47KB and then the qspi_if.bin file is 79KB. 47+79KB is 126KB which is really close to that max limit, is it possible my target st-link clone has less flash than yours? I noticed in your video it says Flash Size "unknown"

My ST-Links are also 128KB.

I've taken a full image of my working DAPLink (bl + if). Try flashing this with ST-Link Utility.

github.com/scottalford75/Remora-RT1052/b...mxrt1050_qspi_if.bin

BR
Scott

just loaded github.com/scottalford75/Remora-RT1052/b...mxrt1050_qspi_if.bin on the target, plugged it in and it also mounted as Maintenance drive. Same thing when i drag/drop stm32f103xb_mimxrt1050_qspi_if.bin onto it again this time, file fully copies but then it doesnt reset itself at that point.

Another data point. For giggles, I tried using a bluepill board as a target and that did work as expected! It mounted as Maintenance, then placed the _if.bin on there and reset and remounted as RT1052. mcuexpresso with the bluepill detects the daplink.

Yet now the pin mapping you gave in forum.linuxcnc.org/18-computer/44828-rem...ard?start=590#262786 I am not having success with.

ive shorted PB12 and PB14 via 100ohm resistor but still doesnt detect the board when attempting to connect in mcuxpresso. Is there anything on the board side you need to do to trigger the programming?

I have connected the SWD,SCK,3.3v and G on the EC500 board to the bluepill as such:

ec500

---

blue pill

success using the bluepill as the daplink! one thing i had to do in order to get the rt1052 to respond within mcuxpresso was have it plugged into the bluepill when placing the stm32f103xb_mimxrt1050_qspi_if.bin onto the Maintenance bluepill drive. Then it loaded and i was able to flash using this method!

Seems like the default ip address is set to 10.10.10.10 with the current repo config, is that correct? I was going to test against the device to see if it responded to pings

here is a picture of the wiring. i turned everything around for viewing pleasure. the dupont cables are connected to the pin rows shown


3v3 to 3v3
GND to GND
CLK to ClK
DIO to DIO

the boards are exactly like yours. the source board has a solid blue LED and the target a flashing red LED

just tested again. no luckl. :/
 

cncwhacko wrote:

success using the bluepill as the daplink! one thing i had to do in order to get the rt1052 to respond within mcuxpresso was have it plugged into the bluepill when placing the stm32f103xb_mimxrt1050_qspi_if.bin onto the Maintenance bluepill drive. Then it loaded and i was able to flash using this method!

Seems like the default ip address is set to 10.10.10.10 with the current repo config, is that correct? I was going to test against the device to see if it responded to pings

Great to hear you are up and going! Yes, the IP address is 10.10.10.10 but as you are compiling from source you could change that if needed.

I'll get the additional IO for the EC500 worked out over the next week or so.

cncwhacko wrote:

Another data point. For giggles, I tried using a bluepill board as a target and that did work as expected! It mounted as Maintenance, then placed the _if.bin on there and reset and remounted as RT1052. mcuexpresso with the bluepill detects the daplink.

Yet now the pin mapping you gave in forum.linuxcnc.org/18-computer/44828-rem...ard?start=590#262786 I am not having success with.

ive shorted PB12 and PB14 via 100ohm resistor but still doesnt detect the board when attempting to connect in mcuxpresso. Is there anything on the board side you need to do to trigger the programming?

I have connected the SWD,SCK,3.3v and G on the EC500 board to the bluepill as such:

ec500

---

blue pill

3.3 ------------ 3.3
G ------------ G
SCK ---------- PB13
SDO ---------- PB14

The EC500 has a 3.3v pin on the header but my ST-Link could not power the board reliably. No issues connecting when using powering the board with 24v and only connecting the 3 pins (G, SCK SWDIO).