Copyright (c) 2024 Dov Grobgeld <[email protected]>

All rights reserved.

Redistribution and use in source and binary forms, with or without

modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this

list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice,

this list of conditions and the following disclaimer in the documentation

and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND

ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDi

WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE

DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR

ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES

(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND

ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT

(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Dov Grobgeld

<[email protected]>

Last edited: 2024-09-10 Tue

All files in this repository are licensed under the following BSD License. See 

The R36S is a very powerful little handheld computer, that comes with the Linux based ArkOS Open Source operating system preinstalled. The system is built with emulation in mind, but as it is a standard Linux based system, it is quite straightforward to write native programs and games for it.

This repo will explore what is needed to program the system in C. Note that in addition, you can use almost any program that Linux supports and which has SDL bindings. E.g. C++, python, and zig.

In order to program the R36S you first need to connect to it from your computer by carrying out the folloiwing steps.

1. Connect Wifi dongle to the right hand usb port

2. Navigate through EmulationStation (ES) to Options, and connect to your local Wifi, by choosing your SSID and entering your password.

3. In the Options menu, choose "Enable remote services". This will only be needed the first time, as we will turn on this permanently. (See note about ssh connections below)

4. After succesfully connecting, check the IP address you connected to through Options->Network Info

5. On your PC, launch a ssh client and connect to the R36S

6. Login with user:ark password:ark

You now have a Linux shell on your R36S!

SSH standands for "Secure SHell" and it is as standard way for unix-like systems to communicate. Once you have turned on the "remote service" option, your R36S is running the SSH daemon, and is ready for remote connections from any ssh client.

There are a large veriety of ssh clients available for different systems. Though in principle it is possible to connect a keyboard to the R36S and program it directly, it is much more convienient to use a "real computer" with a keyboard and connect by ssh. There are lots of ssh clients and tools that for various operating systems.

Here is a list of some of them:

1. Command line ssh - This is the standard terminal connection

2. putty - A client for Windows system

3. termux - This is an android terminal emulator which contains an ssh client. If "all" you have is a android tablet with a keyboard, then you can use it to program the R36S.

4. Microsoft Visual Code - There are several clients available as extensions. This especially useful when you program on the R36S, and through the extension you can use edit remote files and then, compile and run your programs straight from the editor.

5. (emacs with tramp - This is what I use, but I have long ago stopped trying to persuade others to copy my old habits. :-) )

Note about security. By default ArkOS comes configured with default user/password ark/ark. Once you connect the first time you are strongly encouraged to change the password to something else by issuing the `passwd` command:

Note that when you are typing passwords at the shell, **there is no echo**, so you won't see neither the password you type nor any placeholders like "*".

In addition to password based authentication, ssh allows public key based authentication, which will allow you to connect without needing to type your password. Describing how to set that up, is beyond the scope of this tutorial.

Scp stands for secure copy. It is convenient if you are editing the source files of your programs on your desktop and you can then copy them over to the R36S before you compile.

git is a version control system. It is not strictly necessary for programming the R36S, but you do not want to work without it. It will allow you to backup and do source control of the program that you develop, and will also provide a convenient way of syncing the programs that you develop, between your R36S system and yor desktop.

Once you have connected the first time by your are working at the Linux prompt. We are now able to modify and setup the system to make it suitable for programming, initially for C and C++ .

Here are the steps that you need to do:

1. Automatically allow ssh connections without needing to turn it on through the ES menu:

2. Setup C and C++ environment. The arkos system comes with some of the system packages crippled, e.g. they are missing header files needed for C-compilation. The following command rectifies this as well as sets up additional system development packages that we need:

3. We are now ready to compile our first C-program. To do so, first clone this repository by git

4. You can now compile your first program from the command line

This program writes "Hello world" to the console and quits.

5. If you are using Visual Studio Code on your host computer, install the "Remote - SSH" extension from the Visual Studio Market place. The first time you connect, visual studio will dowload the VS Code Server, and it will then allow you to edit files on the R36S.

(I tried installing the Microsoft C/C++ extension. However, I could not get this to work. I'd be happy if someone can explore this further).

Our first hello world program was a command line program. But to write games, we want to have graphics. The R36S supports the standard graphics library SDL2. We can test compiling a SDL2 based c-program as follows:

This worked, somehow, but our program "collides" with the use of the screen by ES, because our program and ES are both running at the same time.

To fix this we can exit emulator system by Menu→Quit→Quit Emulationstation. This will turn the EmulationStation off, until next time you reboot the R36S.

If we now rerun ./hello-sdl2, we get only our colorful SDL on the screen:


Even though the R36S is using a standard SDL, there are a few specifics that you need to be aware of:

1. The screen is 640x480 pixels. This is the only resolution that you can use.

2. All the input controls are mapped as joystick buttons and axes. You can read the state of the joystick by the standard SDL2 joystick functions. In order to use the joystick you need to open it as follows in C:

Once this is done, you can read the state of the joystick by the standard SDL2 joystick functions:

The following table show the mapping of the joystick buttons and axes to the R36S controls:

| Joy-Button | Description |

|------------|-------------|

| 0 | B |

| 1 | A |

| 2 | X |

| 3 | Y |

| 4 | L1 |

| 5 | R1 |

| 6 | L2 |

| 7 | R2 |

| 8 | D-Up |

| 9 | D-Down |

| 10 | D-Left |

| 11 | D-Right |

| 12 | Select |

| 13 | Start |

| 16 | Fn |

The axes are mapped as follows:

| Joy-Axis | Description |

|----------|------------------------------------|

| 0 | Left joystick - Left-Right motion |

| 1 | Left joystick - Up-Down motion |

| 2 | Right joystick - Left-Right motion |

| 3 | Right joystick - Up-Down motion |

The program `print-joystick` will print the axes and buttons of the joystick to the console.

Press Fn+Start to exit the program.

It is possible to setup EmulationStation to support our native games. This is done by modifying the following files:

* `/etc/emulationstation/es_systems.cfg` - This file contains a list of our "emulators". We will add a new system "native" to this file.

* `/etc/emulationstation/themes/es-theme-nes-box/` - Contains themes for the various emulators. We want to add a theme for our "native" system. If you are using another theme, you will want to modify the destination.

To simplify this, enter the `scripts` sub directery of this repository and run the script `install-native-emulator.sh` as follows:

By default this script will reboot the R36S at the end. You may change this behavior, and other defaults, by setting the command line argument.

If all goes well you will now have a native menu in emulator station:


And if you enter it, you will see the c++ sdl program listed as a "game".


The "native" theme images were created by me and are free to use and copy.

First of all, this repository, and this article is work in progress. I hope to expand it as time allows.

However, my intention was not to teach "everything". There are lots of material available on the net about Linux, SDL, git, game programming, and more. My intent was to try to put these into perspective with regards to the R36S.

Please let me know your feedback and comments!

cmake_minimum_required(VERSION 3.13)

project(hello-world VERSION 1.0.0 LANGUAGES C)

add_executable(hello-sdl2

hello-sdl2.c

)

find_package(SDL2 REQUIRED)

target_link_libraries(hello-sdl2 PRIVATE SDL2)

#include <SDL2/SDL.h>

#include <stdio.h>

#include <stdarg.h>

#include <stdlib.h>

#include <string.h>

static void die(const char *fmt, ...)

{

va_list ap;

va_start(ap,fmt);

vfprintf(stderr, fmt, ap);

exit(-1);

}

#define SCREEN_WIDTH 640

#define SCREEN_HEIGHT 480

int main(int argc, char* argv[])

{

// Initialize SDL

if (SDL_Init(SDL_INIT_EVERYTHING) != 0)

die("SDLInit Error: %s\n", SDL_GetError());

// Create a window

SDL_Window *win = SDL_CreateWindow("Hello, World!",

SDL_WINDOWPOS_UNDEFINED,

SDL_WINDOWPOS_UNDEFINED,

SCREEN_WIDTH, SCREEN_HEIGHT,

SDL_WINDOW_FOREIGN);

if (win == NULL)

die("SDL_CreateWindow Error: %s\n", SDL_GetError());

// Create a renderer

//SDL_Renderer *ren = SDL_CreateRenderer(win, -1, SDL_RENDERER_ACCELERATED | SDL_RENDERER_PRESENTVSYNC);

SDL_Renderer *ren = SDL_CreateRenderer(win, -1, SDL_RENDERER_SOFTWARE);

// Setup t0 time using SDL

Uint32 t0 = SDL_GetTicks();

if (ren == NULL)

die("SDL_CreateRenderer Error: %s\n", SDL_GetError());

// Event loop

SDL_bool quit = SDL_FALSE;

while (!quit) {

// Poll for events with timeout of 100ms

SDL_Event e = { .type=0 };

SDL_WaitEventTimeout(&e, 10);

switch (e.type) {

case SDL_QUIT:

quit = SDL_TRUE;

break;

default:

break;

}

// Set draw the interface

SDL_SetRenderDrawColor(ren, 0, 0, 255, 255);

SDL_RenderClear(ren);

// Draw and animate

SDL_Rect fillRect = { SCREEN_WIDTH / 4, SCREEN_HEIGHT / 4,

SCREEN_WIDTH/2, SCREEN_HEIGHT / 2 };

SDL_RenderFillRect(ren, &fillRect);

SDL_RenderPresent(ren);

// Exit after 5 seconds

if (elapsed > 10000)

break;

}

// Clean up

SDL_DestroyRenderer(ren);

SDL_DestroyWindow(win);

SDL_Quit();

return 0;

}