Ryzee119
-
Posts
164 -
Joined
-
Last visited
-
Days Won
33
Content Type
Profiles
Forums
Calendar
Store
Everything posted by Ryzee119
-
Download xenium-tools xbe from the openxenium repo. https://github.com/Ryzee119/OpenXenium/releases Boot up with your aladdin and open this xbe. Once the xbe is open, hot swap to your gold. It should be able to detect a xenium is installed and you should be able to manually cycle the RGB. You can also dump the flash chip from this program. If any of that fails your CPLD (or flash chip) is likely damaged in someway. If that all works but still doesnt boot, its possible that the flash memory is corrupt in some way. I have a clean goldOS dump in that case
-
@Nextria thats awesome. Glad to hear! I powered mine using a bench supply, but if you can pull a 3.3v supply from the programmer that would be handy. Good luck with your builds! Share some photos too
-
@Nextria welcome to the constant struggles of programming CPLDs
-
Updated Openxenium CPLD code coming in the next few days. Found a really obsure booting issue that I am working to fix it. I dont think any one has built any yet, but if you are; just wait a couple days before programming them and make sure you have the latest files from github
-
What its meant to look like. Actually if its a 1.6 i believe it has an issue with xcalibur so doesnt display properly. It was repeatable on my 1.6 but works with focus/conex.
-
Recovery cromwell has a unusual resolution so it may have been the video adaptor/monitor. Good thing you waited for it to finish. Orange LED is normal so looks like it was doing its thing but just wasnt being displayed. Worst case if it bricked, you could recover it with xenium-tools. Shame about 2.3.0. Did you try removing and reflashing that bios?
-
The random '-A' must be a bug i have concluded. It always appears on the first bank you flash. It appears on openxeniums and real xeniums. I dont think v2.3.0 does it.
-
Correct. Flash offset 0x1C0000 to 0x1DFFFF can only be obtained from a genuine xenium. This is the recovery sector that contains a small cromwell loader to initiate the xeniumOS update process. (Switching that switch on the Xenium modchip) This is technically optional and a genuine xenium or a openxenium will work if this area is not programmed but you lose the respective feature.
-
The first 1MB of the dump is your custom bioses. Just blank (0xFF) this area. This still wont remove them from the xeniumOS bios selection menu. (Prob just frag if you try boot them) 1FC000 to 1FFFFF region right at the end is the sector that holds non-volatile settings for XeniumOS. EEPROM backup etc. Id have to check as i cant remember exactly but i would expect the bios names to be here. What i did for my clean dumps is factory reset my Xenium before dumping. Then clear the first 1mb with a hex editor.
-
Not exactly. To get a working Xenium you need two things: XeniumOS (Located on the flash chip, traditionally not protected in anyway) VHDL code (Located on the CPLD, traditionally read protected to prevent clones) XeniumOS is easy to get. Either from a Flash dump of a genuine Xenium OR the Xodus released XeniumOS files. This is NOT on my repo. It is not my software to share so I dont share it on my repo (which focuses on my own work) The VHDL code is the tricky bit and is what my repo provides.
-
Another fun fact If you get a dump of XeniumGold OS you write the Xenium Gold firmware to your OpenXeniums. This was never released by Xodus separately (i believe)
-
You don't need a full dump but it has the recovery partition so the recovery jumper will work. Kinda useless anyway but more of an authentic experience. You can also parse the XeniumOS update files that Xodus released. (2.3.1 is the version i wrote the parser for)
-
Very generous but I cant take all the glory . If someone wants to have a crack at it, I am happy to provide help. It's a tedious and complex process but very rewarding
-
sorry check again
-
https://www.youtube.com/watch?v=P6YYViKby74
-
As Kekule mentioned the S29 flash chip pretty much identical to the am29 chip. Unbelievably close so its almost like they just changed the model number and up revved the datasheet. That was a good find! They have a specific flash sector configuration that XeniumOS takes advantage of so not any old flash chip will work. You can find am29lv160mt if you look hard enough but no benefit. In fact probably worse. (Aging chip)
-
Honestly i have never used a X3 but the modchip has alot of complexity in the hardware that i feel doeasnt add value. Separate eeprom, separate flash chip, external buttons etc. I can understand why they are there but xenium doesnt need any of that and it works fine. It just makes development more expensive for me on top of actually having to buy one in the first place.
-
Indeed, but I dont own one and dont particularly want to buy one especially now that I have unlimited Xeniums
-
Yes I would think so
-
Hi all, Over the past few months I have painstakely reverse engineered the Team Xodus Xenium modchip's CPLD and written a complete open source replacement. I call it OpenXenium. https://github.com/Ryzee119/OpenXenium It has full support for XeniumOS and its features. Repo will list them. The Xenium CPLD is normally read protected to prevent clones. This project did not attempt to break that protection, instead I determined the behavioral properties of the CPLD to write my own VHDL source code. Check the repo out! there is a few xenium related tools that may even help people with a genuine Xenium! Hopefully this will help with LPC related CPLD projects people may have in mind too. Enjoy! Ryan
- 103 replies
-
- 15
-
-
-
@samspin Dont worry it is all sorted.
-
I can confirm that this definitely does not use a raspberry pi
-
Awesome thanks. Ill have a look tonight!
-
Looks I could probably get it working. There is likely some special packets that get send to the Hyperkin controller to initialise it during the enumeration process as that seems to be pretty standard with third party Xbox one controllers. If anyone knows how to use Wireshark and can send a USB traffic log during enumeration that would be good! I cant commit to any timeframe at the moment as I am in the middle of some other projects
-
I have fixed the flickering issue mentioned by @John7272 and a software update has been pushed to github. The default Arduino PWM driver is terrible, so I manually overwrote the timer prescaler. It is a significantly better PWM output now :)
- 25 replies
-
- 2
-
-
- spi2par2019
- xenium
- (and 3 more)
Board Life Status
Board startup date: April 23, 2017 12:45:48