ok i messed something up n cant figure out my way back. Im just not sure what logs to post.
#ls /dev/serial/by-id ls: cannot access '/dev/serial/by-id': No such file or directory
daring kindle
weak pagoda
you need to see /* not the folder /by-id
SO the full command is " ls /dev/serial/by-id/* "
daring kindle
yes i know know. my apologies. when i run ls /dev , serial isnt even in there anymore
ls /dev/serial/by-id ls: cannot access '/dev/serial/by-id': No such file or directory
austere inlet
<@216564703185338369>
Don't ping me. I will get to the posts if I have time for it.
Remember that we are all doing that in our free time and don't get paid in any way
daring kindle
I can't imagine how annoying this must get. My apologies, please forgive me. At this point as bad I just want to be setup and printing, I'll pay you for your time. I just saw many people pinging many people yourself included while desperately searching for a solution all night with hardly no sleep and im still about to have to go to work. I thought I was doing the right thing. It wont' happen again .
austere inlet
I ping people inside their own thread, or the dev that has much more knowledge on some topics. Not everyone of the crew is reading every thread. So I will only ping when I know that he most likely has the answer.
Send the output of following commands:
lsusbapt list udev
daring kindle
oh ok. I understand.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@amber nymph:~/klipper $ apt list udev
Listing... Done
udev/oldstable,now 247.3-7+rpi1+deb11u2 armhf [installed]
austere inlet
Run curl -sSL https://raw.githubusercontent.com/mainsail-crew/MainsailOS/develop/patches/udev-fix.sh | bash
daring kindle
pi@amber nymph:~ $ curl -sSL https://raw.githubusercontent.com/mainsail-crew/MainsailOS/develop/patches/udev-fix.sh | bash
MainsailOS Patcher - udev rule fix
Ahoi!
Please be patient, this might take a while ...
HINT: This should also work for any other Debian/Armbian based Distribution
You'll be prompted for sudo password!
[sudo] password for pi:
Trying to patch your system ...
Get:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease [15.0 kB]
Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
Fetched 15.0 kB in 1s (10.4 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
'udev' version: 247.3-7+rpi1+deb11u2, is affected by bug ...
Install patched udev rule from systemd git repository ...
spare rover
Did you reboot the pi after installing the patch?
daring kindle
yes
austere inlet
Did you test multiple different cables and that your board is powered correctly?
daring kindle
The cable going from my board to raspi correct? i dunno it just seems like i need to reflash my board doing a make menuconfig?
austere inlet
The cable going from my board to raspi correct?
Yes
i dunno it just seems like i need to reflash my board doing a make menuconfig?
If you didn't flash some other firmware in between, then no. Your board doesn't loose randomly the firmware. If it does, something is broken
But you can ofc just try to reflash to see if it's going then again
austere inlet
Just try to reflash, maybe that will help 🤷♂️
daring kindle
I did flash marlin back on my board because I read that somewhere on here to try n do in order to get serial to show back up. I feel like I need a new sd card because the one I was trying to use is a larger sd card that I have to use an adapter with ribbon cable for. The board took marlin no problem. Ok this all started when I tried plugging up my Creality sonic pad while I was trying to get my cr touch to work properly. And it just felt like maybe a board Reflash of Klipper could possible fix the issue. Either that or I need a new cr touch all together. I’ve checked connections. Have swapped to a brand new cable and settings all seem correct seeing as it worked with these setting already before. So I recall trying to flash from the sonic pad n that’s where all hell broke loose. Because everything was working at one point right in the beginning of getting mainsail and Klipper all up n running. I was creating my own probed bed meshes n all. Now all this mess.
I’ll send outputs as soon as I get home from work in a couple hrs.
daring kindle
Did you reboot the pi after installing the patch?
Yes
spare rover
Thanks, this confirms what I expected... There is no additional Hardware detected by the kernel, so, eitjer your Flashing wasnt successful or you simply have no connection to your mcu at all.
daring kindle
so what do i need to do?
spare rover
Flash klipper to your mcu or change cables and inspect mcu board for fried components...
daring kindle
pi@amber nymph:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
What I don’t understand is how it flashes fine for marlin. But not Klipper.
spare rover
Is there now marlin on this board?
daring kindle
No I tried reflashing back to Klipper and lost the lcd screen but still no serial. Thts kinda how I been determining if the board was flashed by losing the Ender lcd screen to check it
So now I have no screen and it’s no flashing correctly it seems.
spare rover
Well if you loose Marlin Screen Menu, the flash was successful. Otherwise it wouldnt do anything.
Best advice I can give to test serial connection isnt faulty, Install Marlin again and flash a spare sdcard with Octoprint or Pronterface on your PC(which also indicates connecting mcu to PC). If octoprint cant connect to Marlin or Pronterface, cant connect, your mcu board might be ruined somehow...
austere inlet
Did we already clear out a cable failure?
daring kindle
yes its not a cable faliure. I inspected mainboard and all appears fine. I purchased a new sd card just incase
and flashed marlin back onto board with no issues
performed a new make menuconfig with correct settings which were...
- Enable extra low-level configuration options
2.STM32F103 3. 28K Bootloader 4. serial PA10 PA9
then compiled with "make" command
powered off printer and unplgged raspi from main board. inserted sd card then powered on printer. lcd goes blank, no more marlin / ender greeting as usual. waited about 10 minutes just to be sure then rebooted pi from putty and powered down printer before plugging in raspi.
once powered up, went back into putty and CD into klipper
performed a "ls /dev"
still on serial.
only serial are two other serials. A "Serial0" and "Serial1"
This sucks bad!
leave it to me to find a way to break something ina pretty uncommon way. SMH
spare rover
and flashed marlin back onto board with no issues
Did you check with Pronterface or Octoprint, just to verify it can connect to Marlin? Because even Marlin has a serial interface
daring kindle
no i didnt im just unfamilar with that. i suppose i can research it
is there a guide you know of?
spare rover
daring kindle
thanks. one sec
daring kindle
do i needto reflash marlin?
daring kindle
my computer isnt picking up my 3d printer. but its been that way since long before flasjing marlin. because i remember when i fist got my pri nter i treied hooking it up to my laptop to see if i could control it with crealuty software and it wasnt reading it then.