Jump to content
IGNORED

atari2600+ bricked after flashing the experimental firmware


omf

Recommended Posts

so, my atari2600+ was working earlier as best it did earlier today when i was testing my newly acquired games.  the quantity that was working wasnt great, so i decided to update to the latest experimental firmware and dumper (update-052024-1.1x-r3.img, dumper-052024-x.01.exe)

 

the updates appeared to work fine based on the original guide.  however after restarting, after the atari logo i saw a android robot logo with a box  and an arrow for a moment then the machine restarts. after allowing this to occur several times without change i attempted to reflash the latest official firmware.  the dumper flashed ok, but on attempting to flash the firmware image i get an error 'Test Device Fail'
image.png.e6b3264d081eaf332fde27434d2b8300.png

does anyone know what the process is to flash the firmware from fresh to bypass this error to reactivate my 2600+ ?

 

 

  • Sad 3
Link to comment
Share on other sites

4 hours ago, Dionoid said:

For the upgrade, did you use the USB cable which came with the 2600+?

yes i did indeed

i have kept all the parts together,  i had been waiting to use it on mass for more games support so its spent most of itslife in its box

 

Link to comment
Share on other sites

Posted (edited)

 


These are the factory installed firmware files. Not sure if this will help.

If this works I would redownload the Experimental firmware again maybe the file didn’t download correctly.

 

Just try installing the Image file again if that doesn’t work try installing the factory Image and dumper.

Then install the Experimental files again.

Edited by MrChickenz
Link to comment
Share on other sites

just tried it again.  it still fails on the on the device test (image above) so doesnt actually get to the flashing stage

 

i am using the same computer and cable (the origina cable) and the same usb port that has worked previously

 

 

the dumper updates fine, its the img file thats the issue.  seems like the RKDevTool cant see the chip properly any more

 

 

Link to comment
Share on other sites

Posted (edited)
10 minutes ago, omf said:

just tried it again.  it still fails on the on the device test (image above) so doesnt actually get to the flashing stage

 

i am using the same computer and cable (the origina cable) and the same usb port that has worked previously

 

 

the dumper updates fine, its the img file thats the issue.  seems like the RKDevTool cant see the chip properly any more

 

 

Was it the same image file? Try a different image file and see if that works. If you can flash one of the Atari 2600+ image files then you can try the Experimental image again. But I would download the Experimental image again to be sure it’s a working file.

Edited by MrChickenz
Link to comment
Share on other sites

1 hour ago, MrChickenz said:

Was it the same image file? Try a different image file and see if that works. If you can flash one of the Atari 2600+ image files then you can try the Experimental image again. But I would download the Experimental image again to be sure it’s a working file.

i have tried the original image attached above, and the two previous betas and the experemental image again,  all of them give the above error. 

 

I dont think it is the image,  the image flashing process does not get to the point where it is written to the chip. when it tests the chip the chip is failing to send back the correct information and it fails and does not cintinue to flashing of the image to the chip.  it seems the experimental image (corrupt or not) that was oringinally flashed overwrote something on the chip and now its not responding as expected by the flasher program.

  • Like 1
Link to comment
Share on other sites

39 minutes ago, omf said:

i have tried the original image attached above, and the two previous betas and the experemental image again,  all of them give the above error. 

 

I dont think it is the image,  the image flashing process does not get to the point where it is written to the chip. when it tests the chip the chip is failing to send back the correct information and it fails and does not cintinue to flashing of the image to the chip.  it seems the experimental image (corrupt or not) that was oringinally flashed overwrote something on the chip and now its not responding as expected by the flasher program.

Maybe someone from the Experimental Thread can be of assistance. Hopefully you get it working again.

Link to comment
Share on other sites

I'm pretty confident the problem isn't the flashed firmware. When you turn the console on with TV=COLOR and RESET held down, it actually does "press" the rockchip recovery button, which throws the board into bare metal recovery mode. That's the maskrom mode mentioned in your flash logs. At that point the device is running the non-updateable bootloader, and should be the exact same code as when you previously flashed the device.

 

This reddit thread seems to have some fixes for the same error, albeit with a Retron 5, which seem to target the driver. Maybe Windows went and updated the driver, or maybe it's spotty on your system for some reason. Before you go through the fixes in that thread, I'd first try with different cables, ports, and/or PCs, since that's easier and quicker to do.

  • Like 1
  • Thanks 2
Link to comment
Share on other sites

I think maybe the Atari 2600+ needs an easier update method? I know it's pretty straight forward, thou you actually need to have the driver installed and enabled/detected to completely install firmware/dumper updates...

Maybe too confusing for users who are not PC/tech savvy? 🤔

  • Like 1
Link to comment
Share on other sites

44 minutes ago, shane857 said:

I think maybe the Atari 2600+ needs an easier update method? I know it's pretty straight forward, thou you actually need to have the driver installed and enabled/detected to completely install firmware/dumper updates...

Maybe too confusing for users who are not PC/tech savvy? 🤔

an easier update would be good yes, but this isn't the issue here as i am a competent computer user

 

3 hours ago, RevEng said:

I'm pretty confident the problem isn't the flashed firmware. When you turn the console on with TV=COLOR and RESET held down, it actually does "press" the rockchip recovery button, which throws the board into bare metal recovery mode. That's the maskrom mode mentioned in your flash logs. At that point the device is running the non-updateable bootloader, and should be the exact same code as when you previously flashed the device.

 

This reddit thread seems to have some fixes for the same error, albeit with a Retron 5, which seem to target the driver. Maybe Windows went and updated the driver, or maybe it's spotty on your system for some reason. Before I go through the fixes in that thread, I'd first try with different cables, ports, and/or PCs, since that's easier and quicker to do.

thanks for the explanation, with this i realised that the Evercade uses the same chip family and might be causing me grief so after commandeering the wife's laptop, i managed to do the update process again (successfully to the latest experimental firmware and dumper)

 

thank you to all who have tried to help me, it is much appreciated...

  • Like 6
Link to comment
Share on other sites

5 minutes ago, omf said:

an easier update would be good yes, but this isn't the issue here as i am a competent computer user

 

thanks for the explanation, with this i realised that the Evercade uses the same chip family and might be causing me grief so after commandeering the wife's laptop, i managed to do the update process again (successfully to the latest experimental firmware and dumper)

 

thank you to all who have tried to help me, it is much appreciated...

I had the same issue.

Link to comment
Share on other sites

2 hours ago, omf said:

thanks for the explanation, with this i realised that the Evercade uses the same chip family and might be causing me grief so after commandeering the wife's laptop, i managed to do the update process again (successfully to the latest experimental firmware and dumper)

I've seen a few people mention problems having to do with this very thing, where they've flashed the firmware of a device, then when using the same computer the flashing of a different device fails. I've also seen it mentioned that deleting the drivers used for flashing the previous device prior to flashing the new one resolves the issue, but that can be a bit of pain, as you've got to know exactly which driver(s) you're purging, and that can be tricky when it's not actively being used.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...