Remora - ethernet NVEM / EC300 / EC500 cnc board

scotta wrote:

www.aliexpress.com/item/32937765384.html

This J-OB v2 successfully connected to the board with the Segger software complaining about the clone device etc.

So.. Are you recommend to by this J-OB clone?

No recommendations just yet, just that it connected. I still need to play with it some more. A DAPlink with custom drag and drop firmware would be the ultimate open source solution for people to flash. But I can't get a stable version working.

EDIT: Tried to read the FLASH today with the J-Link OB v2 without success. "ERROR: Can not read register 15 (R15) while CPU is running" etc. Things are never simple....

I installed an old v6.60 version of J-Link to see if it was something to do with the clone detection. Unfortunately the same result using the JFlash GUI.

So, I tried the command line J-Link Commander tool, and Success!!! Original firmware has been read out from the Flash and put away in a safe place.    And better news is that the firmware does not look to be secured with all text strings visible in the bin file. 

Looks like we have a way for people to flash the firmware, even if it is via the command line.

Next step is to do a dummy test program in Flash to ensure the tool chain, and then to remove the iMX RT1052 from the board.

Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: MIMXRT1052CVL5B
Type '?' for selection dialog
Device>MIMXRT1052CVL5B
Please specify target interface:
  J) JTAG (Default)
  S) SWD
  T) cJTAG
TIF>s
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "MIMXRT1052CVL5B" selected.


Connecting to target via SWD
InitTarget() start
InitTarget()
_TargetHalt: CPU halted
InitTarget() end
Found SW-DP with ID 0x0BD11477
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x04770041)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FD000
CPUID register: 0x411FC271. Implementer code: 0x41 (ARM)
Found Cortex-M7 r1p1, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ E00FD000
ROMTbl[0][0]: E00FE000, CID: B105100D, PID: 000BB4C8 ROM Table
ROMTbl[1] @ E00FE000
ROMTbl[1][0]: E00FF000, CID: B105100D, PID: 000BB4C7 ROM Table
ROMTbl[2] @ E00FF000
ROMTbl[2][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
ROMTbl[2][1]: E0001000, CID: B105E00D, PID: 000BB002 DWT
ROMTbl[2][2]: E0002000, CID: B105E00D, PID: 000BB00E FPB-M7
ROMTbl[2][3]: E0000000, CID: B105E00D, PID: 000BB001 ITM
ROMTbl[1][1]: E0041000, CID: B105900D, PID: 001BB975 ETM-M7
ROMTbl[1][2]: E0042000, CID: B105900D, PID: 004BB906 CTI
ROMTbl[0][1]: E0040000, CID: B105900D, PID: 000BB9A9 TPIU-M7
ROMTbl[0][2]: E0043000, CID: B105F00D, PID: 001BB101 TSG
Cache: Separate I- and D-cache.
I-Cache L1: 32 KB, 512 Sets, 32 Bytes/Line, 2-Way
D-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
Cortex-M7 identified.
J-Link>Halt
PC = 60006226, CycleCnt = 00000000
R0 = 00000000, R1 = 00000000, R2 = 00000001, R3 = 00000002
R4 = 03FFFF10, R5 = 402D8000, R6 = 20200F0C, R7 = 00000000
R8 = 00000001, R9 = 400FC06C, R10= 1F78A400, R11= 0000000A
R12= 000013E5
SP(R13)= 20200EE0, MSP= 00002A58, PSP= 20200EE0, R14(LR) = 6000621D
XPSR = 21000000: APSR = nzCvq, EPSR = 01000000, IPSR = 000 (NoException)
CFBP = 02000000, CONTROL = 02, FAULTMASK = 00, BASEPRI = 00, PRIMASK = 00

FPS0 = 00000000, FPS1 = 00000000, FPS2 = 00000000, FPS3 = 00000000
FPS4 = 00000000, FPS5 = 00000000, FPS6 = 00000000, FPS7 = 00000000
FPS8 = 00000000, FPS9 = 00000000, FPS10= 00000000, FPS11= 00000000
FPS12= 00000000, FPS13= 00000000, FPS14= 00000000, FPS15= FFFFFFFF
FPS16= 00000000, FPS17= 00000000, FPS18= 00000000, FPS19= 00000000
FPS20= 00000000, FPS21= 00000000, FPS22= 00000000, FPS23= 00000000
FPS24= 00000000, FPS25= 00000000, FPS26= 00000000, FPS27= 00000000
FPS28= 00000000, FPS29= 00000000, FPS30= 00000000, FPS31= FFFFFFFF
FPSCR= 03000000
J-Link>SaveBin d:\ec300.bin, 0x60000000, 0x400000
Opening binary file for writing... [d:\ec300.bin]
Reading 4194304 bytes from addr 0x60000000 into file...O.K.
J-Link>

Another point for people wanting to try. I did modify the JLinkDevices.xml to use QSPI as per the following link.

mcuoneclipse.com/2019/10/27/using-segger...-on-nxp-i-mx-boards/

There is now a new EC500 as well. A request for board support was raised on the Remora-EC500 github. It looks so so similar to the EC300 but with some additional inputs.
 

After frustrating myself with the J-OB v2 probe and J-Link software, which would successfully read the flash, but nothing I could do would allow erasing and writing the flash...

So back to MCUXpressoIDE to see if I could get a Flash debug setup working. And finally I have a working tool chain with a cheap and open source CMSIS-DAP probe (ST-Link v2 converted)

It was so nice to be able to load a program into the flash and step through the XiP address space

The LinkServer installed with MCUXpresso can be run from a command line script. This may be the easiest way for people to flash boards, but they will have to install the free MCUXpressoIDE.

I feel much more confident that we'll get Remora running on the RT1052 based boards now!

Now to remove the MCU from the board...