deater wrote:
My personal goal right now is to figure out enough of the GPU to get some 3D graphics going
On that note,
https://github.com/LdB-ECM/Raspberry-Pi/tree/master/GLES2_Rotatedeater wrote:
...file transfer going so I can work on the GPU stuff w/o having to constantly swap SD cards. Editor is finally working. I was looking into Zmodem to transfer files over the serial connection and didn't realize what a licensing mess that was.
Yep, I run into that issue as well. There's an already working FOSS solution though:
raspbootin (for AArch32) and my rewrite that also supports chainloading,
raspbootin64 (for AArch64). On the PC side they both use the same, pretty simple utility
raspbootcom to send the kernel. If you have troubles compiling it with latest compilers under Linux (I had), see my
rewrite of the sender, or you could try the
Java kernel sender.
The protocol is extremely simple:
Code:
"\003\003\003" (RPi to PC, ready to accept)
N, four bytes LE (PC to RPi, size of kernel)
"OK" or "SE" (RPi to PC, okay or size error)
N bytes (PC to RPi, the image)
but if you want, you can replace this easily by some BBS modem protocol if you'd like and use minicom on the Linux side (GPL'd and supports multiple file sender protocols).
The
rpi-boot source could be useful too, it uses a slightly modified version of the protocol above (with checksums), and it includes a
sender that can be compiled with Win32 natively. I would not recommend to use rpi-boot as a tool though, because it's a bit bloated imho, but it's perfect to learn from its source.
Cheers,
bzt