Caught exception!

#1

.. And I'm feeling proud as a cat with a mouse! wink

This happened when triggering samples with a Korg Nanopad 2.

Control transfer failed: -7
connected
java.lang.Exception: cpuserial has wrong length
at axoloti.HWSignature.Verify(HWSignature.java:96)
at axoloti.USBBulkConnection.connect(USBBulkConnection.java:321)
at axoloti.MainFrame.jCheckBoxConnectActionPerformed(MainFrame.java:769)
at axoloti.MainFrame.access$400(MainFrame.java:80)
at axoloti.MainFrame$7.actionPerformed(MainFrame.java:410)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2022)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2346)
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:6525)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3324)
at java.awt.Component.processEvent(Component.java:6290)
at java.awt.Container.processEvent(Container.java:2234)
at java.awt.Component.dispatchEventImpl(Component.java:4881)
at java.awt.Container.dispatchEventImpl(Container.java:2292)
at java.awt.Component.dispatchEvent(Component.java:4703)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4898)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4533)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4462)
at java.awt.Container.dispatchEventImpl(Container.java:2278)
at java.awt.Window.dispatchEventImpl(Window.java:2750)
at java.awt.Component.dispatchEvent(Component.java:4703)
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$1.doIntersectionPrivilege(ProtectionDomain.java:75)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:86)
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$1.doIntersectionPrivilege(ProtectionDomain.java:75)
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)

#2

are you sure your cat didnt tread on the mouse? smile (my kittens do all the time!)

seriously though... to me this looks like, you had data failure (-7) , and then you pressed 'connect' to reconnect.
and this failed, to verify the serial number..

assuming this is correct... can you tell me ...

  • did the patch continue to run, even though not connected (patches don't need the UI to run, so sometimes the UI gets disconnected but the patch carries on fine)
  • did you have to power cycle your axoloti to get it working again? (if the patch had crashed, this might explain the failure on reconnection) ( did you do this after you hit connect?)
  • can you reproduce it, reliably.
  • is the CPU highly loaded?
  • when you reconnect the axoloti board, do you get a 'soft watch report' ?

we have seen -7 failures before, and I've seen the verify fail too... I think when the board had crashed,
but I don't think I can reliably reproduce yet... it just sometimes happens, so a reproducible case would help alot.

#3

Yeah, this is what happens when you're trying to debug in the middle of the night when u should have gone to sleep hours ago..
Probably won't be able to reproduce it, but I'll get back 2 u if I do.

Where can I read up on the failure codes?

#4

that is a very good question... @johannes ?

I've so far seen -1,-4, -7, -9 ... If Johannes doesn't know off hand, I'll go check the code.
and then put something in the user guide section (I suspect the codes won't tell us a huge amount)

#5

ok, i checked the source code... they are basically errors writing to USB

Ive details them in a new topic (and probably will expand later), but as mentioned they don't really tell us much more than we could not write to the board ... -7 is Timeout, this probablymeans board is not 'acking' the data sent to it, probably because its crashed, so not processing USB packets.

Axoloti error codes

#6

Good, thanks for the info even tho it is as you say, a tad unspecific! :3

How bout crashes when not running in live mode, will the console return error messages anyway?