Remora - Can't get it out of estop....

First, thanks for all the help.  This is my time LinuxCNC so, please bear with me.  My setup:  Rpi5 with SPI to a BigTreeTech SKR 1.4 (has the LPC processor) running Remora pulled from Github a couple weeks ago.  I got everything compiled and I think in the right place (I got a bunch of warnings on the SPI Remora compile but was told to ignore).  I figured the remora-xyz sample code looked like a good place to start.  The LinuxCNC Config Selector allows me to select remora-xyz and a window starts with axis.ngc.  *The problem is that the Emergency Stop button comes up pressed and it can't click it off*.  I have tried using the halmeter tool and found a variable called iocontrol.0.user-request-enable that I think may be relevant based on looking at the .hal file.  This PIN reads FALSE but very briefly flashes to TRUE, then back to FALSE when I click on the Estop button.  I as wondering if the remora-xyz example is actually trying to read a HW input somewhere on the SKR 1.4 board that I should be terminating correctly?   Any suggestions much appreciated.  TIA.   

Hi,
I'm currently trying to get a rp2040 working with Remora over ethernet, so a very different setup. But I was in a similar case yesterday and for me it was a data payload problem, that was different in the component and in the firmware. I don't think that this is your problem, but are you sure that you have a communication between the RPi and the SKR? Also, I don't know how your SPI connection looks like, but the standard frequency is at 20MHz, which requires short wires; maybe try to add the SPI_freq=1000000 to your loadrt line in the hal file to see if at 1MHz SPI frequency there is a communication.

Thanks for replying. The wires are about six inches in length so the communication integrity might be a problem and are separate wires, not ribbon cable. I will try experimenting with the SPI_freq to see if it makes a difference. I think my next step will be to put an oscope on the SPI lines running between the Rpi and the SKR and see what is going on. You refer to a "data payload problem"....don't know what they means.?

Hi Mars,

Unfortunately, there is no support for the LPC based boards with the RPi5 version of the Remora component. The LPC chips need the CS line to toggle on each byte being sent out. This would be why it's not coming out of eStop.

Also, the firmware for the LPC boards is outdated in terms of the Remora data structure.

oh....that is why. Thanks for the answer. You may consider putting something in the documentation to flag this so that others don't try this path. I need to regroup and figure out the next cheapest HW to work with the Rpi5. Do you think the STM based boards will be around for awhile? I was hoping to go Remora but I have to think about that parallel port board that someone makes for the Rpis.

Yes, I think so. The 3D printer market will determine the evolution of controller boards.

STM F4 boards are well supported.

The Devs are actively working on a newly refactored Remora-core and HALs for various MCU series to move away from Mbed. This will bring support for H7 boards which are in beta testing at the moment.