Jump to content
OGXbox.com

Ryzee119

Members
  • Posts

    165
  • Joined

  • Last visited

  • Days Won

    33

Everything posted by Ryzee119

  1. Before you pull it all apart you should ask on MM discord. They can probably help out here. Could just be a bug in the software
  2. Amazing work! Regarding PID/VID for PS3/4 controllers generally it is better to check against the interface class/subclass/protocol. Atleast on Xbox these are always consistent and so you don't need to rely on hardcoded PID/VIDs etc by I'm not sure how the PS controllers are tbh
  3. I don't think there is inherently anything wrong with SEM product if used with the claimed intentions and I didn't agree with the DCMA of the wiki page of course as it rightly didn't share links to firmware and expected users to purchase a xboxhd from makemhz. Although not clear how the user was meant to get the firmware as it couldn't be like dumped from the xboxhd board you purchased which is normally how these things go SEM did seem like more of a targetted jab at MakeMhz than a genuine attempt to increase availability of xboxhd boards without stellar but that's besides the point and an opinion only. I really hope Nem doesn't just release his hdmi board with the microcontroller effectively moved to the SEM board as some kind of loop hole and intend people to use SEM and "the community" will write the firmware knowing full well it will be 100% binary compatible with MakeMhz firmware by unbelievable odds. But I look forward to his technical overview of his design and will reserve further judgement. If the community is expected to write firmware id expect an overview eventually to be exceptionally thorough so we stand a chance of even beginning to help on the firmware side. There is loads of changes from my design based on previous images shared so genuinely curious why so many changes. I don't even know what this QSB thing is for tbh. I was pretty proud of my design and didn't expect it to need many (if any) major changes. If based on my design as claimed there is loads of debug logs Nem could provide here which would probably actually tell him or me what's going on if he is having troubles. There's is also an extremely good chance I could just tell him what's wrong with source code and/or a schematic. His source must be quite different from mine as it's been ported to a different IC. I would help at a much more reasonable price of $200 per hour. (But actually I'd prob help if given genuine questions about my design for free)
  4. Make sure in your LCD.xml you change LCD.timeWide21, LCD.timeWide22 with something else as this is bugged out in xbmc with xenium chips
  5. Only minor changes. It does all the same things as the legacy one. - Less components for simplified BOM - Larger compents for easier soldering (0805s instead of 0402s etc) - Crystal has been replaced with a new style package. This caused alot of issues in the past. - Larger power traces and grounds. Should help with wired controllers that have large inrush currents.
  6. Good thing about git is that all history is saved This is the last commit before the pcb revision update. https://github.com/Ryzee119/ogx360/tree/4ca560ee891af992e6eee105a37c6758a537e22f
  7. I have since worked out that the "-A' thing is part of the 'quick boot' feature. It indicates what button to mash during bootup to boot that bios. You can change it to -B or -X etc. This is only used when Quick boot is enabled but unforuntaely it shows the '-LETTER' thing either way which is annoying The instant boot feature is more useful imo. Set a bios as your 'default', and enable instant boot. From that point on, the power button will boot that BIOS, and the eject will boot XeniumOS
  8. Input to the encoder is YCrCb444. Its a DDR pixel bus. You sure the maxV is fast enough ? At 720p or 1080i the pixel clock is 70ish Mhz. The pixel is ~140Mhz. (About 7ns period) At 480p/i its about 24mhz so not too bad. Im working on a digital hdmi conversion slowly but its hit a few snags
  9. @Laminatesnow That is a fork of https://github.com/Ryzee119/spi2par2019 which changes the hd44780 LCD interface to a I2C OLED display.
  10. If anyone has a Hyperkin Duke controller, I think ive got it working in the latest firmware update. If anyone is bored and wants to try it out, the firmware is here: https://github.com/Ryzee119/ogx360/releases/tag/1.4 You will likely only need to update the 'master' module on your ogx360
  11. @Bob_the_vampire you are welcome. Glad to hear it
  12. @Bob_the_vampire yep that flash dump has some issues. Even the protected sector is messed up. So its possible that the CPLD banking is broken or hopefully its just corrupt flash. Upload this to your xbox in the xenium-tools xbe directory and rename it to flash.bin, then in Xenium tools use the 'Write raw flash.bin to Xenium Flash' option. "START+B" If that doesnt work, it doesnt sound promising. Send me another dump of it after flashing it as you did previously. flashGoldClean2.3.1.zip
  13. 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
  14. @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
  15. @Nextria welcome to the constant struggles of programming CPLDs
  16. 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
  17. 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.
  18. 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?
  19. 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.
  20. 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.
  21. 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.
  22. 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.
  23. 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)
  24. 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)
  25. 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

Board Life Status


Board startup date: April 23, 2017 12:45:48
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.