Jump to content

Draxxon

Banned
  • Posts

    1,925
  • Joined

Posts posted by Draxxon

  1. https://gbatemp.net/threads/custom-firmware-for-atgames-legends-flashback-with-support-for-arcade-games.527550/

    Swapping the sega core was done in test only. it never got released. gen plus gx was chosen over pico drive because it supported more extensions and would pose less questions from users. Mame2000 core got swapped to mame2003+, but i'm not sure how it all works. rmr_md / rrifonas would be the one to ask. So yeah Mame and FinalBurnAlpha roms can be add. And crazy but, Sega 32X will run on the Legends Flashback after all too.

    This was the core swap, maybe it will help. Getting Stella6 to run on this would make the FBX the "AtariBox VCS Killer" to me.




     

    core swap.rar

    • Like 1
    • Thanks 1
  2. Just now, BitMerge6502 said:

    also, for anyone that wants it, here's my AFB8 all-games.ini file. It might be useful to someone if they want to copy a specific entry for a game for use on the AFB9/X. I spent a great deal of time with the game descriptions. Most of them are excerpts from the original manuals with 2600 specific stuff that doesn't apply to AFB removed or changed (like TV picture switch & insert cartridge stuff).

    all-games.ini 533.1 kB · 1 download

    can I add any info from your file that's missing in my pack? and share it in a future update? so far I have the entries from the 9/gold/x/xdeluxe in the pack. I also used all the entries that were made by the guys here in the FB9G CFW thread.

    • Like 2
  3. I use notepad. It works. I'm sure ++ is better for sure, though. 

    The swapping of the core is something that gets asked about a lot. Here is the info that was told to me:

     

    "The flashback is running an old Stella core. The menu launcher is hard-coded to use that core, so you'd either have to hack the menu app or swap a different core for the one it thinks it's launching."

     

    "The Mali400 GPU driver is misconfigured at best. OpenGL ES is basically broken and the correct version of the driver binary isn't present. It is launching everything in Windows X (slow). In theory if I can compile a replacement kernel and load the correct driver it could conceivably run Stella 6."

    So, it looks like it is possible, after all.

    • Like 2
  4. 1 hour ago, Wizzard said:

    Thank you very much for this updatre. Just one question, where do I have to put the boxarts or title screens? Do I also need that ini file? Thanks!

     

    edit: I am not sure if I made it right, but I just copied those 3 files to USB and turned on FB X deluxe. Then pressed joystick left and it seems like it installed some update, after restart it asked me to install it again.

     

    It created 2 folders on SD: "emulator" with empty files and "rom", which contains empty and non-empty files. What did I do wrong?

    Step 1: put "atari_update.img" file on your device, insert device and power on. push left to update when prompted. let it update. after it is finished it will ask again. hit right for no. go to main menu. power off system. remove device. delete update file from device.

     

    Step 2: put the "mount_sd" file on the device, insert and power on system. it should take a while. IF YOU HAVE A USB 2.0 device it will take a very long time. let is sit on the main menu and go do something else for 10 mins. sometimes ive found launching a game and playing for a few minutes triggers the control files and works. USB 3.0 seems to not have these issues from my testing. Anyways this generates the "rom" folder. all the files should be inside and not corrupt. you should be able to see all the box art images and roms and whatnot. the "all-games.ini" file is inside here also. leave the "mount_sd" file on your device permanently.

     

    Step 3: put the "startup.sh" file on your device, power system on and let it sit. again, launch a game and play a few minutes. this will dump the "emulator" folder. Inside the "emulator" folder is other folders where you will find the music the emulator core, the UI elements etc. leave the "startup.sh" file on your device permanently. Not all of the UI elements are editable. some that you will find and edit will have no in game effect because they are hardcoded. the default bezel_00 (no bezel) is an example. 

     

    Step 4: create a folder named "game" on the root of your device. to load .bin and .a26 roms (without artwork) the old way. I'll reiterate, .bin or .a26 extensions work. no spaces in roms name, it cant be super long but I never tried to figure out the max. it also cant have crazy special characters, but again, dashes and underscores work, im not sure exactly what doesn't. but you will know because you will be navigating through the pages of your game folder in the Ext. USB Drive section and it will black screen freeze your system when the unproperly named game appears. And you will be forced to reset your console.

     

    Alternate: Update system and delete update img file from device. Put the Mount_SD and StartUp files on your device. download my theme and it is a slightly edited "emulator" folder and put that on your device. download my Atari pack and it is a "rom" folder with 900 games and art. put that on your device, and you wont have to do the partition dumping if you can live with using my edits as a base. Or just use the rom folder by itself and forget the theme altogether. you don't have to have an emulator folder on your USB device at all. or vice versa, the rom folder doesn't have to be used to run the emulator folder.

    I will add, using a 2.0 device will work, but it is slow. not just for the dumping of files, but navigating the main menu at times and launching games. I mean, it works, and once you load a game, its fine. but for what its worth, use a 3.0 device or sd card with usb adapter. its a lot smoother experience overall. use a 2.0 drive if that's all you got and don't have access to a 3.0. I have a 32GB SanDisk Ultra 3.0 Flash Drive and it works great. my 32GB PNY 2.0 drive gave me similar problems as described here.

    Something else to note. All the edits are on the USB device, not on the system itself. removing the device will boot the system like stock/normal. Which means you could have multiple USB devices with multiple custom setups if you wanted to. Or multiple game, emu, and rom folders all on the same USB device, and you could just rename them all something different. but the system will only recognize the folders with the proper names, "rom" "game" "emulator" so just swap the names around to run different set ups. for example, dump the emulator folder and rename that folder to "stock_emu" or whatever really, and download my them and use that. if you want to go back rename my "emulator" folder to "Sans_Boom" and change the "stock_emu" folders name back to "emulator". Same for the other folders. For instance you could download all kinds of different romsets, like no-into, good set, pal only, 1G1R, favorites, etc, and have all those romsets in folders on your USB Device, and just change the one you want to runs folder name to "game". get tired of that set, change the name back and pick a new set and name it "game". With these small files and todays large drives, you could really have a massive digital Atari collection. I actually have like 500 Atari manuals in PDF format in a folder on my flash drive also. the only downside is you can't select any of this on the console itself. you will have to plug your Flash drive into a pc or laptop to swap folders or read manuals. but at least its possible.

     

     

     

    • Like 1
    • Thanks 2
  5. Here it is, the A.T.A.R.I. (AtariAge Text, Art and Rom Injector) v0.X

    900+ games this time. It will work with the Atari Flashback 9HD, 9Gold, X and XDeluxe as long as you are running the Custom Firmware and the mount and startup files are on the root of your SD Card/USB Device.. This works the same as the "emulator" folder. This is the "rom" folder. Swap it out with the one you dumped to the root of your USB Device.

    you should have on the root of your SD Card/USB Device:

    the "mount.sd" file.

    the "startup.sh" file.

    a folder named "game" with Atari 2600 roms in either .bin or .a26 format and no spaces in the rom name, and not an overly long name. (this is just for side loading games without art the old way.)

    a folder named "rom". dump it with the "mount.sd" file when you power on the system. (or just use the one I just posted here)

    a folder named "emulator". dump it with the "startup.sh" file when you power on system. (or just use the Sans Boom Theme/"emulator" folder up above.

     

    If you need help, just ask. If you have changes in mind to make to the rom pack for future updates, just let me know.

     

    About the music, I always turn the background music off, so I don't even think to edit it. but yes, totally swappable. The stella core is in there too, I imagine someone who knows what they are doing could edit or swap that. 

     

    To edit the main game list: in the rom folder is a file named "all-games.ini". you have to edit that file with notepad. If you have Tron.a26 rom you will need a thumbnail in PNG format, 211x290 pixels, named Tron.a26.png and a second thumbnail 122x168 named Tron.a26.s.png. The rom the thumbnails and even the all-games ini file all are in the "rom" folder together. Check the other games entries in the all-games.ini file to get an idea how to add your new game. but it looks like this:
     

    [Crossbow]
    File=/rom/Crossbow.a26
    Platform=Atari
    Sort=Crossbow
    Year=1987
    Genre=atari
    Description=
    Note= \
    Player Mode: Multi-player game (1-2) \
     \
    1. SELECT button. \
    Press the SELECT button to choose between games. \
     \
    2. Use joystick controllers. \
    Use the P1 or left slot joystick for one player games, and the P2 or right slot joystick for the second player in two player games. \
     \
    3. Difficulty switches. \
    Toggle Switches for Difficulty. \
     \
    4. Instructions. \
    Press START button to begin play.

     

    Alright guys, Have Fun!

    ATARIvX.rar

    • Like 5
    • Thanks 1
  6. Here is a theme, if you will. It's a few small edits of the "emulator" folder. The giant word "BOOM!" has been removed from the Menu Backgrounds. The Atari Flashback Gold bezels were swapped in. The blue and yellow SD Card icons for side loaded games were switched to generic Atari 2600 box art (since there is no SD Card slot). The ActiVision game launch/splash screen text was changed to an ActiVision logo from the Atari 2600 time period. Simply swap out the "emulator" folder you dumped to the root of your USB Device with the "startup.sh" script with this new "emulator" folder. Or you could go into the "emulator/res/images" folder and just swap out the individual images that you want to change ala carte.

    ProTip: If you are having trouble getting the "startup.sh" control file script to trigger (slow 2.0 USB device), try launching a game. If you still cannot get it to dump, simply use this theme ("emulator" folder) instead.

    Looking forward. The rom packs that were made for the AFB9HD and AFB9Gold will also work on the AFBX. The all-games.ini file, the thumbnail sizes, naming conventions and file extensions all stayed exactly the same. I'll have a new pack up sometime very soon. And, it will be backwards compatible with the Flashback 9s.

    I want to take a second to sincerely thank Brad. Thank you so much, bud. I really enjoy modding the Atari Flashbacks. It's a super fun hobby that I couldn't enjoy without your efforts. You're awesome.

     

     

    Sans_Boom_Theme.rar

    • Like 1
    • Thanks 2
  7. You put the artwork and the ini file in the rom folder that you generate when you update with the most current CFW AND run the mount and startup files. You will still need to source the roms. I didn't include them. The roms will need to have specific names, just as they appear in the ini file. The officlal ini file is needed for all the game descriptions text and controls.

    • Like 1
  8. if the official update file isn't renamed to "atari_update.img" the system won't see it, or prompt for joystick left, when you turn the console on. If it IS named properly, and it doesn't prompt for joystick left, I would guess either broken/incompatible SD Card or broken SD Card reader/console.

    Not sure how you can brick these from firmware/custom firmware, as the system will always recognize properly named updates and you can flash it back. That's the beauty of these atgames systems. I'm not super knowledgeable, but I'm pretty sure there is a partition that doesn't get flashed over, ever. And that is where the program is at that looks for properly named updates when the console gets powered on. so if you "brick" it, you just re-flash an update to fix it.

    The sound issue (games not playing with sound) is a known hardware issue. I've experienced it seldom. Launching a game and exiting back to main menu brings the sound back for me. I have heard others will unplug the HDMI and plug it back in while system is powered on and that fixes it, but i've never tried that myself.

    I can tell you I have flashed dozens of systems multiple times, all the official and custom firmware works. I have "bricked" a system once. (powering on would load the atgames logo and make the chirp on the legends flashback 2018, but never go to the built in games list.) But I just re-flashed it and everything was fine. I can also tell you that the custom firmware to add games and artwork to the main UI is what you need to be using. You can flash the Atari FB9 Gold over the standard unit and make it a gold.

     

     https://atariage.com/forums/topic/296676-flashback-9-gold-cfw-to-load-roms-and-boxart-from-sd/#comments

    • Like 1
  9. So, I pressed the issue, and there is no firmware.bin file available.

     

     

    Hi Thomas, 
    Thank you for the follow up. 
    Please note that there was never update released for the Atari Flashback Portable Player on our website so we suspect that probably the website it was downloaded from might have damaged the unit. Atari Portable should play the games that are uploaded on the SD card (with correct format) without any firmware update. 
    We would like to offer you a replacement, however, we don't have this unit available in stock. Would you be interested to receive a version without wood-graving as a replacement. At the meantime, we would like to retrieve your unit back for checking. 
    Please let us know. 
     
    Best regards, 
    AtGames Customer Support 

     

  10. My camera sucks.

    86999754_2753215324793384_1171291543588306944_n.jpg

    I opened up the new portable, The board says "AP3280B_MK1F_V1.0_20190705" and "20190716"

    One chip says:
    ESMT

    M12L128168A-            6T

    AZN1P83TX             1832

     

    The other says:
    MXIC L183341

    MX29LV64DEBTI-70G

    SD007900A4


    So, I'm guessing we can't get neo boot loader working on this as it is not a RedKid chip but instead a Monkey King (rockchip)???

  11. So, I emailed AtGames and tried to get a copy of a firmware.bin file, but I don't think they even have anything to send me. At this point I probably won't pursue it any further.

     

    "Hi Thomas, 
    After further checking with our development team, the system should recover once the SD card is removed and power cycle done. Unfortunately, there is no option to perform the factory reset on this product and turning it on and off should set the unit back to original settings. 
    Is it possible you find the binary file location it was downloaded from so we can investigate at our side and find out what might have caused this unusual issue. 
     
    Thank you for checking. 
     
    Best regards,"

     

     

  12. yes, and I think the SD Card limit is 4GB.

    All the folder structure has to be set up to implement the artwork and corresponding XXX.bin database files. If you add more roms to say folder "ROMS D-E", you wont be able to just add artwork, you'll have to delete the ROMS D-E.bin database file and start over. Which is why all the artwork and assembly editor programs were included if someone wanted to do that. 

  13. Almost forgot. This one can run new firmware and update with a "firmware.bin" file, like Kevin Mos3 said. So, it DOES have that going for it. Although, I doubt they will ever release firmware updates, as it doesn't even appear on the AtGames flashback update portal zone whatever page, with the other new units.

    Maybe I should email customer service and tell them none of my games are showing up in my list after I updated it with a flashback X image and see if they send me a "firmware.bin" file???

×
×
  • Create New...