Documentation for client binaries?

[Hypexed]

Hello.

I'm wondering if there is any documentation available for an OF client binary? I've searched online but most of what I found is documenting the OF command line. Anything else details some info about the client mode but it lacks proper information to program it. It took me a while to find that on PowerPC R5 serves as the core OF callback function along with OF parameter structure. Most of the information I have got is from open source examples and examining the Linux kernel sources.

What I need to do is to setup the console. I'm writing a chained bootloader for a PASemi PPC64 machine but I get no output from writing to the stdout handle. I'd appreciate if you could point me in the right direction regarding setting up a console to whatever display is active using the OF API. Thanks! :-)

[MitchBradley]

I can probably dog something up but the first thing that comes to mind is to write the intermediate loader in Forth. At One Laptop Per Child, we used that strategy to great advantage. The first stage boot file was a Forth script called olpc.fth. That script figured out a lot of stuff like which initrd to use, whether or not to pull updates, etc, then finally issued another boot command. It worked out quite well and was ready to develop, test, and maintain. Any file that begins with "\ " (backslash space) I.e. a Forth comment line is supposed to be recognized as Forth by the boot command.

…

On Apr 29, 2019, at 1:09 AM, Hypexed ***@***.***> wrote: Hello. I'm wondering if there is any documentation available for an OF client binary? I've searched online but most of what I found is documenting the OF command line. Anything else details some info about the client mode but it lacks proper information to program it. It took me a while to find that on PowerPC R5 serves as the core OF callback function along with OF parameter structure. Most of the information I have got is from open source examples and examining the Linux kernel sources. What I need to do is to setup the console. I'm writing a chained bootloader for a PASemi PPC64 machine but I get no output from writing to the stdout handle. I'd appreciate if you could point me in the right direction regarding setting up a console to whatever display is active using the OF API. Thanks! :-) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Hypexed]

Thanks for your response. I can understand from reading OF Forth scripts about that method. My issue with that is the OF interface in the firmware is somewhat minimal and only exposed internally. It uses CFE as a user interface but client binaries are ran with an OF binary interface. On top of that my bootloader is loaded and ran as a pure binary. So everything I do has to start from the binary interface and go from there. Why I am going about it this way is because the core bootloader can read config files and build up a linked list of boot files all loaded up and ready to go. For some reason output to the screen is locked out despite an obvious framebuffer being in view. It would help to even output to a serial console. What I don't know is what is locking out console output and if I need to set it up a certain way or reset the display through some OF methods to bring back a basic text console. It's kind of frustrating as I am coding blind since I can't tell what is wrong. The only output I can produce is from purposely crashing my code leaving a debug log on serial but that doesn't help me. :-)