search

Mellow-3D / FLYF407ZG

31 stars 11 forks source link

Klipper can not communicate. #8

Open ghost opened 4 years ago

ghost commented 4 years ago

When i upload klipper FW, then can not communicate klipper with MCU. kép Maybe bootloader problem?

FLYmaker commented 4 years ago

I study how to use

AniInABox commented 4 years ago

I have the same Issue. Kevin from Klipper said that this should be analyzed with a Hardware Debugger und seams to be a Bootloader Problem.

kakou-fr commented 4 years ago

waiting for it too

kakou-fr commented 4 years ago

Could you publish the source of the bootloader ?

robustini commented 4 years ago

Can someone help me? See here: https://github.com/FLYmaker/FLYF407ZG/issues/9

ghost commented 4 years ago

Could you publish the source of the bootloader ?

I need this bootloader too.

AniInABox commented 4 years ago

Does something happen in the Background, or can i put the Board into trash?

Please give US the Bootloader Code vor the Wiring Diagramm. Wrn want to usw this Board with Klipper and other Firmwares.

ghost commented 4 years ago

Work with Marlin!

AniInABox notifications@github.com ezt írta (időpont: 2020. febr. 16., V 16:28):

Does something happen in the Background, or can i put the Board into trash?

Please give US the Bootloader Code vor the Wiring Diagramm. Wrn want to usw this Board with Klipper and other Firmwares.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/FLYmaker/FLYF407ZG/issues/8?email_source=notifications&email_token=ALRBIHRFDB4VABGWVTSSBALRDFLTPA5CNFSM4KM2I6HKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL4KBNY#issuecomment-586719415, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALRBIHTVRAIJ4ZTI7RQLD43RDFLTPANCNFSM4KM2I6HA .

ghost commented 4 years ago

My opinion is: FLYmaker user is chinese. New coronavirus is much more important than FLYboard.

FLYmaker commented 4 years ago

klipper FW requires DVECT_TAB_OFFSET = 0x8000   The bootloader writes the klipper FW to the address after 0x8008000

FLYmaker commented 4 years ago

我的意见是：FLYmaker用户是中国人。新的冠状病毒比FLYboard重要得多。

thank you Thankfully i did not get sick

AniInABox commented 4 years ago

klipper FW requires DVECT_TAB_OFFSET = 0x8000 The bootloader writes the klipper FW to the address after 0x8008000

What does that mean? I have to configure Klipper to Write to another Start Position?

AniInABox commented 4 years ago

Here is the Answer from Kevin (Klipper):

Setting a "32KiB bootloader" in "make menuconfig" sets the firmware address to 0x8008000. So, the problem must be something else.

-Kevin

kakou-fr commented 4 years ago

just tested, it work with klipper

SmoothieAq commented 4 years ago

@kakou-fr could you please give some details on how you made it work.

I tried:

  1. make menuconfig with:
    • Micro-controller Architecture: STMicroelctronics STM32
    • Processor model: STM32F407
    • Bootloader offset: 32KiB
    • Clock reference: 8 MHz crystal
    • Use USB instead of serial
  2. make the klipper.bin
  3. format a 8GB sd card on my Windows pc with FAT32
  4. Copy the klipper.bin to that
  5. Place the sd card in the FLY and connect it with USB to the Raspberry
  6. Power off, then power on

When I look in /dev, I can not see anything that looks like an usb port the the FLY On the FLY I have 3 green leds

I am at loss what to do now, help appreciated :-)

kakou-fr commented 4 years ago

│ │ [ ] Enable extra low-level configuration options │ │ │ │ Micro-controller Architecture (STMicroelectronics STM32) ---> │ │ │ │ Processor model (STM32F407) ---> │ │ │ │ Bootloader offset (32KiB bootloader (SKR-PRO)) ---> │ │ │ │ [*] Use USB for communication (instead of serial) │ │ │ │ USB ids --->

copy klipper/bin and rename it firmware.bin

SmoothieAq commented 4 years ago

yeah, forgot that. Now I get an usb-Klipper_xxx in /dev/serial/by-id :-D Thank you!

I'll try to configure the first parts of klipper this weekend...

SmoothieAq commented 4 years ago

It is up an running now. Seems you just have to read the 10 line instruction in generic-flyboard.cfg and do what it says. What with all the negative fuzz??