Smartboy dumper does nothing

[shad0wxwolf]

Instructions on how to use this program are very vague I've attempted to dump the device using both the USB ID and the ttyacm0 and all I get is how to use the program for an output, no rom dumping or anything.

[hadess]

./smartboy-dumper /dev/ttyACM0 as root should work.

[shad0wxwolf]

this is all that happens when I run that smartboy-dumper

[hadess]

Have you tried following the instructions in https://github.com/hadess/smartboy-dumper/issues/6#issuecomment-647809700 ?

[shad0wxwolf]

Tried with root still nothing.

[shad0wxwolf]

okay I got it working but now I get this

[hadess]

Can you try running it with G_MESSAGES_DEBUG=all as an environment variable? And also please stop posting screenshots, you can cut and paste the text directly, by putting it in between 3 backticks. See the markdown help linked from the bottom right of the text entry.

[shad0wxwolf]

exported the g massages debug thing and all I get is

Opened device /dev/ttyACM0 Got ROM Size: 0 bytes (0 x 16kB) ** ERROR:smartboy-dumper.c:258:fd_watch: code should not be reached Bail out! ERROR:smartboy-dumper.c:258:fd_watch: code should not be reached

Aborted

[pawntheory]

I'm also getting this under Arch Linux 5.7.6-arch1-1. Not getting any of the debug messages with G_MESSAGES_DEBUG=all.

Running ./smartboy-dumper /dev/ttyACM0 as root gets:

*** Opened device /dev/ttyACM0
*** Got ROM Size: 2097152 bytes (128 x 16kB)
**
ERROR:smartboy-dumper.c:258:fd_watch: code should not be reached
Bail out! ERROR:smartboy-dumper.c:258:fd_watch: code should not be reached

Device opens and the size is read successfully, but after that it sets the dumper->tag_pos to IN_STARTROM, throwing the above assert. (I put a g_print under that switch case to check and it definitely is going to IN_STARTROM, not just falling through the default).

Another thing: when running any time after the first time it hangs and I have to kill it. This is the case until the device is unplugged and reinserted. This may also be a fault with my system or my USB-C adapter, however. Heck, the whole thing could be my system or adapter. I'll try a different of each when I get the chance and reply.

[hadess]

Finally got the device out of storage. I've seen one of the assertion, but it was reading a 0-sized ROM. The whole code could do with being a little more forgiving for device errors, which I'll try to do when it stops falling over and disabling USB ports after a couple of tries :/

(I also use a USB-C adapter that's super fiddly...)

[hadess]

I've ordered some USB cable bits to debug this properly.

[hadess]

There were multiple problems:

• The "No Rom" state was never reached
• The "No Rom" state didn't ask for a cartridge
• The device takes a while to detect cart removal, so can give you the name, but fallback to "No Rom" mode in the middle of gathering the metadata (name, size)

You might still need to Ctrl+C and restart the dumper if it doesn't detect carts after a while.