Remora - ethernet NVEM / EC300 / EC500 cnc board

It should only be a wiring issue, maybe post a couple of pictures so we can see your setup?

I have received my second STlinkv2 and have programmed it with the stm32f103xb_bl.bin file. I reset the device plugged in directly and it gets mounted as the Maintenance drive. I then copied the stm32f103xb_mimxrt1050_qspi_if.bin file to the Maintenance drive but unlike your video i dont see the device eject/reload itself at that point, doing manual power cycle the maintenance drive just remounts with the stm32f103xb_mimxrt1050_qspi_if.bin file missing but it doesnt come back with the RT1052 drive name as expected. Any ideas?

cncwhacko wrote:

I have received my second STlinkv2 and have programmed it with the stm32f103xb_bl.bin file. I reset the device plugged in directly and it gets mounted as the Maintenance drive. I then copied the stm32f103xb_mimxrt1050_qspi_if.bin file to the Maintenance drive but unlike your video i dont see the device eject/reload itself at that point, doing manual power cycle the maintenance drive just remounts with the stm32f103xb_mimxrt1050_qspi_if.bin file missing but it doesnt come back with the RT1052 drive name as expected. Any ideas?

Hmm, I have not had that problem. Maybe do a full erase and re-flash the boot loader firmware gain.

An EC500 has arrived and I thought that this would be a great test to see if programming was straight forward with the DAPLink on a board with original firmware.

Unfortunately no...

FAIL.TXT error: Failed to initialize the target MCU

This error occurs even with using the boot_M0 pin to force a boot not from flash.

I new this was to good to be true.

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