h3n3/kiauh
1
0
Fork 0
Code Issues 46 Pull Requests 10 Packages Projects Releases Wiki Activity

New install of kiauh doesn't create a functional klipper.bin for SKR1.3 #97

New Issue
Closed
opened 2021-07-25 01:30:23 +02:00 by LoganFraser · 6 comments
LoganFraser commented 2021-07-25 01:30:23 +02:00 (Migrated from github.com)
Copy Link

I recently used kiauh to install klipper, mainsail and fluidd. I got an error connecting to my skr1.3 due to an older firmware, but had issues generating a functional klipper.bin file for it, getting usb connection fail messages on rpi bootup. I did not manually install make until after I tried to generate the klipper.bin file manually. Is it possible there's a missing dependency for make in the kiauh installation process? After following the identical settings I was using in kiauh to make the firmware manually, I was able to connect to my skr1.3 again.

I recently used kiauh to install klipper, mainsail and fluidd. I got an error connecting to my skr1.3 due to an older firmware, but had issues generating a functional klipper.bin file for it, getting usb connection fail messages on rpi bootup. *I did not manually install make until after I tried to generate the klipper.bin file manually*. Is it possible there's a missing dependency for make in the kiauh installation process? After following the identical settings I was using in kiauh to make the firmware manually, I was able to connect to my skr1.3 again.
dw-0 commented 2021-07-25 08:46:04 +02:00 (Migrated from github.com)
Copy Link

Im not sure if i understand correct.
KIAUH doesn't create a klipper.bin file automatically just by installing/cloning it.

The user always has to go into the advanced menu and from there choose the appropriate option to either build only or build and flash the firmware.

Im not sure if i understand correct. KIAUH doesn't create a klipper.bin file automatically just by installing/cloning it. The user always has to go into the advanced menu and from there choose the appropriate option to either build only or build and flash the firmware.
LoganFraser commented 2021-07-25 17:48:02 +02:00 (Migrated from github.com)
Copy Link

Process followed to create a non-functional firmware using kiauh:
Install kiauh using instructions from download page on a clean install of Raspbian buster.
Install Klipper, Mainsail and fluidd via script.
Create firmware via script, (4 then 3) using the following options:

                                 Klipper Firmware Configuration

[ ] Enable extra low-level configuration options
Micro-controller Architecture (LPC176x (Smoothieboard)) --->
Processor model (lpc1768 (100 MHz)) --->
[*] Target board uses Smoothieware bootloader
Communication interface (USB) --->

rename the generated klipper.bin file to firmware.bin, copy to SD card.
power off rpi and skr1.3
move SD card to skr1.3, restore power, wait 90 seconds, remove power.
remove SD card.

On reboot, the Pi shows many USB connection failure messages, the SD card firmware.bin has been renamed firmware.cur indicating a successful flash of a non-functional firmware.

So either the version of make used in the script is creating an issue, or the settings being passed from kiauh to make are not correct.

Process followed to create a non-functional firmware using kiauh: Install kiauh using instructions from download page on a clean install of Raspbian buster. Install Klipper, Mainsail and fluidd via script. Create firmware via script, (4 then 3) using the following options: Klipper Firmware Configuration [ ] Enable extra low-level configuration options Micro-controller Architecture (LPC176x (Smoothieboard)) ---> Processor model (lpc1768 (100 MHz)) ---> [*] Target board uses Smoothieware bootloader Communication interface (USB) ---> rename the generated klipper.bin file to firmware.bin, copy to SD card. power off rpi and skr1.3 move SD card to skr1.3, restore power, wait 90 seconds, remove power. remove SD card. On reboot, the Pi shows many USB connection failure messages, the SD card firmware.bin has been renamed firmware.cur indicating a successful flash of a non-functional firmware. So either the version of make used in the script is creating an issue, or the settings being passed from kiauh to make are not correct.
dw-0 commented 2021-07-25 17:52:11 +02:00 (Migrated from github.com)
Copy Link

So either the version of make used in the script is creating an issue

KIAUH uses the same make which is used when you build the firmware by hand.

or the settings being passed from kiauh to make are not correct.

For that to check, i need to know HOW you build the firmware by hand and which commands you exactly used.
KIAUH uses the make command as suggested in the klipper docs: https://github.com/KevinOConnor/klipper/blob/master/docs/Installation.md#building-and-flashing-the-micro-controller
Therefore its a simple make which gets executed as can be seen here: https://github.com/th33xitus/kiauh/blob/master/scripts/install_klipper.sh#L382

> So either the version of make used in the script is creating an issue KIAUH uses the same make which is used when you build the firmware by hand. > or the settings being passed from kiauh to make are not correct. For that to check, i need to know HOW you build the firmware by hand and which commands you exactly used. KIAUH uses the make command as suggested in the klipper docs: https://github.com/KevinOConnor/klipper/blob/master/docs/Installation.md#building-and-flashing-the-micro-controller Therefore its a simple `make` which gets executed as can be seen here: https://github.com/th33xitus/kiauh/blob/master/scripts/install_klipper.sh#L382
LoganFraser commented 2021-07-25 18:01:15 +02:00 (Migrated from github.com)
Copy Link

sudo apt install make
cd ~/klipper
make menuconfig
make clean
make

sudo apt install make cd ~/klipper make menuconfig make clean make
LoganFraser commented 2021-07-25 18:02:26 +02:00 (Migrated from github.com)
Copy Link

with the same options listed for firmware configuration:
[ ] Enable extra low-level configuration options
Micro-controller Architecture (LPC176x (Smoothieboard)) --->
Processor model (lpc1768 (100 MHz)) --->
[*] Target board uses Smoothieware bootloader
Communication interface (USB) --->

with the same options listed for firmware configuration: [ ] Enable extra low-level configuration options Micro-controller Architecture (LPC176x (Smoothieboard)) ---> Processor model (lpc1768 (100 MHz)) ---> [*] Target board uses Smoothieware bootloader Communication interface (USB) --->
dw-0 commented 2021-07-25 18:12:35 +02:00 (Migrated from github.com)
Copy Link

I see. I'll add an additional dependency check for make to the script before calling the make commands.
Hope that will help.

I see. I'll add an additional dependency check for `make` to the script before calling the make commands. Hope that will help.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🐛 bug
Something isn't working
 can't reproduce
➕ community extension
crowsnest
duplicate
This issue or pull request already exists
 ✨ feature request
New feature or request
 fluidd
Something that is fluidd related
 improvement
improvement of existing features/code
 invalid
klipper
Something that is klipper related
 klipperscreen
Something that is klipperscreen related
 mainsail
Something that is mainsail related
 mobileraker
moonraker
Something that is moonraker related
 not kiauh
not planned
octoeverywhere
Something that is OctoEverywhere related
 ❓ question
Further information is requested
 💤 stale
todo
wontfix
This will not be worked on
No Label 🐛 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
h3n3
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: h3n3/kiauh#97
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?