Thanks for your response!
I’m not expecting it to work out of the box, I wanted to see if I could get it booted to where you had it, so that I could start poking around and seeing what I could get working. I am not by any means an expert in embedded systems, but I am trying to get more involved to become better versed in it. I’ve built some kernels and bootable images for simulated/emulated environments at my work, and this was a natural next step to dive a bit more in. I have an old Ouya kicking around and figured this would be a good use of the hardware - it’s using the Kingston memories though, sorry I wouldn’t be able to help with your request for more data at least.
My comments about documentation and being more explicit were because a lot of the steps you’ve listed in your Wiki are really high-level and general, and because there is implied information that may be obvious to you since you’re knee-deep in working on it means I and others may make an assumption you haven’t and we’d be spinning our wheels and wasting your time asking questions. I really appreciate the info you put in this thread - this explains a lot of the behaviour I’m seeing, and what got you to that stage, and what my next steps are going to be (getting my serial console connected).
I figured the rpi image would be tweaked and cause problems, but it was unfortunately the only armhf image they had readily available to download - I was hoping I’d get lucky. Your instructions just said you’d used a 20.04 Ubuntu image supporting arm7hf, so it was just an assumption I made that I wanted to rectify. I’ll use your method next to at least make sure I’m at parity to what you’re doing.
Oh, also, are you checking in your modifications for the boot image changes anywhere to allow larger kexec images? I’m curious to see what you did. I assume it’s not in the v5.8-ouya branch, as I hadn’t seen any updates for a bit of time on it.
I really do appreciate you taking your time to answer, in any case.