Jump to content
OGXbox.com

Bowlsnapper

Fanatical Members
  • Posts

    4,834
  • Joined

  • Last visited

  • Days Won

    147

Everything posted by Bowlsnapper

  1. Which Amazon Rework Station?
  2. I also wonder about this. Maybe @Jay Yardley may have some insight?
  3. Forgive me for being stupid. Now I understand why you're having an issue. You can't browse an Xbox DVD with a regular PC OS. You need to either use a 3rd party utility like XDVDMulleter or Extract-XISO. This is because the ISO is in the proprietary XDVDFS filesystem, instead of a regular data disc, for ensured compatibility. I would suggest using the latest version (1.4.2), since there were some bug fixes and improvements made, as well as more documentation on the disc itself. Please consider coming into the Discord Server, so that I can help a bit more directly, however, I will still answer any questions you have here on the forum. BSX Mods: https://discord.gg/kFRKK77dEk
  4. d5f10897577366e0cf982b2ec4b7e7f11d06f2d712baed5ac55925e6627da0d1 Is what it should be. If it isn't, I just need to upload it again. My apologies, if that's the case. @Cyberxine
  5. Try without the DVD drive connected.
  6. It is 16TB per volume. You can theoretically have a max of 32TB.
  7. Come on, Bro. This means that you can fit 32TB in an Xbox. Who doesn't want to put 32TB of HDD space in an Original Xbox? Seriously. Doing things like this is pushing the boundaries of what we thought this thing was capable of even a year ago. It's fun. It's cool. Why not do it? If no other reason, I assume it makes it easy to transfer data from one to another. That's useful in itself.
  8. What I know is that PrometheOS contains ModXO so that it all works together with one flash. The only thing is that it still has ModXO 1.0.2 (I believe) in Prom 1.4.0 so he was overwriting the 1.0.5 ModXO that he was flashing first. When flashing PrometheOS, if you want to have the most updated ModXO firmware, you need to flash Prom first, and then ModXO. Flashing modxo after will leave Prom intact since it isn't overwriting it, but it WILL overwrite the older ModXO firmware bundled in with Prom. The only way to address this is to update the PrometheOS flash files with every release of the ModXO firmware, even if PrometheOS still remains at the same version. This does not explain why he was not able to boot since it theoretically should have just worked, which is the point of bundling it in the first place. But I know the Dev boards can be a bit janky at times so I suggested flashing Prom and then the newest ModXO on top of that and it luckily got him going.
  9. I can look at the shipping cost and weigh one tonight. PM me your address and email so I can fill out the customs form and get a solid price for you.
  10. The YD is a custom chinese version of the Pico dev board that has USB-C instead of Micro-B and a neopixel on it, basically. @nogarth, what is the issue exactly? I'm not understanding your post.
  11. Something that could conceivably be addressed in firmware?
  12. What do you believe might be happening?
  13. Do you even WANT the wiring? You could just use a pin header and call it a day. Mount the chip to the mobo. Using wires is totally antiquated at this point.
  14. Well this aged interestingly, didn't it? If you are able to see this notification, you got close. I'm interested by how you figured out that the GPIO would need to communicate with the LPC at a certain frequency.
  15. I've been noticing this with my 1.6 test console too, so you're not alone. It is intermittent. Sometimes it does it, and sometimes it doesn't. But ALWAYS with one reboot (FRAG style) before booting successfully. I've been shitting bricks because I thought it was an issue with my chip design, but apparently I am not alone. I'll try to look into it for us. Have you been able to test with any other 1.6 consoles? What form is your chip in, the pico development board? Is anybody else experiencing this with their 1.6 consoles? Edit: Is your ModXO always powered in your 1.6? If it isn't, make sure it is powered constantly (By USB if you must) and see if this problem persists. Basically, make sure the board is already powered. 1.6s are known for their 5V standby power, so if your ModXO is not powered by this somehow with your wiring, have it always powered and see if there is a change.
  16. Before I fully read how you were using it ("Rainbow Puke") I was assuming you were talking about the LPC wiring.
  17. I didn't even notice the slick packaging at first. Nice touch!
  18. Am I understanding correctly that this is a version of the XDK that installs on top of VS2019 and that can debug the Xbox natively through XBDM, finally getting rid of the need for VS2003 and an XP machine?
  19. I have plans for that. Both chips will get the eyes, but with an extra added creative touch...
  20. The BSX Nova (V9) and Mini (V3) are now finished. The The Nova now has 100 percent of the proposed ModXO pinout. I have placed the SPI display CSN lines on a separate JST (as well as on their own solder pads) on the Nova, so that anybody using I2C can just use the Display port without having either extra wires or a custom JST connector. The Mini has the CSN lines on solder pads only, since there was limited space for another connector. I have put debug solder pads on both chips, so that the pico debug kit can be used with them and ModXO can be debugged properly. I have tried very hard to have the highest quality I can achieve and to have the design look very sleek and professional. I would like the ModXO firmware to have a solid hardware base for its firmware to thrive in and showcase what it's capable of. Both chips come with the front panel PCB for status indication and flashing/recovery. I have 5 Minis and 5 Novas. The Mini is $30 and the Nova is $45. I will build more this week. What you see pictured has been placed and reflowed by hand and it was a gigantic pain in the ass. Lol. I am hesitant to invest in large amounts until I know that the demand is there. If people like what they see, and they sell, then I will invest in more and hopefully give people a quality ModXO chip for future features to be expressed by. I am creating pinouts this week, as well as an install guide. All chips can be requested with a pin header, D0 Socket wire, 1.6 LPC rebuild PCB, and Any JSTs you need for your peripherals, such as LCDs.
  21. I've been thinking a bit and I wanted to express some thoughts. I believe I have created a nice chip and created a nice starting point for the project. I have tried very hard to create something that is quality and that people would be proud of saying that they have in their systems. However, this project would not be possible without the efforts of Shalx and Team Resurgent. I may have been able to read some datasheets and connect some blue lines in KiCAD (Albeit for the first time in my life), but I think it would be a bit ridiculous for me to act like this has been all me. I was developing a hardware embodiment of the ModXO firmware, and trying to create the best physical representation of what this firmware is capable of and what it has the potential to. Code is a powerful tool and I am confident that Team Resurgent has the skill and drive to pull it off. I should thank Shalx specifically for hanging with me and answering my questions when he has the time to do it. So here's hoping that project BSX succeeds. It can only do so if ModXO enables it to. Thank you to the community and everybody who contributes to both Team Resurgent and ModXO, both directly and indirectly. https://buymeacoffee.com/shalx?l=de?t=true https://ko-fi.com/teamresurgent
  22. The latest run. Both chips have undergone some final design changes and are going into production. Stay tuned. @CoolRunnings92C Thanks, buddy. As soon as I'm able, these things are going out. Not long now... although you should have one in your mailbox pretty soon here.

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.