[BUG] Unresponsive motherboard after trying to flash OG firmware about marlin-ai3m HOT 9 CLOSED

On Mon, Sep 25, 2023 at 1:11 AM David Ramiro ***@***.***> wrote: Is the red LED on the motherboard on? Try turning off the power supply, disconnecting USB, then setting the jumper on the motherboard from DC to USB and connecting USB again. This might get you a connection and the ability to flash. — Reply to this email directly, view it on GitHub <#141 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7N6PE6LA333UKG5JJ7Q3LX4E4EFANCNFSM6AAAAAA5FIG34Q> . You are receiving this because you authored the thread.Message ID: ***@***.***>

On Mon, Sep 25, 2023 at 5:23 PM paul beard ***@***.***> wrote: The red light is on until/unless I move that jumper. No connection either way. The power supply fan blows regardless. Moving the jumper means no screen to go with no red light. I have the little USB flashing dongle on its way to me, in case that's all that's needed here. Is there anything else I can try in the meantime? On Mon, Sep 25, 2023 at 1:11 AM David Ramiro ***@***.***> wrote: > Is the red LED on the motherboard on? > > Try turning off the power supply, disconnecting USB, then setting the > jumper on the motherboard from DC to USB and connecting USB again. This > might get you a connection and the ability to flash. > > — > Reply to this email directly, view it on GitHub > <#141 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA7N6PE6LA333UKG5JJ7Q3LX4E4EFANCNFSM6AAAAAA5FIG34Q> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > -- Paul Beard / www.paulbeard.org/

On Mon, Oct 2, 2023 at 8:57 AM David Ramiro ***@***.***> wrote: Those Atmega boards are seldom bricked beyond repair, so a flash via serial has good chances of reviving it. That being said, just flashing a hex without bootloader should never have the board lose the ability to flash via USB like that, so either something went wrong while flashing or there was some preexisting defect. This is actually the first report of a "brick" like that if you search through the issues on here, so I'm really not sure how to help. Are you positive that you used the correct original firmware? There are many versions of the i3 Mega out there nowadays and the 2 versions I provide on my webspace might be outdated. — Reply to this email directly, view it on GitHub <#141 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7N6PCZMKPHH724WPHIJ43X5LP67AVCNFSM6AAAAAA5FIG34SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBTGI4DKMBZGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

On Mon, Oct 2, 2023 at 4:33 PM paul beard ***@***.***> wrote: Thanks for the reply. I pulled the firmware from AnyCubic, I think, but the real problems were with whatever I updated with. I think I picked the right hex but maybe I missed something. There are several variants of this model, as it turns out. The firmware update was when the touchscreen became inop and where I can't reconnect via USB. Wishing there was something like the hard reset sequence on open firmware compliant routers as an option here…been down that road many times. When that serial cable arrives, I'll see if I get some resolution. My best bet may be to get a modern motherboard for it, and skip all this. Best case is if I have a stock anycubic mega s and after running it alongside a Prusa, I have to think about that. I'll look at the anycubic site again to see if I missed anything or if there is any update. On Mon, Oct 2, 2023 at 8:57 AM David Ramiro ***@***.***> wrote: > Those Atmega boards are seldom bricked beyond repair, so a flash via > serial has good chances of reviving it. That being said, just flashing a > hex without bootloader should never have the board lose the ability to > flash via USB like that, so either something went wrong while flashing or > there was some preexisting defect. > > This is actually the first report of a "brick" like that if you search > through the issues on here, so I'm really not sure how to help. Are you > positive that you used the correct original firmware? There are many > versions of the i3 Mega out there nowadays and the 2 versions I provide on > my webspace might be outdated. > > — > Reply to this email directly, view it on GitHub > <#141 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA7N6PCZMKPHH724WPHIJ43X5LP67AVCNFSM6AAAAAA5FIG34SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBTGI4DKMBZGI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > -- Paul Beard / www.paulbeard.org/

On Tue, Oct 3, 2023 at 6:56 PM paul beard ***@***.***> wrote: Well, I seem to be at an impasse here. I can connect the board via a USBtiny dongle to a machine that supports avrdude. I get a green light on the USBtiny device and power LED on the trigorilla board but finding the serial port in macOS is beyond my skills. Lots of searches and nothing had worked: the USBtiny shows I assume the USBtiny is connected properly or the LEDs wouldn't light up. I'll have to look around to find out how to get this all working. This obviously precludes buying an upgrade board since I would be in the same situation with it. I realized this is beyond the scope of the firmware development process but maybe you can think of some way to unbrick this thing or get another working motherboard. Maybe the board itself is damaged in some way, I have no way to tell. It does boot and display the UI but nothing except changing pages within it. ioreg -p IOUSB -l -b | grep -E "@|PortNum|USB Serial Number" will reveal the USBtiny… +-o ***@***.*** <class IOUSBHostDevice, id 0x1000a62fc, registered, matched, active, busy 0 (5 ms), retain 18> but nothing useful appears in /dev Thanks for any info you can share. On Mon, Oct 2, 2023 at 4:33 PM paul beard ***@***.***> wrote: > Thanks for the reply. I pulled the firmware from AnyCubic, I think, but > the real problems were with whatever I updated with. I think > I picked the right hex but maybe I missed something. There are several > variants of this model, as it turns out. The firmware update was when the > touchscreen became inop and where I can't reconnect via USB. Wishing there > was something like the hard reset sequence on open > firmware compliant routers as an option here…been down that road many > times. When that serial cable arrives, I'll see if I get some resolution. > My best bet may be to get a modern motherboard for it, and skip all this. > Best case is if I have a stock anycubic mega s and after running it > alongside a Prusa, I have to think about that. > > I'll look at the anycubic site again to see if I missed anything or if > there is any update. > > On Mon, Oct 2, 2023 at 8:57 AM David Ramiro ***@***.***> > wrote: > >> Those Atmega boards are seldom bricked beyond repair, so a flash via >> serial has good chances of reviving it. That being said, just flashing a >> hex without bootloader should never have the board lose the ability to >> flash via USB like that, so either something went wrong while flashing or >> there was some preexisting defect. >> >> This is actually the first report of a "brick" like that if you search >> through the issues on here, so I'm really not sure how to help. Are you >> positive that you used the correct original firmware? There are many >> versions of the i3 Mega out there nowadays and the 2 versions I provide on >> my webspace might be outdated. >> >> — >> Reply to this email directly, view it on GitHub >> <#141 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AA7N6PCZMKPHH724WPHIJ43X5LP67AVCNFSM6AAAAAA5FIG34SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBTGI4DKMBZGI> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> > > > -- > Paul Beard / www.paulbeard.org/ > -- Paul Beard / www.paulbeard.org/