Mr Robot Posted September 21, 2017 Share Posted September 21, 2017 I'm trying to upgrade the firmware of an Ultimate 1MB card that came installed in an 800XL I just bought to the latest one by FlashJazzCat. I was following along with the video on pigwa, enabled spartados, rebooted into uflash, updated the bios, updated the spartados and rebooted again. Now when I reboot I just get this... I think this U1MB might be so old it still has v1 of the cpld code on it, the guy I bought it from had no idea. Have I bricked it? Can it be recovered? Help! Quote Link to comment Share on other sites More sharing options...
+StaxX28 Posted September 21, 2017 Share Posted September 21, 2017 (edited) Same thing happened to me when I tried to flash FJC bios U1Mb V1... You need to reprogram the original Candle ROM on the PLCC chip with an EPROM burner. Attached file works on U1Mb v1 U1MBv2.rom Edited September 21, 2017 by StaxX28 1 Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted September 21, 2017 Share Posted September 21, 2017 (edited) If you already have an EPROM burner, great. If not, I recommend the TL866CS: http://autoelectric.cn/EN/TL866_main.html Buy the CS version, not the A version because it's cheaper. Upgrade your CS to an A using the tool I posted here: http://atariage.com/forums/topic/246355-minipro-tl866-upgrade-instructions/?view=findpost&p=3403336&hl=%2Btl866cs Edit: I posted using my phone, so of course there was an error. This should be the correct link to the first post in the upgrade thread: http://atariage.com/forums/topic/246355-minipro-tl866-upgrade-instructions/?do=findComment&comment=3383742 Edited September 21, 2017 by Kyle22 2 Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted September 21, 2017 Share Posted September 21, 2017 Or purchase a Xilinx programming cable and update the CPLD. Search the forum for more info. This is why there's a warning on the BIOS download page regarding the CPLD revision. If in doubt, enable "SIDE hardware" and poke $D1FF to see if the mathpack overlay appears. 2 Quote Link to comment Share on other sites More sharing options...
Level42 Posted September 21, 2017 Share Posted September 21, 2017 Playing devil's advocate: isn't there a way the flash software could scan for the right CPLD and refuse flashing if it's the wrong one ? Quote Link to comment Share on other sites More sharing options...
+kheller2 Posted September 22, 2017 Share Posted September 22, 2017 Playing devil's advocate: isn't there a way to notify someone before downloading the firmware that they should be careful and use the right process? I have yet to upgrade my v1 but I'm very well aware of the steps to go through because of other's suffering. Quote Link to comment Share on other sites More sharing options...
Jinks Posted September 22, 2017 Share Posted September 22, 2017 I will never upgrade mine. It works thats all I could ever want. Quote Link to comment Share on other sites More sharing options...
Mr Robot Posted September 22, 2017 Author Share Posted September 22, 2017 (edited) The only person I have to blame is myself for thinking "I'll give it a shot, what could go wrong" when I didn't know what version I had. I found a page here with lots of info about upgrading the cpld after screwing it all up and I've ordered a Xilinx programmer. For future reference, (This is the bit I couldn't find anywhere) This is CPLD JED v1 This is CPLD JED v2 Edited September 22, 2017 by ChoccyHobNob 5 Quote Link to comment Share on other sites More sharing options...
Level42 Posted September 22, 2017 Share Posted September 22, 2017 (edited) I will never upgrade mine. It works thats all I could ever want. OMG seriously.......you miss SO much.....IMHO Jon's upgraded firmware pulls out the full potential out of the U1MB.....but this is also why there should be some check done by the flash tool .....people shouldn't be afraid to try it....but I have no clue if it's possible to let the flasher tool check that.... Edited September 22, 2017 by Level42 3 Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted September 22, 2017 Share Posted September 22, 2017 It's actually easier for the human being in front of the keyboard to check, but I should have realised that never works. 3 Quote Link to comment Share on other sites More sharing options...
Level42 Posted September 22, 2017 Share Posted September 22, 2017 I would not say never. But when I did some programming I always built in the "user error" options....it's like designing a fuse into an electronic circuit.... Quote Link to comment Share on other sites More sharing options...
Marius Posted September 22, 2017 Share Posted September 22, 2017 Or purchase a Xilinx programming cable and update the CPLD. Search the forum for more info. This is why there's a warning on the BIOS download page regarding the CPLD revision. If in doubt, enable "SIDE hardware" and poke $D1FF to see if the mathpack overlay appears. Could you explain these steps a bit more? This is interesting. I would like to know how to do these steps, so I can check which U1MB's are v1 (I am sure I have at least 3 of these) Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted September 22, 2017 Share Posted September 22, 2017 (edited) I would not say never. But when I did some programming I always built in the "user error" options....it's like designing a fuse into an electronic circuit.... You need not explain to me the importance of "user error" options; this is why the flashing tool signature checks the firmware components and will not allow the user to flash the wrong file to the wrong slot. Regarding the CPLD question specifically, however, circumventing user... oversight, shall we say... is not so easy. Firstly the extra IO RAM opened up by the v2 JED is completely inaccessible outside of the BIOS setup utility unless the PBI BIOS is enabled. With the PBI BIOS enabled, we can at least probe $D1FF (much the same as the manual method I suggest for checking the existence of the math pack overlay), although having the PBI BIOS enabled is in no way a pre-requisite for flashing the ROM. The best I can offer here is a warning message when updating the BIOS from the legacy version to the alt version, along the lines of "Please go and figure out if you have the V2 JED first". Could you explain these steps a bit more? This is interesting. I would like to know how to do these steps, so I can check which U1MB's are v1 (I am sure I have at least 3 of these) Remove any external PBI devices, enable "SIDE hardware" and "SpartaDOS X" using the original BIOS. Ensure the SIDE PBI ID is set to "1". Boot into SDX. Type: SET PROMPT= This clears the prompt and ensures no SIO activity while we're typing commands. Type: PEEK $D800 Note the result. Type: POKE $D1FF,1 PEEK $D800 Note the result (hopefully "U"). If the peeked value changed, you have the V2 JED (since we know the math pack overlay just appeared). We can go further and look for RAM at $D1xx and $D5xx too, but there should be no need. Alternatively, one can just plug in SIDE, enable SIDE hardware, and see if the HDD works. But the above instructions are intended for non-SIDE owners. Note also that if the "SIDE hardware" option is present on a board with a V1 JED, it means the board has the wrong BIOS anyway. The difference is that alt BIOS requires the V2 JED to boot. Generally, the existence of the "SIDE Hardware" option on the legacy BIOS menu is an indication that you're good to go. Edited September 22, 2017 by flashjazzcat 4 Quote Link to comment Share on other sites More sharing options...
Mr Robot Posted September 22, 2017 Author Share Posted September 22, 2017 I was never not going to do this upgrade so the bricking was inevitable. If I'd been lucky and the guy I bought from had got a newer U1MB it would have been no problem. The only downside is that I currently cant use the 800xl until the programmer arrives. It'll give me time to fit a stereo pokey and give it a good clean and try to get the cigarette stench out of it. 2 Quote Link to comment Share on other sites More sharing options...
Mr Robot Posted October 26, 2017 Author Share Posted October 26, 2017 (edited) OK, so I followed the instructions here, the programmer took forever to get here from China, it's a slightly different model than the one tuf mentioned in the instructions. Here's mine. I made my cable from the cable mentioned in tuf's step 3 and used a chunk of GPIO socket I had laying around for Raspberry Pi projects. Here it is. I have since covered the connector in hot glue to protect all the connections. Everything else was exactly as tuf wrote and it all went according to plan. I noticed here that there is a v3 of the CPLD JED file, is that something I should be putting on my U1Meg now it's working and updated? Edited October 26, 2017 by ChoccyHobNob 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.