-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uno Support #4
Comments
Sorry about the fairly late reply. There originally was actually Uno support back when I was first working on this (before I uploaded anything to GitHub), but an update to the Arduino libraries caused more of the RAM to be used. The main way I would make Uno support work again would be to decrease the size of the main buffer I use. Admittedly, it's been a while since I last worked on arduinogbdump, so it might take a little while for me to get back into it. |
No problem. I remembered shortly after that my Yun has a 32u4 onboard and
successfully used it to dump carts.
I did only find a small handful of games were the RAM successfully dumped
(pretty much only Pokemon games), but the ROM dumped worked for pretty much
everything I had except my Gameboy Camera cart. I would love to get the
camera RAM and ROM dumps working to retrieve some of my old stored photos.
Let me know if I can help test anything that isn't currently working, as I
find this project is a really awesome reuse of old gaming accessories.
Keep up the good work!
|
Got a compilable version for Arduino Uno. However when i launch with communicator : Got the following messages when I try to read data at the start of the app : "The Arduino isn't ready to be read() from!" Issue on github #8 |
You mention uno support is planned in the readme. Any update on that? I have several atmega328's sitting around, but unfortunately no 32u4 with a 16mhz crystal. It looks like it is currently only 15 bytes over on memory with the sketch as is. Is it an option to split the sketch into two, one for ROM operations, one for SRAM operations to shave down the memory footprint? Or perhaps one stripped down sketch for read-only, instead of r/o and r/w for sram?
Thanks for any help you can provide, looking forward to dumping some carts!
The text was updated successfully, but these errors were encountered: