Crash downloading from Cobalt 2 from Subsurface mobile
Dirk Hohndel
dirk at hohndel.org
Wed Aug 8 15:23:15 PDT 2018
On Wed, Aug 08, 2018 at 03:54:07PM -0500, Matt Thompson wrote:
> >
> > Of course it's lying to you because it is NOT using FTDI - this is a USB
> > device that it just talks to directly.
>
> Good to know. I'll stop posting about that one in FTDI threads :)
Not a problem - you are simply reminding me that I need to fix this in our
output :-)
> > And it seems to successfully talk
> > to the Cobalt, able to download the the firmware version (that number does
> > look odd),
>
> Indeed. The firmware version reported on the device is 2.460/4
OK, so this was the firmware version, we just need to decode it :-)
161218564 is 0x99c0004 so the two words are 0x099c = 2460 and 0x0004 = 4
Bingo :-)
> > serial number (also looks a bit odd),
>
> The serial number is actually (mostly) correct. As reported on the device
> it is 4515-0833 as opposed to 45150833
So we are talking to your device just fine.
> > first dive and then move on.
> >
> > What I'd love to know is why it crashes... nothing in the log indicates
> > what's going wrong there...
>
> Yup. No other information on screen or anything. Just the Android system
> dialog telling me it crashed and offering to launch the app again.
Do you have access to adb on a computer? If you can connect to the Cobalt,
trigger the crash, then connect to a computer and run 'adb logcat' we
should be able to see a backtrace. That might help us figure out what's
wrong.
/D
More information about the subsurface
mailing list