-
Notifications
You must be signed in to change notification settings - Fork 4
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
Xenium Ice Fails #6
Comments
Also the case for me. I ran the tool when I was on 2.2.1 (didn't read it needed 2.3.1)... it seen the chip, but failed for unknown bios. Updated to 2.3.1, and now "Xenium not detected" |
using Xenium Tools (first release)... it detects the chip... but looks like the Man ID = 01, but Device ID = o4 (instead of c4)... is there a debug mode where I can see what the Updater is seeing? Thank you |
I have this same issue. |
Also having same issue. updated from 2.2.1 to 2.3.1 and not detected by the firmware updater or in xenium tools. Detected in older version of xenium-tools as id 01 c4. Boots fine, just can't update it or manage it with xenium tools any longer, or update to any of the patched updates. |
Due to frying my CPLD on my Ice... I replaced with a OpenXenium CPLD and everything worked after. Appears may be something in the original CPLD firmware that doesn't respond well with update code? |
I downgraded mine to 2.2.1 with the older xenium tools and a 2mb 2.2.1 flash image I dumped from mine before doing any of this. I then used the newer xenium-tools to write 2.3.5 to it using a dump I had from another OpenXenium that was upgraded. That worked but it's still not detected by the firmware update tool or xenium tools. Not sure what is different in the cpld on these, but it's not responding with the right info for the tools. |
Sorry for the late response, but I just noticed this git issue while briefly looking back at OX / XOS this week. I'm pretty sure the original Xenium CPLD normally toggles when the flash is writable, but I have never owned an original chip to experiment with. Specifically, XeniumOS only enables writing to the flash when updating the Xenium config, flashing a bios, or executing its self-destruct routines (lol). In fact, when launching a bios XOS makes doubly-sure the chip has disabled write access to the flash: I mentioned this to @Ryzee119 over a year ago when I was researching XeniumOS. The magic X bit of 'unknown function' as referenced in the VHDL very likely enables/disables writing to the flash: Back then, there was no reason a launched bios or any tool should have had any reason to modify the Xenium flash. Only the chip/XOS knew the layout and config of their flash and virtual banks - there was no reason to allow anything else to modify it since it's supposed to be fully managed by XOS. |
I have a original Xenium Ice that isn't detected by the upgrade xbe
I have tried re upgrading the Xenium firmware from 2.3.1 to 2.3.1 and still fails
also tried flipping the switch on the mod chip with same effect
thnx Mary
The text was updated successfully, but these errors were encountered: