Remora - Rpi Software Stepping Using External Microcontroller via SPI

Im using studio, ive compiled the stm32 repo just fine. I also find it strange, I just download the git, open a workspace in remora os5, and download the libraries within studio, says its 5.15.0. Select target, SKRV2 or OCTOPUS, and build. The file LPC17xx.h is there under targets/nxp/device . Says everything is up to date for mbed studio


this is the full output, I was just wondering if there was some secret

MODDMA lib
Commit: 97a16bf2ff439853ed01edd65a382207e203c733
Imported from: os.mbed.com/users/AjK/code/MODDMA/

mbed-os 5.15.0
Commit: 64853b354fa188bfe8dbd51e78771213c7ed37f7
Imported from: github.com/ARMmbed/mbed-os/
edit, ok I was doing something with the MODDMA lib that was messing it up

Hi, the MODDMA library is already included in the repo in the correct location within the TARGET_SKRV1_4 directory. No need to import it again, which will put in the root directory and in the compile path.

Thank you for your help and patience. Yeah studio was saying i should "fix" the mbed-os and moddma lib. That explains why the stm32-repo worked and the main didnt.
How do I go about debugging this octopus? something like FTDI ,stlink or JTAG?? Can we hook these up USB like the official mbed boards and debug within studio? Ill break what ever I have to...
What I do know
I have reset pin on PC_15 in my config
Firmware loads and makes a cur file
Leds look like they are loading firmware and acting proper
12v power
Bad SPI payload = 0
No output on the serial
Memory does not look corrupted and bootload/firmware are on the correct address lines
SKR2 for reference, works on my setup.

look if ur connected to the right spi port.

@scotta : Do you think it is possible to connect until 5 MCU like the rpspi.c driver ? or maybe start with 2, one on the RPI SPI0 and an another on the RPI SPI1

cakeslob wrote:

Thank you for your help and patience. Yeah studio was saying i should "fix" the mbed-os and moddma lib. That explains why the stm32-repo worked and the main didnt.
How do I go about debugging this octopus? something like FTDI ,stlink or JTAG?? Can we hook these up USB like the official mbed boards and debug within studio? Ill break what ever I have to...
What I do know
I have reset pin on PC_15 in my config
Firmware loads and makes a cur file
Leds look like they are loading firmware and acting proper
12v power
Bad SPI payload = 0
No output on the serial
Memory does not look corrupted and bootload/firmware are on the correct address lines
SKR2 for reference, works on my setup.

Hi, I've fixed the MODDMA issue in the develop branch. There was a MODDMA.lib file in the root directory. This is what was prompting people to download the lib.

So the SKR2 bin works on the Octopus board..? Interesting. The CPU frequency would be slower than possible. But it does help narrow down the problem. The only difference between the two builds is the system_clock.c file in the target directory. And this is really only setting the frequency to 180MHz. 

The only other difference is the serial pins in mbed_app.json and in some of the setting in custom_target.json. You might be onto something. Thanks

gtt38 wrote:

@scotta : Do you think it is possible to connect until 5 MCU like the rpspi.c driver ? or maybe start with 2, one on the RPI SPI0 and an another on the RPI SPI1

Definitely and this is something I had in the back of my mind. We could utilise SPI0 and have multiple Chip Selects.

Sorry, I should specify I bit more. The skr2 works with the skr2, it was mostly a sanity check to make sure my cables/gpio/linuxcnc were not the root cause. I havent actually tried with just the skr2 firmware, I didnt really consider it but I will now. 
The only difference I am seeing between the 2 also, is just some pins and the clock. I find no other references that indicate any different compile flags among the other firmware. 
The only thing difference I noticed in klipper, is something with the bootloader and the clockspeed with a 12 Mhz clock reference but Im not sure what its referring to.
github.com/bigtreetech/BIGTREETECH-OCTOP...ter/Firmware/Klipper


I hooked up the octopus to mbed studio with a chinese stlinkv2 and it works and connects, but when trying to debug the program, it makes my computer go completely ape shit triggering mouse events all over the place.

gtt38 wrote:

look if ur connected to the right spi port.

they are all the same pretty much , on exp2, i checked a few times just incase

Ok, I should have checked the clock frequency, rather than copying from another Mbed target. I've updated the develop repo with an updated system_clock.c and compiled bin file. Fingers crossed this was the issue.

I saw your repo and i m gonna try to create my own target for stm32f411 this weekend