# SKR mini e3 v2 Not found after update **URL:** \ **Category:** General Discussion\ **Created:** [October 8, 2021, 1:08am UTC](https://klipper.discourse.group/t/skr-mini-e3-v2-not-found-after-update/1061 "2021-10-08T01:08:29Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Jschools](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/jschools/32/32_2.png) [@Jschools](https://klipper.discourse.group/u/Jschools)\ **Post date:** [October 8, 2021, 1:08am UTC](https://klipper.discourse.group/t/skr-mini-e3-v2-not-found-after-update/1061/1 "2021-10-08T01:08:29Z")
After updating to v0.10 I can no longer detect my MCU. I have tried reflashing, have verified the settings are correct from the config. I have asked on discord but have not found a solution. Out of ideas what to try next. ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/2cc5314c91325e3ca1fef2cb98213ff5fdd84eb9.png) Edit: looks like I am not the only one getting this error. From Reddit: [https://www.reddit.com/r/klippers/comments/q3n3ql/cant\_find\_serialid\_using\_a\_skr\_mini\_e3\_v20/?utm\_source=share&utm\_medium=ios\_app&utm\_name=iossmf](https://www.reddit.com/r/klippers/comments/q3n3ql/cant_find_serialid_using_a_skr_mini_e3_v20/?utm_source=share&utm_medium=ios_app&utm_name=iossmf) ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [October 9, 2021, 7:58am UTC](https://klipper.discourse.group/t/skr-mini-e3-v2-not-found-after-update/1061/2 "2021-10-09T07:58:07Z")
Do a step by step analysis: - Unplug and replug USB - Run `dmesg` and you should see some information on a new USB device or potentially on some errors. Post it here - Run `ls /dev/serial/by-id/*` and post the results here - Post your klipper log ---
**Author:** ![Jschools](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/jschools/32/32_2.png) [@Jschools](https://klipper.discourse.group/u/Jschools)\ **Post date:** [October 16, 2021, 11:11pm UTC](https://klipper.discourse.group/t/skr-mini-e3-v2-not-found-after-update/1061/3 "2021-10-16T23:11:06Z")
Nothing registers in dmesg when plugging/unplugging the USB. pi@fluiddpi:~/klipper $ ls /dev/serial/by-id/\* ls: cannot access ‘/dev/serial/by-id/\*’: No such file or directory Klipper log just complains about invalid MCU. ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [October 17, 2021, 10:14am UTC](https://klipper.discourse.group/t/skr-mini-e3-v2-not-found-after-update/1061/4 "2021-10-17T10:14:31Z")
This means that the Linux Operating System does not “see” your SKR. Potential reasons: - Defect USB cable - Defect USB port (on SKR or Pi side) - Other hardware related defects - Other issues with the Pi like defect Pi SD card - Problem with the firmware on the SKR Possible solutions: - Change USB cable and try different USB ports on the Pi - Make sure to have followed [klipper/generic-bigtreetech-skr-mini-e3-v2.0.cfg at master · Klipper3d/klipper · GitHub](https://github.com/Klipper3d/klipper/blob/master/config/generic-bigtreetech-skr-mini-e3-v2.0.cfg) and [Installation - Klipper documentation](https://www.klipper3d.org/Installation.html) → `firmware.bin` needs to get renamed to `firmware.cur` on your SKR’s SD card to indicate a proper flash - Setup a new SD card for your Pi ---
**Author:** ![Jschools](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/jschools/32/32_2.png) [@Jschools](https://klipper.discourse.group/u/Jschools)\ **Post date:** [October 17, 2021, 3:36pm UTC](https://klipper.discourse.group/t/skr-mini-e3-v2-not-found-after-update/1061/5 "2021-10-17T15:36:15Z")
I have tried all of the above steps. Like I said, after updating the firmware these problems occurred. I can confirm that flashing the firmware changes to firmware.cur. I have re-imaged my pi multiple times. Something changed in the firmware that is being flashed to the SKR that is breaking this. ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [October 17, 2021, 4:47pm UTC](https://klipper.discourse.group/t/skr-mini-e3-v2-not-found-after-update/1061/6 "2021-10-17T16:47:31Z")
> [@Jschools](#): > > Something changed in the firmware that is being flashed to the SKR that is breaking this. Surely possible that it is a regression but on the other hand I would have expected more issues like yours if it is a general thing. If it is the case, then you can always go back to an older git version and try. E.g.: ```plaintext git checkout 3176150050b666a582ac0993dc14e6663133ecb9 make distclean make menuconfig make ``` This will bring you to a commit at beginning of August. To revert back to latest master issue: ```plaintext git checkout master ``` ---
**Author:** ![Jschools](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/jschools/32/32_2.png) [@Jschools](https://klipper.discourse.group/u/Jschools)\ **Post date:** [October 17, 2021, 8:17pm UTC](https://klipper.discourse.group/t/skr-mini-e3-v2-not-found-after-update/1061/7 "2021-10-17T20:17:11Z")
> [@Sineos](#): > > `git checkout 3176150050b666a582ac0993dc14e6663133ecb9` pi@fluiddpi:~/klipper $ ls /dev/serial/by-id/\* /dev/serial/by-id/usb-Klipper\_stm32f103xe\_39FFD4054255373722511757-if00 Its back!! So how do we figure out what is broken? ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [October 17, 2021, 9:21pm UTC](https://klipper.discourse.group/t/skr-mini-e3-v2-not-found-after-update/1061/8 "2021-10-17T21:21:10Z")
Now you would have to find the commit, which broke things. Obviously it is somewhere between beginning of August and release of v0.10. Here the `git bisect` command can come in handy but it requires some effort on your side. This command will always use a version halfway between a last-known good and a known bad. See here for a nice tutorial: [A beginner's guide to GIT BISECT - The process of elimination](https://www.metaltoad.com/blog/beginners-guide-git-bisect-process-elimination) After you have identified where things go wrong someone with coding knowledge (e.g. @koconnor) would have to analyze your finding. ---
**Author:** ![Jschools](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/jschools/32/32_2.png) [@Jschools](https://klipper.discourse.group/u/Jschools)\ **Post date:** [October 17, 2021, 9:32pm UTC](https://klipper.discourse.group/t/skr-mini-e3-v2-not-found-after-update/1061/9 "2021-10-17T21:32:13Z")
Bummer, this might be where it ends for me then. I would need a lot of assistance even locating the latest commit. I don’t understand how this is not a more widespread issue, I have a very common board. Thank you for your assistance. If I become braver, I’ll stumble down the git bisect route. Hopefully, this thread can continue to help other people. ---
**Author:** ![Jschools](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/jschools/32/32_2.png) [@Jschools](https://klipper.discourse.group/u/Jschools)\ **Post date:** [October 17, 2021, 11:41pm UTC](https://klipper.discourse.group/t/skr-mini-e3-v2-not-found-after-update/1061/10 "2021-10-17T23:41:13Z")
Had a friend walk me through git bisect. This was the final outcome ```auto 7f82dcb442596959c667d0ed8f19e39af3f94b0d is the first bad commit commit 7f82dcb442596959c667d0ed8f19e39af3f94b0d Author: Kevin O'Connor Date: Thu Aug 19 14:59:53 2021 -0400 endstop_phase: Use config.getintlist() for trigger_phase config option Signed-off-by: Kevin O'Connor :040000 040000 8c8ea5abf6da1ee2daa9ce493ae464cd91b952d3 a00105fc01406421e8ee5ef0f37747ca332a4698 M klippy ``` Looking at this commit it has nothing to do with why the USB would not work. Weird. ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [October 19, 2021, 5:56am UTC](https://klipper.discourse.group/t/skr-mini-e3-v2-not-found-after-update/1061/11 "2021-10-19T05:56:37Z")
> [@Jschools](#): > > Looking at this commit it has nothing to do with why the USB would not work. Weird. This is really strange. Would you please reconfirm that ```plaintext git checkout 58dedb6b16796427466816e0f6f6eaccb464ca87 make distclean make menuconfig make ``` actually works. And ```plaintext git checkout 7f82dcb442596959c667d0ed8f19e39af3f94b0d make distclean make menuconfig make ``` does not work. The mentioned bad commit does not change the MCU code, so in theory this should absolutely not lead to the issues you are seeing. ---
**Author:** ![koconnor](https://avatars.discourse-cdn.com/v4/letter/k/aca169/32.png) [@koconnor](https://klipper.discourse.group/u/koconnor)\ **Post date:** [October 19, 2021, 3:06pm UTC](https://klipper.discourse.group/t/skr-mini-e3-v2-not-found-after-update/1061/12 "2021-10-19T15:06:52Z")
FWIW, I have a skr-mini-e3-v1.2 and the bootloader is very flaky. Try to write the same image 5 times and the first four fail, but the fifth is accepted. The description above sounds like a “random failure”, you may wish to go back to the master branch and retry the flash a few times. -Kevin ---
**Author:** ![cheung](https://avatars.discourse-cdn.com/v4/letter/c/f04885/32.png) [@cheung](https://klipper.discourse.group/u/cheung)\ **Post date:** [October 31, 2021, 2:47am UTC](https://klipper.discourse.group/t/skr-mini-e3-v2-not-found-after-update/1061/13 "2021-10-31T02:47:02Z")
Hello, I have the same problem here suddenly,before i had a long time use. (ls / dev / serial / by ID , can’t find SKR v1.3)，Windows can recognize it , but RPI can’t. I try to flash different image systems many times ,but it doesn’t work.Today， motherboard is powered on again, the motherboard can be recognized.But RPI can’t recognize it after reboot now 😰 ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [November 5, 2023, 8:59pm UTC](https://klipper.discourse.group/t/skr-mini-e3-v2-not-found-after-update/1061/14 "2023-11-05T20:59:20Z")