Jump to content

Brad_from_the_80s

New Members
  • Content Count

    51
  • Joined

  • Last visited

Community Reputation

73 Excellent

2 Followers

About Brad_from_the_80s

  • Rank
    Star Raider

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Although I've not messed with it at all, I observed on the FB X that there are two new binaries in the /emulator partition, one named "serialinput" and one named "wireless". The "serialinput" binary is being executed immediately before launching the UI, presumably to handle the wired controller input as a sort of daemon. The "wireless" binary is not being used at all, and I can't say exactly what it does or whether it is even functional. FWIW.
  2. If they ever release an official firmware update that addresses audio lag or other enhancements I would have to update the CFW to include those.
  3. Greetings Atari fans. I have had the standard Atari Flashback X sitting around here for a few weeks and finally got around to creating a custom firmware to allow you to load additional roms with boxart from USB (using USB OTG hub/cable and a USB drive of your choice). The basic idea is the same as the firmware I created for using the SD card on the Flashback 9 series, see original thread here: Attached here you will find a CFW version for the standard Atari Flashback X, and also one for the Atari Flashback X Deluxe. The standard firmware has been tested a little, but I don't have a Deluxe model to test. However it's the exact same hack, so I think it should work for those who need it. If it does work for you then feel free to report back, or I can tweak as needed. In the zip archive you will find an atari_update.img file. You can follow the AtGames official firmware instructions to load this firmware image using the same desktop flashing tools. HOWEVER, if you have applied at least one of the earlier firmware updates then this new CFW can be applied in a manner similar/same as for the Flashback 9. Simply attach your USB drive with the atari_update.img file in the root and the system should detect the update and flash the same way it did for Flashback 9. After successfully applying the firmware delete the atari_update.img file from your USB drive. As before, the customizations are activated by the presence of the "mount_sd.ini" file in the root of your USB drive (yeah, I didn't bother renaming it). By default the custom firmware will dump the internal /rom partition from the device to your attached USB storage and then use the USB copy of /rom for game roms, box art and all-games.ini file. Also included is a sample startup.sh custom script you can include in your USB drive. This script will also dump and run the /emulator partition from your USB drive. This should allow for tweaking the artwork. One tip, if you are using an old or slow USB thumb drive (like USB 2.0), you may need to wait a few minutes to allow write operations to complete when first allowing the CFW to dump files, so be patient. I haven't messed with the Flashback X or this CFW much really. it's simple enough, and I think it should work fine, but if you do find issues just report here and we'll see what can be done about it. No warranties, use at your own risk, etc, etc. Enjoy! AR3060_CFW.zip AR3060S_Deluxe_CFW.zip
  4. The FB X never showed up in my stocking somehow, so I just ordered one. Walmertz had the 110 game version available, as I don't think the "Deluxe" is worth an extra $30. So if/when I have a modified firmware available I'll probably start a new thread.
  5. Well in spite of a little, umm, heartburn around here, I appreciate everyone contributing to add value to what I've done. I will probably try to procure a FB X in the next couple weeks and I believe I should be able to do a similar firmware update those units, TBD. I also had intended to maybe build some tool to help with the INI management, I just have to get some time to spend on it. But thanks to everyone and hope you are all enjoying your Flashback 9 a little more than before.
  6. The changes in my firmware were fairly minor, just a modified launch script which wouldn't affect emulator or rom behavior or performance. In theory you cannot brick these devices, as they will always try to load a correctly named new firmware from SD card. Are you sure you used the correct 2.1.1 version for your model number (3650 vs 3050, Gold wireless vs standard)? Although I'm not aware that this would cause the issue you describe. it could also just be a hardware issue, there are no doubt a few defective units that slip through. You might also try a different SD card, as these are sometimes defective or have performance issues.
  7. I figure the CFW are probably interchangeable, but you probably wouldn't want to use the standard HD model firmware on your Gold unit. At minimum you'd lose a few built-in games and have an arguably plainer menu, and I'm not sure if you'd then have problems with wireless controllers. The reverse situation is probably no big deal. I like the custom bezel, and all the ini file entry contributions. 👍 I still don't have an FB X. Maybe by my Christmas break, and then I can enable similar capabilities.
  8. I don't know about the Sam's Club Deluxe version. Most likely it has those 2 games hidden plus its extra 10. The custom fw that was released for USB support contains only 112 if I recall, the expected 110 plus 2 inaccessible.
  9. They are in flash storage on the device, but there are no menu entries for them, so there is no way to launch them. It's something that can probably be changed pretty easy once I have a unit and can customize the firmware a little.
  10. Interesting there's a Rockchip branded SoC this time instead of "MonkeyKing" or whatever. Still basically the same hardware as far as specs.
  11. No need for mouse. The built-in UI highlights items using primarily just the joystick and joystick button to navigate. It's simply a little custom SDL fullscreen graphical app and seems a tad clumsy, but it works. I was thinking to discard/replace the stock UI with something custom anyway. It lacks some flexibility and features I'd like, and would need more control over what it launches. I don't know yet if I can get away with just using LD_LIBRARY_PATH to supply/replace so's (I did for my SDL2 build, since I can run arbitrary code from SD card, but of course OpenGL ES was still broken), or if I truly need to customize the root partition. There is also no DirectFB lib, but not sure that's needed. Seems I have more to explore and test.
  12. I've come across that but maybe need to look at it more closely again. Lot of overlap with what I've been seeing/researching for the FB 9 (and probably FB X). So far I can build vanilla SDL2 app and it works fine (on X), as long as I don't ask for OpenGL. This is basically what the stock menu is doing and probably why it is so slow. I can build custom SDL2, patched for Mali and configured to use OpenGL ES, but the driver of course is for X which always aborts. So the main roadblock seems to be getting working OpenGL ES on a Mali non-X driver. I kind of figured the FB hardware might work okay. It only has 2 cores (1 GHz stock) but 256MB memory. And I figured with Retroarch could look into adding 5200/7800 cores later if I ever get that far, though I don't know much about those cores or their performance/quality yet.
  13. I have not tried compiling or running Stella 6 for the device so far, but I've poked around the FB 9 a bit. A few basic issues I've noticed. The version of SDL2 library on the device is compiled to use OpenGL library (as opposed to OpenGL ES), which is not present or supported on the device. Attempts to create an OpenGL ES screen through SDL fails because attempts but can't load full OpenGL. Bypassing SDL, attempts to run a test app linked against just OpenGL ES fails due to an X server abort. The kernel claims to be loading the Mali driver, but the included Mali user space driver is the X Window version, which would seem to have unnecessary performance dragging overhead were it even functional. I've not yet continued exploring to see whether this is resolvable via customization/configuration, but in basically stock state it seems it will not work.
  14. For the regular 110 game FB X, looks like there are hidden games again as I count 112. Unless I'm mistaken they are Freeway and Pitfall 2. Will be able to access them and add more if/when I have cfw ready, pretty much the same method as FB 9.
×
×
  • Create New...