Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BTT-Octopus with STM32H723? #68

Open
thaala opened this issue Nov 3, 2024 · 10 comments
Open

BTT-Octopus with STM32H723? #68

thaala opened this issue Nov 3, 2024 · 10 comments

Comments

@thaala
Copy link

thaala commented Nov 3, 2024

Hello all,

i have two boards here from BTT. Octopus V1.1 with H723 processor and a Kraken V1.0 with same processor.
Because Kraken has fixed TMC5160 drivers missing - it may be a problem to use it with remora. Octopus lacks currently support for H723 processor only. Pins of Octopus are same as for M466 processor variant. Could you please give a roadmap to bring remora to the H723 - Version?

Is it maybe only the timing (clocking) setup? In case of success i will contribute the source to your project.
Is there a progress by adding TMC5160 driver code?

Thank you in advance.

@cakeslob
Copy link
Contributor

cakeslob commented Nov 3, 2024

Fantastic, always looking for help, lets start with the H7
With the nucleo H723, i have it working up until SPI by bypassing the bootloader and SD card
Roadmap :

  • Bootloader : not loading properly with the SKR3, personally i consider this lower priority
  • SD card SDIO driver : not sure where this was left off but there have been more updates by jojo to the driver that we need to implement and test , can be tested without it but it will need it in the long run
  • SPI DMA : biggest hurdle at the moment, because without it, theres nothing for no one . something with the SPI DMA MUX or something

spi issue is the biggest problem, and I am finding it very hard to debug the H7

@cakeslob
Copy link
Contributor

cakeslob commented Nov 3, 2024

RE TMC5160
user Sean has been working his way through the TMC SPI as well as working on the SKR3, I think he has the initial work done offline, but I dont know how physical testing has gone. He has also done some work on H7 but I dont know how far he has gotten
here is a link to his fork
https://github.com/seanmccully/Remora

@thaala
Copy link
Author

thaala commented Nov 3, 2024

Fine..
nice to be welcome with it.
Need some setup time - a week or so.... ;-)

thank you for this fast response...

BR
thilo

@thaala
Copy link
Author

thaala commented Nov 11, 2024

Hi,
in meanwhile i'm ready with env setup and have running some test progs with cubeMXide. Seems that spi dma is working with testprog.
Now i m trying to use mbed as work- and debug-space but i am unable to setup remora6 workspace in mbed by a selection of custom target skrv3 or octopus446.
This is a miracle to me. i need a kick in the ...
"How to": A first step to select TARGET_SKRV3 as build target?

Btw. is there a double of ROBIN_E3 in the custom_targets.json? it looks like a typo...
Could you please give little advice to set build target to SKRV3?

BR Thilo

@cakeslob
Copy link
Contributor

hmm cant find my writeup, its in the issues page somewhere but ill do a quick one

  1. download repo
  2. open mbed studio
  3. under "file" then "open workspace"
  4. go to the remora repo, and select the folder for workspace "/Firmware/FirmwareSource/Remora-OS6"
  5. once it opens the workspace under that folder, in the lower menu under "Libraries" select Fix all"
  6. after it downloads the mbed lib, you can then select the target, and compile

mbed1

@cakeslob
Copy link
Contributor

The Robin e3 and the robin 3 are 2 different boards

@thaala
Copy link
Author

thaala commented Nov 12, 2024

Thank you - it works.
regarding e3 board - i know that but for e3 you have two different sections...

sorry not custom_targets - it was mbed_app.json

    "ROBIN_E3": {
        "platform.stdio-baud-rate": 115200,
        "target.stdio_uart_tx": "PA_9",
        "target.stdio_uart_rx": "PA_10",
        "target.features_add": ["STORAGE"],
        "target.components_add" : ["SD"]
    },
         "ROBIN_E3": {
        "target.mbed_app_start": "0x08005000",
        "platform.stdio-baud-rate": 115200,
        "target.stdio_uart_tx": "PA_9",
        "target.stdio_uart_rx": "PA_10",
        "target.features_add": ["STORAGE"],
        "sd.SPI_MOSI": "PB_15",
        "sd.SPI_MISO": "PB_14",
        "sd.SPI_CLK":  "PB_13",
        "sd.SPI_CS":   "PA_15",
        "target.components_add" : ["SD"]
    },
    "SKR_MINI_E3": {
        "target.mbed_app_start": "0x08007000",

@thaala
Copy link
Author

thaala commented Nov 12, 2024

Hello,

after playing around with mbed studio i am really confused about selecting custom targets. None of the custom boards appears. After correct the mbed_app.json by deleting first robin_e3 entry i have a success now.

After reopen mbed studio all custom tragets appeared..

BR
Thilo

@cakeslob
Copy link
Contributor

good eye, although it doesnt seem to cause me any issues with custom targets, with or without both entries. something incorrect in custom_targets.json would describe what you are experiencing

@scottalford75
Copy link
Owner

I've dug out my old work on the SKR3 and have it working upto SPI comms. DMA appears to be working but I'm getting the request header coming back for some reason.

Currently in SMT32cubIDE but the thought is to move this into PlatformIO as Cakeslob suggested. I'd appreciate any feedback on the SPI issues...

https://github.com/scottalford75/Remora-STM32H7xx/tree/main

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants