Unable to get Katapult UUI

General Discussion
1

Basic Information:

Printer Model: Voron 2.4
MCU / Printerboard: octopus
Host / SBC: BTTPI SB2209 with U2C
klippy.log Not applicable

Describe your issue:

…“Detected UUID: 41b40a950e8a, Application: Klipper this should be Application: Katapult”
Have deleted Klipper and Katapult but keep getting the same result. I have changed the BTT canbus 2209 Thought I might have damaged the old one. Looked up the trouble shooting which indicates starting the machine again and rebooting which I have done also many times.
I have followed Esoterical very clear instructions for toolhead flashing each time but have the same results
When I download Katapult it says successful download.
Is there any way I can view the serial numbers in mainsail thought I had seen that you could somewhere in all the reading I have done
Any help would be much appreciated as I am sure I have missed something simple

Screenshot 2024-06-10 Putty
Screenshot 2024-06-10 Putty662×852 23.1 KB

Screenshot config 10 June 2024

2

Just to be sure:
What firmware is on your U2C? If 41b40a950e8a allways reports Application: Klipper this sounds like it is your U2C.
When flashing katapult over USB have just this one device connected to the pi while flashing.

Sidenote: What octopus version do you have? Octopus is also usable as a usb-can bridge.

3

Thank you but I tried again with only one item attached still the same result. I do have an octopus 1.1 but all the things I read advised that the U2c is maybe the best way to go.
Think I will have one more go right back to the main board again and see what happens.
Any more advice gratefully received.

4

You have a BTT Pi - do you have the U2C module for it or the normal U2C V2?

There are two mcu version of the octopus v1.1 - F407 and F446 - which one do you have?

5

Hi thanks for helping I have the 446 version

6

That answers half of my questions. What about my first one?

7

Sorry I missed the first one I have a BTT U2C v2.1

8

How have you wired the BTT U2C?

I don’t know how long you’ve been here, but over the past few weeks, there have been some lively discussions regarding the BTT U2C.

9

Thanks I must have missed those will look back I take that they are under U2C

10

I have wired it as per picture

20240623_1311341
20240623_13113411920×1920 254 KB

11

So, on the left end it’s the USB C connector, in the middle facing downward it’s a Microfit connector passing power and the two CAN signals and on the right is the power. Correct?

Now, using a DMM, check the continuity of the wires and make sure power is getting to your toolhead board.

12

Thanks for your help will try tomorrow

13

All checked out shows flashing red light on toolhead showing that it is in katapult mode but still comes back biqu@TimVoron:~$ python3 ~/katapult/scripts/flashtool.py -i can0 -q
Resetting all bootloader node IDs…
Checking for Katapult nodes…
Detected UUID: 41b40a950e8a, Application: Klipper
Query Complete
Not Katapult application
I have followed Esoterical and started again 4 times now still the same result

14

Sorry, what is the toolhead controller that you’re using? I don’t seem to be able to find it in this thread.

Along with that, what are the “Esoterical” instructions that you’re going through?

15

BTTPI SB2209 with U2C with BTT EBB sb 2209 can v1.0
Toolhead Flashing | Esoterical’s CANBus Guide

16

Sorry for taking so long to get back to you.

Now, for your BTT EBB SB2209, how did you configure your make?

From your original post, it looks like you followed the “Esoterical” example which you’ve posted as:

Screenshot config 10 June 2024

BUT you aren’t working with a toolhead controller with a STM32G0B1 MCU, you’re working with the RP2040 which should have the make menuconfig of:

image
image944×356 66.4 KB

as detailed in the BTT EBB SB2209 Build Guide which you can find here:

Can you confirm the make menuconfig you used?

The Esoterical instructions are all right, but BTT did a good job on their instructions (they start at page 25 of the Build Guide) - could I suggest that you follow them and let us know how you make out?

17

Same sry for the later reply from my side - did not get a ping/email notification.

Are you really sure that 41b40a950e8a is your EBB?
Can you do a dmesg -W without anything connected to the BTT Pi and then plug your U2C in.
Paste the log that appears after plugging in here.
I want to know if your U2C has Klipper in USB-CAN bridge mode on it or the candleLight_fw.

18

[quote=“docgalaxyblock, post:17, topic:16949”]
dmesg -W
[/quote]This is the answer to your last question
I have also attached a picture of the toolhead board

20240626_1542471
20240626_15424711920×1920 235 KB

I have another toolhead board which I thought I had made u/s but maybe not picture below
20240626_toolhead 2
20240626_toolhead 21920×1920 228 KB

biqu@TimVoron:~ dmesg -W [ 180.023881] panfrost 1800000.gpu: Unhandled Page fault in AS0 at VA 0x000000000600BE00 Reason: TODO raw fault status: 0x1C8 decoded fault status: SLAVE FAULT exception type 0xC8: PERM_FAULT_0 access type 0x1: EXECUTE source id 0x0 [ 180.024005] panfrost 1800000.gpu: js fault, js=1, status=JOB_BUS_FAULT, head=0x6ca6240, tail=0x6ca6240 [ 212.958932] usb 8-1: new full-speed USB device number 2 using ohci-platform [ 213.193985] usb 8-1: New USB device found, idVendor=1d50, idProduct=606f, bcdDevice= 0.00 [ 213.194012] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 213.194019] usb 8-1: Product: candleLight USB to CAN adapter [ 213.194025] usb 8-1: Manufacturer: bytewerk [ 213.194030] usb 8-1: SerialNumber: 002F004E5542501720303939 [ 213.379012] gs_usb 8-1:1.0: Configuring for 1 interfaces [ 213.381652] usbcore: registered new interface driver gs_usb [ 213.549280] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready [ 240.022753] panfrost 1800000.gpu: Unhandled Page fault in AS0 at VA 0x000000000600BD00 Reason: TODO raw fault status: 0x1C8 decoded fault status: SLAVE FAULT exception type 0xC8: PERM_FAULT_0 access type 0x1: EXECUTE source id 0x0 [ 240.022870] panfrost 1800000.gpu: js fault, js=0, status=JOB_BUS_FAULT, head=0x6d16880, tail=0x6d16880 biqu@TimVoron:~ dmesg -W
[ 180.023881] panfrost 1800000.gpu: Unhandled Page fault in AS0 at VA 0x000000000600BE00
Reason: TODO
raw fault status: 0x1C8
decoded fault status: SLAVE FAULT
exception type 0xC8: PERM_FAULT_0
access type 0x1: EXECUTE
source id 0x0
[ 180.024005] panfrost 1800000.gpu: js fault, js=1, status=JOB_BUS_FAULT, head=0x6ca6240, tail=0x6ca6240
[ 212.958932] usb 8-1: new full-speed USB device number 2 using ohci-platform
[ 213.193985] usb 8-1: New USB device found, idVendor=1d50, idProduct=606f, bcdDevice= 0.00
[ 213.194012] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 213.194019] usb 8-1: Product: candleLight USB to CAN adapter
[ 213.194025] usb 8-1: Manufacturer: bytewerk
[ 213.194030] usb 8-1: SerialNumber: 002F004E5542501720303939
[ 213.379012] gs_usb 8-1:1.0: Configuring for 1 interfaces
[ 213.381652] usbcore: registered new interface driver gs_usb
[ 213.549280] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
[ 240.022753] panfrost 1800000.gpu: Unhandled Page fault in AS0 at VA 0x000000000600BD00
Reason: TODO
raw fault status: 0x1C8
decoded fault status: SLAVE FAULT
exception type 0xC8: PERM_FAULT_0
access type 0x1: EXECUTE
source id 0x0
[ 240.022870] panfrost 1800000.gpu: js fault, js=0, status=JOB_BUS_FAULT, head=0x6d16880, tail=0x6d16880

[ 300.015925] panfrost 1800000.gpu: Unhandled Page fault in AS0 at VA 0x000000000600BD00
Reason: TODO
raw fault status: 0x1C8
decoded fault status: SLAVE FAULT
exception type 0xC8: PERM_FAULT_0
access type 0x1: EXECUTE
source id 0x0
[ 300.015994] panfrost 1800000.gpu: js fault, js=0, status=JOB_BUS_FAULT, head=0x7166880, tail=0x7166880

19

When posing code snippets, please always use Preformatted Text to put it in the correct form. Else things get mashed up.

Format

2 Likes
20

First what @EddyMI3D wrote

Ok it reports itself as it has the candleLight FW flashed.
Will look something up and report tomorrow back
:sleeping_bed: