hmm, 1.03 to 1.04.. I quickly looked over changes, nothing really stood out that should make it worst, as it appears my changes were related to midi output.. not too surprising as I was stabilising the work I was doing on the Push 1 display which was causing me issues...
console, nothing unexpected there... correctly picked up sizes,
one slight oddity, is that it uses endpoints 1 and 82 , usually you would expect 1 and 81... but this is consistent with your lsusb output, so just a bit strange, and the axoloti firmware doesn't care.
another oddity, is you should be getting a line with host interval e.g.
USB Host Input interval : 0
the only reason this 'concerns' me, is i wonder if this means your not getting other logging.
anyways no matter....
the way to proceed is to build a new firmware....
you can either do this by using a github build
by copying the firmware source (you will find it inside the axoloti app) to a new (writeable) directory
then changing the preferences to point to this directory
you will then find new menu options for flashing 'user firmware'
compile it, and check it works first...
then in usbh_conf.h you will find USBH_DEBUG_LEVEL, change this to 3 (from 2)
this will log more info.
In particular I think we are interested in seeing if the usb goes into a 'unusual state' that perhaps its not recovering from.
(it should be relatively obvious from the console when you get errors)
try running this, but send as little data as possible, as too much logging WILL break the connection.
basically the watchdog will terminate as it takes too much time to do the login. this is NOT an error condition...
you can comment out a few of the USBH_DbgLog lines in usbh_midi_core.c, if this proves difficult/excessive, but i think for input its ok.
the other thing to try
in usbh_midi_core.c. change MIDI_MIN_READ_POLL to 0, this will mean it will process messages every time chibios wakes it up.... Im not sure what this will do to overall performance, so initially test with a simple patch, and again initially try to not send too much data...
have a go with this, and see if this gives us some more info