Remora - ethernet NVEM / EC300 / EC500 cnc board

So  there it is... I have checked rs232 adaptor connection and working on other device
Board flashed successfully from bin file log attached

stmlink v2 showing maintanace not rt1052

# DAPLink Firmware - see daplink.io
Build ID: v0257-15-gd2db0d5b (gcc, local mods)
Unique ID: 00000000066eff495356675287124206a5a5a5a597969908
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: 0
URL: daplink.io


log from flash:

Executing flash operation 'Program' (Program file into flash: remora-rt1052-1.1.0.bin) - Mon Jul 24 17:43:08 BST 2023
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.7 (Mar 22 2023 09:52:55 - crt_emu_cm_redlink.exe build 13)
(  0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in C:/Users/rasta/Documents/MCUXpressoIDE_11.7.1_9221/workspace/remora-rt1052/Debug\MIMXRT1052xxxxB.xml
(  5) Remote configuration complete
Reconnected to existing LinkServer process.
============= SCRIPT: RT1050_connect.scp =============
RT1050 Connect Script
DpID = 0BD11477
APID = 0x04770041
Disabling MPU
Configure FlexRAM for 256KB OC RAM, 128KB I-TCM, 128KB D-TCM
Finished
============= END SCRIPT =============================
Probe Firmware: CMSIS-DAP v1 (Arm)
Serial Number:  02270b03066eff495356675287124206a5a5a5a597969908
VID:PID:  0D28:0204
USB Path: \\?\hid#vid_0d28&pid_0204&mi_03#a&383eca04&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
( 30) Emulator Connected
( 40) Debug Halt
( 50) CPU ID
debug interface type      = CoreSight DP (DAP DP ID 0BD11477) over SWD TAP 0
processor type            = Cortex-M7 (CPU ID 00000C27) on DAP AP 0
number of h/w breakpoints = 8
number of flash patches   = 0
number of h/w watchpoints = 4
Probe(0): Connected&Reset. DpID: 0BD11477. CpuID: 00000C27. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE E00FD000: CID B105100D PID 000008E88C ROM (type 0x1)
ROM 1 E00FE000: CID B105100D PID 04000BB4C8 ROM (type 0x1)
ROM 2 E00FF000: CID B105100D PID 04000BB4C7 ROM (type 0x1)
ROM 3 E000E000: CID B105E00D PID 04000BB00C Gen SCS (type 0x0)
ROM 3 E0001000: CID B105E00D PID 04000BB002 Gen DWT (type 0x0)
ROM 3 E0002000: CID B105E00D PID 04000BB00E Gen (type 0x0)
ROM 3 E0000000: CID B105E00D PID 04000BB001 Gen ITM (type 0x0)
ROM 2 E0041000: CID B105900D PID 04001BB975 CSt ARM ETMv4.0 type 0x13 Trace Source - Core
ROM 2 E0042000: CID B105900D PID 04004BB906 CSt type 0x14 Debug Control - Trigger, e.g. ECT
ROM 1 E0040000: CID B105900D PID 04000BB9A9 CSt type 0x11 Trace Sink - TPIU
ROM 1 E0043000: CID B105F00D PID 04001BB101 Sys (type 0x0)
NXP: MIMXRT1052xxxxB
DAP stride is 1024 bytes (256 words)
Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MIMXRT1050_SFDP_QSPI.cfx
Image 'iMXRT1050_SFDP_QSPI Mar 21 2023 13:24:31'
Opening flash driver MIMXRT1050_SFDP_QSPI.cfx
Sending VECTRESET to run flash driver
Flash variant 'JEDEC_SFDP_Device' detected (4MB = 64*64K at 0x60000000)
Closing flash driver MIMXRT1050_SFDP_QSPI.cfx
( 65) Chip Setup Complete
Connected: was_reset=false. was_stopped=true
( 70) License Check Complete
Loading 'remora-rt1052-1.1.0.bin' Binary 0x60000000 len 0x30F2B
Opening flash driver MIMXRT1050_SFDP_QSPI.cfx (already resident)
Sending VECTRESET to run flash driver
Flash variant 'JEDEC_SFDP_Device' detected (4MB = 64*64K at 0x60000000)
Writing 200492 bytes to address 0x60000000 in Flash
(  0) Mass erasing Flash
Mass erased flash in 10513msec
1 of 1 (  0) Writing sectors 0-3 at 0x60000000 with 200492 bytes
(  0) at 60000000: 0 bytes - 0/200492
(   at 60000000: 16384 bytes - 16384/200492
( 16) at 60004000: 16384 bytes - 32768/200492
( 24) at 60008000: 16384 bytes - 49152/200492
( 32) at 6000C000: 16384 bytes - 65536/200492
( 40) at 60010000: 16384 bytes - 81920/200492
( 49) at 60014000: 16384 bytes - 98304/200492
( 57) at 60018000: 16384 bytes - 114688/200492
( 65) at 6001C000: 16384 bytes - 131072/200492
( 73) at 60020000: 16384 bytes - 147456/200492
( 81) at 60024000: 16384 bytes - 163840/200492
( 89) at 60028000: 16384 bytes - 180224/200492
( 98) at 6002C000: 16384 bytes - 196608/200492
(100) at 60030000: 16384 bytes - 212992/200492
Sectors written: 4, unchanged: 0, total: 4
Wrote sector 0-3 with 200492 bytes in 8497msec
Closing flash driver MIMXRT1050_SFDP_QSPI.cfx
(100) Finished writing Flash successfully.
Flash Write Done
Loaded 0x30F2B bytes in 19294ms (about 10kB/s)
Reset target (system)
Starting execution using system reset

I had no response from serial tho 

     


 

I've just hooked the NVEM back up to the test bench to confirm on the same hardware. All working as expected including serial output.

Your size of the file you are flashing looks wrong. Output below from flashing with MCUXpresso GUI Flash tool. Image size is 321392 bytes where your output is 200492 bytes..?

It still looks like your are using the DAPlink firmware. Please change to the CMSIS-DAP firmware on your ST-Link.

github.com/scottalford75/Remora-RT1052/b...SIS-DAP-STLINK21.hex

That did work something and I have responses from rs232 terminal , flashing light in ETH socket and below is LinuxCNC config IP a and ping.

 
Is there guide how to find config in linuxcnc.ini? I have seen so much new information I would appreciate some directions from here ofc if it is working in fact. 

Great to see you have made some progress! A starting point would be to use one of the example configurations and then customise to your installation.

github.com/scottalford75/Remora-NVEM/tre...es/remora-nvem-basic
 

Good morning,
I would like some advice for the following problem:

After flashing version remora-rt1052-1.1.0.bin I get an Assert Error after boot. I went back to version remora-rt1052-1.0.0.bin and get the same error. Is this a hardware problem?

See the RS232 log after boot:

Remora RT1052 starting

Initializing PHY...

## Entering SETUP state


1. Loading JSON configuration file from Flash memory



2. Parsing JSON configuration file
Config deserialisation - Deserialization succeeded

3. Configuring threads
Creating thread 40000
Creating thread 1000

4. Loading modules

Creating a std module
Creating an Ethernet communication monitoring module
Creating Pin @
port = GPIO3
pin = 0

Base thread object

X - Joint 0 step generator

Creating a std module
Creating Pin @
port = GPIO21
pin = 15
Creating Pin @
port = GPIO21
pin = 14

Base thread object

Y - Joint 1 step generator

Creating a std module
Creating Pin @
port = GPIO21
pin = 13
Creating Pin @
port = GPIO21
pin = 12

Base thread object

Z - Joint 2 step generator

Creating a std module
Creating Pin @
port = GPIO21
pin = 11
Creating Pin @
port = GPIO21
pin = 10

Base thread object

A - Joint 3 step generator

Creating a std module
Creating Pin @
port = GPIO21
pin = 9
Creating Pin @
port = GPIO21
pin = 8

Base thread object

B - Joint 4 step generator

Creating a std module
Creating Pin @
port = GPIO21
pin = 7
Creating Pin @
port = GPIO17
pin = 8

Base thread object

C - Joint 5 step generator

Creating a std module
Creating Pin @
port = GPIO17
pin = 5
Creating Pin @
port = GPIO17
pin = 6

FHA
Make Digital Input at pin PD_12

Creating a std module
Creating Pin @
port = GPIO20
pin = 12

FHB
Make Digital Input at pin PD_13

Creating a std module
Creating Pin @
port = GPIO20
pin = 13

SRO
Make Digital Input at pin PB_14

Creating a std module
Creating Pin @
port = GPIO18
pin = 14

SJR
Make Digital Input at pin PB_15

Creating a std module
Creating Pin @
port = GPIO18
pin = 15

STOP
Make Digital Input at pin PD_8

Creating a std module
Creating Pin @
port = GPIO20
pin = 8

PROBE
Make Digital Input at pin PD_9

Creating a std module
Creating Pin @
port = GPIO20
pin = 9

INP3
Make Digital Input at pin PD_10

Creating a std module
Creating Pin @
port = GPIO20
pin = 10

INP4
Make Digital Input at pin PD_11

Creating a std module
Creating Pin @
port = GPIO20
pin = 11

INP5
Make Digital Input at pin PD_14

Creating a std module
Creating Pin @
port = GPIO20
pin = 14

INP6
Make Digital Input at pin PD_15

Creating a std module
Creating Pin @
port = GPIO20
pin = 15

INP7
Make Digital Input at pin PC_6

Creating a std module
Creating Pin @
port = GPIO19
pin = 6

INP8
Make Digital Input at pin PC_7

Creating a std module
Creating Pin @
port = GPIO19
pin = 7

INP9
Make Digital Input at pin PC_8

Creating a std module
Creating Pin @
port = GPIO19
pin = 8

INP10
Make Digital Input at pin PC_9

Creating a std module
Creating Pin @
port = GPIO19
pin = 9

INP11
Make Digital Input at pin PA_11

Creating a std module
Creating Pin @
port = GPIO17
pin = 11

INP12
Make Digital Input at pin PA_12

Creating a std module
Creating Pin @
port = GPIO17
pin = 12

INDEX
Make Digital Input at pin PC_15

Creating a std module
Creating Pin @
port = GPIO19
pin = 15
ASSERT ERROR " instance < ARRAY_SIZE(s_gpioBases) ": file "fsl_gpio.c" Line "60" function name "GPIO_GetInstance"