On Sun, 10 Feb 2019 10:03:45 -0600, Cecil - k5nwa wrote:
> On 2/10/2019 7:08 AM, albert wrote:
>> Last saturday we had a meeting of the Dutch Forth chapter.
>> One of the members I met there has built a Forth that runs on a
>> Raspberry pi as an os. It accomodates all sort of I/O including
>> graphics. I've seen the (single)
>> assembler file, and understand little, except that he had to include
>> all the addresses, constant, mask etc. from the BCM chip underlying the
>> pi and knows how to use them. I'm particularly impressed about
>> initializing the memory map.
> [snip]
>
> Impressive since the hardware is not open there is a lot of digging to
> be done for information to make it work. I'm not familiar but does the
> Raspberry have a built in BIOS to provide basic software to talk to the
> major hardware items? If not the every new model of the Raspberry will
> be a major struggle to get it working.
The Pi is /almost/ documented, as in there's hardware documentation for
everything... except the graphics and some other internal workings of the
Broadcom SoC. This is especially bad because the graphics chip is what
boots the system in the first place (think of the baseband processor in
mobile SoCs), you can't just disregard it. However, for the /first/ Pi,
much of the reverse engineering work has been done[1]; people have at
least written their own boot routines and an emulator that can interpret
the vendor ones. I don't know whether this helps with later Pis, but it
probably does at least in part.
(It surprises me that, despite all this, the Pi has been successful,
while the completely documented BeagleBoard seems to have faded into
obscurity. The situation with secret undocumented hardware is
understandable. Deplorable, but... at least the reasoning is clear.
This, on the other hand, is both sad and puzzling.)
[1]:
https://github.com/hermanhermitage/videocoreiv
--
Alex