(no title)
dinartem | 1 year ago
Note to self: you should have added random delays before and after making the POST code visible on the external pins.
dinartem | 1 year ago
Note to self: you should have added random delays before and after making the POST code visible on the external pins.
dhx|1 year ago
This is one of my go-to case study videos for the development effort required to architect a computer to resist attackers who have physical access.
[1] https://youtu.be/U7VwtOrwceo?t=536
unknown|1 year ago
[deleted]
spencerflem|1 year ago
jsheard|1 year ago
Obligatory: https://www.youtube.com/watch?v=U7VwtOrwceo
SteveNuts|1 year ago
liamwire|1 year ago
notavalleyman|1 year ago
nemothekid|1 year ago
Essentially as the platform owner, you want to ensure games sold for the platform "just work", and if you have a bunch of third parties running bad software, consumers would lose faith in the platform altogether.
treyd|1 year ago
throwaway48476|1 year ago
brokenmachine|1 year ago
ashleyn|1 year ago
Lammy|1 year ago
liamwire|1 year ago
dinartem|1 year ago
So I had no real hardware to test any of the software I was writing, and no other chips (like the Apple G5 we used as alpha kits) had the custom security hardware or boot sequence like the custom chip would have. But I still needed to provide the first stage boot loader which is stored in ROM inside the CPU weeks before first manufacture.
I ended up writing a simulator of the CPU (instruction level), to make progress on writing the boot code. Obviously my boot code and hypervisor would run perfectly on my simulator since I wrote both!
But IBM had also had a hardware accelerated cycle-accurate simulator that I got to use. I was required to boot the entire Xbox 360 kernel in their simulator before I could release the boot ROM. What takes a few seconds on hardware to boot took over 3 hours in simulation. The POST codes would be displayed every so often to let me know that progress was still being made.
The first CPU arrived on a Friday, by Saturday the electrical engineers flew to Austin to help get the chip on the motherboard and make sure FSB and other busses were all working. I arrived on Monday evening with a laptop containing the source code to the kernel, on Tuesday I compiled and flashed various versions, working through the typical bring-up issues. By Wednesday afternoon the kernel was running Quake, including sound output and controller input.
Three years of preparation to make my contribution to hardware bring-up as short as possible, since I would bottleneck everyone else in the development team until the CPU booted the kernel.
Dracophoenix|1 year ago
Oh and I'd just like to say thank you for your contribution to my childhood/adolescence.
dvdbloc|1 year ago
jolan|1 year ago
saturn8601|1 year ago
landr0id|1 year ago
It’s going to be a doozy
vlovich123|1 year ago
kaoD|1 year ago
Can anyone confirm if I'm on the right track with my guess?
LPisGood|1 year ago
cbanek|1 year ago