Can"t connect anymore?!

#1

last week everything was fine. Went to use today and I'm getting this message.
USB device found
connected
java.lang.Exception: cpuserial has wrong length
java.lang.Exception: cpuserial has wrong length
at axoloti.HWSignature.Verify(HWSignature.java:111)
at axoloti.USBBulkConnection.connect(USBBulkConnection.java:315)
at axoloti.MainFrame.jCheckBoxConnectActionPerformed(MainFrame.java:727)
at axoloti.MainFrame.access$500(MainFrame.java:89)
at axoloti.MainFrame$8.actionPerformed(MainFrame.java:521)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2022)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2348)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
at javax.swing.JToggleButton$ToggleButtonModel.setPressed(JToggleButton.java:308)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:252)
at java.awt.Component.processMouseEvent(Component.java:6533)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3324)
at java.awt.Component.processEvent(Component.java:6298)
at java.awt.Container.processEvent(Container.java:2236)
at java.awt.Component.dispatchEventImpl(Component.java:4889)
at java.awt.Container.dispatchEventImpl(Container.java:2294)
at java.awt.Component.dispatchEvent(Component.java:4711)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4888)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4525)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4466)
at java.awt.Container.dispatchEventImpl(Container.java:2280)
at java.awt.Window.dispatchEventImpl(Window.java:2746)
at java.awt.Component.dispatchEvent(Component.java:4711)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:90)
at java.awt.EventQueue$4.run(EventQueue.java:731)
at java.awt.EventQueue$4.run(EventQueue.java:729)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:728)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

Control transfer failed: -7
Ping: WaitSync Timeout, disconnecting now
Disconnect request
Control transfer failed: -7
Control transfer failed: -7
Control transfer failed: -7
Control transfer failed: -7
I'm on a MacBook Pro 10.13.6
any ideas?

#2

installed on a diffrent computer. Imac...
same message.

#3

Hello. Do the two LEDs flash when power is applied? They flash back and forth,with the left one staying on.
After:
USB device found
connected

you get:
Authentic Axoloti Core

The Java error messages are from the patcher software. My thoughts are: is this 'corrupted' firmware or a hardware failure? The USB connected suggests the client USB chip is ok, but not the MCU?
Is your Axoloti just the bare-board or is it in a case? Perhaps there was ESD damage from handling it?

#4

Thanks for your reply. Somehow it appears the sd card became corrupted?!The card is only a week old with two saves to it.With the card removed it's connecting. Will try to reformat the card and retry.
Thanks again.

#5

That's a relief. So if it gets stuck reading the SD card during boot-up, that's it. No further communication and the Patcher throws a terminal-looking error.

#6

Yeah. With the cpuserial errors I though something had fried somehow. So glad it was the card. I just got this thing! Live and learn.