Firmware compilation .config files

Question

Firmware compilation .config files

Closed this issue a year ago · 3 comments

I'd like to compile my own Klipper firmware for my Neptune 3 Plus, however when I flash it, I can no longer communicate over USB, even though I have that config option on. Only your ZNP_ROBIN_NANO.bin file (for the USB version) posted here works for some reason. I think I have the config settings wrong (from make menuconfig). Not asking for support from you with that, but is it possible you could commit to this repo the .config files that you generated from make menuconfig to build both the UART and USB versions of the firmware?

For example, in the klipper source, after you save your menuconfig, a hidden .config file is created with those settings you selected from menuconfig:

staehle@machine ~/g/p/klipper $ ls -aF
./   config/  .git/     klippy/  out/      src/   .config      COPYING     Makefile
../  docs/    .github/  lib/     scripts/  test/  .config.old  .gitignore  README.md

Thanks!

Answer 1 · 2023-08-24T16:48:51.000Z

To clarify, you went into make menuconfig, you selected use extra low level settings, selected stm32f401, 32k bootloader, 8mhz crystal, pa10/pa9 for USB, save, exit and compile (make), rename to ZNP_ROBIN_NANO.bin and you're having issues? That's all I ever really have to do. Check the baudrate and make sure it's set to 250000 or you have to specify what the baud is in your mcu section. Other than that, it should be pretty cut and dry. I don't have the .config file handy at the moment.

…

________________________________ From: Jake Staehle ***@***.***> Sent: Thursday, August 24, 2023 12:40 PM To: TheFeralEngineer/Klipper-for-Elegoo-Neptune-series-3D-Printers ***@***.***> Cc: TheFeralEngineer ***@***.***>; Mention ***@***.***> Subject: [TheFeralEngineer/Klipper-for-Elegoo-Neptune-series-3D-Printers] Firmware compilation .config files (Issue #27) Hi @TheFeralEngineer<https://github.com/TheFeralEngineer> ! I'd like to compile my own Klipper firmware for my Neptune 3 Plus, however when I flash it, I can no longer communicate over USB, even though I have that config option on. Only your ZNP_ROBIN_NANO.bin file (for the USB version) posted here works for some reason. I think I have the config settings wrong (from make menuconfig). Not asking for support from you with that, but is it possible you could commit to this repo the .config files that you generated from make menuconfig to build both the UART and USB versions of the firmware? For example, in the klipper source, after you save your menuconfig, a hidden .config file is created with those settings you selected from menuconfig: ***@***.*** ~/g/p/klipper $ ls -aF ./ config/ .git/ klippy/ out/ src/ .config COPYING Makefile ../ docs/ .github/ lib/ scripts/ test/ .config.old .gitignore README.md Thanks! — Reply to this email directly, view it on GitHub<#27>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARUZ2LN267D665Z2OK7UFGDXW57ZBANCNFSM6AAAAAA35JRV2U>. You are receiving this because you were mentioned.Message ID: ***@***.***>

Answer 2 · 2023-08-24T16:56:15.000Z

Ohh okay, I had the communication interface selection wrong. I'll blame Klipper for the confusion there because that menu looks like:

(Top) → Communication interface
                                             Klipper Firmware Configuration
(X) USB (on PA11/PA12)
( ) Serial (on USART1 PA10/PA9)
( ) Serial (on USART1 PB7/PB6)
( ) Serial (on USART2 PA3/PA2)
( ) Serial (on USART2 PD6/PD5)

I had USB (on PA11/PA12) selected (because it says "USB" haha), but you're saying I actually want Serial (on USART1 PA10/PA9) to actually select USB.

And now I noticed that you wrote "Select (Serial (on # USART1 PA10/PA9) for the communication interface." and meant "USB" by that. Got it.

I'll compile again and try it! Thanks for the quick reply!

Answer 3 · 2023-09-17T15:16:19.000Z

Hey sorry I forgot to provide an update. Changing it to PA10/PA9 was the solution! I compiled and flashed the binary, and it worked just fine! Thank you!