-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No firmware for STM32G0B0RET6 ? #775
Comments
BUMP |
Hello, thank you for the response.
With regard to the picture you have shared, where is this picture from?
Where does this code need to be implemented?
…On Tue, Oct 8, 2024 at 4:26 PM lwq690 ***@***.***> wrote:
Snipaste_2024-10-08_18-55-39.png (view on web)
<https://github.com/user-attachments/assets/3300a60e-482d-4743-af48-e94066470a03>
—
Reply to this email directly, view it on GitHub
<#775 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE76DANBP6HBVBZWC5PF5QDZ2O267AVCNFSM6AAAAABLMBDDBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJZGUZDGNRZG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Regards,
Amit Kumar.
9036179216
|
Hello,
I think the image you shared is klipper.
I am looking for marlin source code.
…On Wed, Oct 9, 2024 at 12:55 PM Amit Kumar ***@***.***> wrote:
Hello, thank you for the response.
With regard to the picture you have shared, where is this picture from?
Where does this code need to be implemented?
On Tue, Oct 8, 2024 at 4:26 PM lwq690 ***@***.***> wrote:
> Snipaste_2024-10-08_18-55-39.png (view on web)
> <https://github.com/user-attachments/assets/3300a60e-482d-4743-af48-e94066470a03>
>
> —
> Reply to this email directly, view it on GitHub
> <#775 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AE76DANBP6HBVBZWC5PF5QDZ2O267AVCNFSM6AAAAABLMBDDBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJZGUZDGNRZG4>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
--
Regards,
Amit Kumar.
9036179216
--
Regards,
Amit Kumar.
9036179216
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bought BIGTREETECH SKR Mini E3 V3.0 from BIGTREETECH store on Amazon UK
Connected board and Marlin was showing fine and I could probe the MCU from the pi via USB. Downloaded the correct prebuilt firmware from github and I could tell it flashed to some degree as screen was now all blue no longer showing Marlin. From this point onwards I cannot probe MCU via USB.
The description on amazon states STM32G0B1RET6 but on inspection it's been shipped with a STM32G0B0RET6.
Flashed the Marlin firmware from github even though it's probably for the wrong MCU and the screen comes back to life with Marlin but still cannot probe MCU via USB.
I have watched a good 10 videos covering the creation of firmware, followed the standard settings for STM32G0B1RET6 but changed just the MCU to STM32G0B0RET6 and it still does not fix the issues.
I suspect at this point the usb port is faulty but it would be nice if someone were to compile and upload a tested firmware.bin for this MCU. Maybe there is no real difference and the compiled firmware should be working fine. despite wrong MCU selection.
sudo dmesg -w output.....
[ 48.905983] Indeed it is in host mode hprt0 = 00021501
[ 49.093787] usb 1-1: new full-speed USB device number 2 using dwc_otg
[ 49.094255] Indeed it is in host mode hprt0 = 00021501
[ 49.281841] usb 1-1: device descriptor read/64, error -71
[ 49.390237] Indeed it is in host mode hprt0 = 00021501
[ 49.577785] usb 1-1: device descriptor read/64, error -71
[ 49.685902] Indeed it is in host mode hprt0 = 00021501
[ 49.873868] usb 1-1: new full-speed USB device number 3 using dwc_otg
[ 49.874485] Indeed it is in host mode hprt0 = 00021501
[ 50.061878] usb 1-1: device descriptor read/64, error -71
[ 50.170388] Indeed it is in host mode hprt0 = 00021501
[ 50.361847] usb 1-1: device descriptor read/64, error -71
[ 50.469964] usb usb1-port1: attempt power cycle
edit, update...
Second board arrived from amazon, G0B1 instead of the G0B0 and everything is working as expected so it was either a duff USB port or the firmware that killed it.
The text was updated successfully, but these errors were encountered: