Handheld retro game console “Retro FC” review

The memory of past, my younger times remembers what I played, what I wanted to play. This small gaming console has hundreds of unclear to original or not games, and some are not working correctly. But China made this for only under 20 USD includes shipping fee – Great copyright avoiding leading nation. And I can waste my boring time with this small device.

CPU : Epoxy molded some kind of 8bit MCU.
RAM : unknown ( maybe included in CPU )
RAM : Seems to kinda NAND flash ( maybe within 512MB )
LCD : 3″ TFT ( 320×240 or less, NF pannel, not IPS )
TVO : Supports analog VHS out with mono audio thru 3.5mm plug to RCA cable
BAT : BL-5C 900mAh

Counted to 168, some games are same but different name or version, some games are not able to play because key dosen’t work.

Almost of similar products ( just different game counting on box ) has same box detail and view as like this:

Contains a paper what described how to use – yes, it is manual – with a battery and a charging cable ( old school USB mini B type ). Specially BL-5C is very popular Lithium based battery of China products.

BL-5C battery, 900mAh capacity

Little review
 Console is similar size of Nintendo Gamboy (legacy version of 4 gray level LCD), actually copied shape exactly. But each buttons feeling to weak to good to press for gaming. No option to hearing in headphone thru 3.5mm headphone jack.

Device UI only supports English or Chinese with Final-Fight in game OST as background music
Many games, but real playable is less.

 Many games are ready but I could played for few games. Almost of games modified version in China ( maybe for avoiding copyright from original version ). But still it got some positive side for player – “WORTHY !” – for under 20 USD.

 This is perfectly dark sided, avoiding copyright laws, cheap piece of plastic. Hard to control player charactor in game by bad rubber dom buttons. But I am now playing this little device before going sleep in muted. Long battery helps drop worries to recharging. Many junk games feeling myself going tired as soon for good sleeping. All bads can handle with under 20 USD.

Easy way to build Rock960 ARM64 system image.

Why need to do this?

96Board developing team only provides armhf ( arm 32bit ) pre-build images in officially. But some people as like me, are need to use AARCH64 for better performance. This article is for people who demands runs Rock960 board on AARCH64.


  • x86.64bit debian based Linux, recommends ‘Linux Mint 18.x’.
  • Make sure your linux ‘up to date’ by these
    • sudo apt-get update
    • sudo apt-get upgrade
  • These packages to be installed before start.
    • git related
      • repo git-core gitk git-gui gcc-arm-linux-gnueabihf u-boot-tools device-tree-compiler gcc-aarch64-linux-gnu mtools parted pv libssl-dev
    • some others
      • binfmt-support qemu-user-static python-dbus python-debian python-parted python-yaml
    • use  sudo apt-get install ... with above packages to be installed.
  • Some other tool binaries, ‘rkdeveloptool’ and ‘k3399_loader_v1.12.112.bin’.
    • Recommend to install ‘rkdeveloptool’ to your system – ‘/usr/local/bin’.
    • ‘rkdeveloptool’ is placed in ‘rkbin/tools’, or refer to my prebuilt image archive.

Clone Rock960 repositiory

There’s may many ways to getting source codes, but I recommend to do this way with your git client. And we before start, make a directory to identify where we are starting rock960 building work, so I recommend to make ‘rock960dev’ directory on your home ( ~, or ${HOME} ).

Then, let’s do these, remember – this work takes may long long waiting …

Build kernel and u-boot

You may waited for long time to be done, now we need keep moving to next step to build kernel and u-boot. these are important your board works to ARM64(AARCH64).

And remember, Rock960 board model name is ‘rock960ab’, or if you bought ‘C’ model ( no built-in eMMC model ) means ‘rock960c’ – it’s little bit different model but same platform of RK3399.

Our journey will be started in ~/rock960dev, and type like these.

This works generates each ‘.config’ files in kernel and u-boot directory with default ‘rock960ab’ model configurations. You can change kernel options with ‘menuconfig’ in kernel directory with make ARCH=arm64 menuconfig.

Build file system

All linux ( or Windows, or Android too ) need file system that contains many things like busybox and desktop ( X11 ) for doing something. So we need build file system.

First thing to do, is install some packages in local ( don’t need to consider failure while install these, just skip them if met failure screen ) in ‘rootfs’ directory.

Le’ts move to ‘rootfs’ and your current directory path will be ‘ ~/rockdev/rootfs’, then let’s do this for once.

Now, time to build desktop system !

Just a wait, you didn’t minded to build desktop (LXDE) build ? Just change TARGET to what you wnated – maybe server with ubuntu release ?

And it may takes really long waitness, drink a beer and fish&chips. Or a cup of coffee. Or continue to tomorrow.

Make a system.img

Everytime you done each work, all generated file copies to ‘rock960dev/out’ directory except root file system ( it generates linaro-rootfs.img in rootfs directory ). So when we reached to step for making file system done, now it need to make it a whole image as know as ‘system.img’.

Now let’s move to rock960dev directory, then proceed this.

A file ‘system.img’ will be generated in ‘out’ directory.

Flashing your image to Rock960 board !

Now it is left only for last step of flashing new image to eMMC.

Let’s make your datas backed up to somewhere in Rock960 board, then step inside to flash eMMC and new 64bit linux with ‘MASKROM’  and ‘RESET’ buttons on board. Press them together and release only ‘RESET’ to enter ROM writing mode.

Now flashing them all


Rock960 debian stretch prebuild system image for AARCH64

Currently 96rock’s (VAMRS) Rock960 board officially published for debian stretch image for 32bit ( they aren’t published for AARCH64 ), so I rebuilt their open source for supporting nvative AARCH64 at all with bundled LXDE.

Download link:


This compressed binary contains many things: seperately kernel and u-boot image. But you don’t have to flash them in each, just use rkdeveloptool in toolbin.


  • Extract compressed file to somewhere to use them easily.
  • Move to extracted path.
  • Give permission “rkdeveloptool” binary to executive, use
  • Make your Rock960 board connected USB-C to your PC and turn to maskrom mode ( push both of maskrom and reset butttons, then release only reset )
  • Your host PC ( may Linux ) should detects new USB device, then it may allow to downloading mode with rkdeveloptool.
  • Then just write system.img to your board.
    Warning : all your datas in eMMC may deleted, back up your data before doing this !
  • It may takes for minutes, wait for done.
  • Then reset your board.

After boot up

You may see LXDE desktop within a minute, then connect to your WiFi, then make systems up to date with these.


How to know 64bit ?

Just make a C++ source and compile it, then run it for a test. ( before you may need get install g++ with this :  sudo apt-get install g++ )



Additional build info

My AARCH64 system image build in these options –

  • Default Rockchip configuration
  • Not supports SOC cameras ( a.k.a MIPI-CSI )
  • USB-C OTG supports as default option ( removable drive at host PC )

Recommended work to do after flashing image

  • Keep update your system via ‘apt-get’
  • Manage your power configuration – I don’t recommend to use power manager ( there’s many Rockchip DWM driver control errors )

Recommended for developers

  • Install ‘g++’ first.
  • LXDE’s X11 library is not much functional – need to consider non-acccelerated desktop graphics ( because MALi 8xx not suppors OpenGL ! – OpenGL|ES and OpenGL is not compatibled )

Latest Inland SSD 480GB has no DRAM !

When I bought Inland SSD 480GB again from Amazon, I found new SSD is exactly different from old model by just open paper box – that was plastic enclosured SSD, it was never expected.

Left : new, Right: old

 Aghhh .. always problem is ‘cost down matter’ of many manufacturer, new SSD model may changed ODM manufacturer, It means no more metal enclosured chasis, no DDR cache for stability and fast performance for end up capacity, so they are discontinued many things. Here is more negative issues when I open case for putting thermal pads to manage heating.

One third size PCB from the past, why? What happended to them  … Yes, new Inland SSD 480GB is totally different, here is PCB picture of previous model with enclosure, black painted steel? aluminium? with full sized PCB with many components.


Previous SSD 480GB contains full size PCB with many Toshiba NANDs with DDR memory beside Phison controller. Every side of PCB finished with grounding that increases durability. Much different with new !

But new PCB is smaller than previous, it is like Chineses cheap SSD, just one third size from SATA3 connector, Different Phison controller is really smaller than previous, different model of PS3111-S11 from PS3110-S10.

New SSD model PS3111-S11 is made for 3D MLC and TLC NAND models without DDR cache, just supports SLC cachining for limited capacity. So fresh device may not makes troubles while write datas until this SLC caching ran out – then most of lacks of performance occurs mostely filled capacity in half.

New SSD 480GB ironed two NANDs up and down side, may better than Chinese single module. But still there’s nothing like write cache on board. ‘Quick forget makes me comfort’, yes fast way is just close the enclosure with my minimal thermal therapy, I put some copper tapes to spread heats from controller and backside NAND while it operates in high temperature thru thermal pad.

Plastic enclosure makes high temperature thermals stucks in small chamber because there’s nothing like to space to spreads out heated air to outside of enclosure. So I am always using this solution to makes components of high temperature heating components to against roasted death of them.

Fresh performance at USB 3.0 controller with UASP is almost 300MB/sec to sequence write, and sequence reading is 360MB/sec.

Phison PS3111-S11 controller supports thermal monitoring – some Chinese cheap models are not support this, with minimal S.M.A.R.T features. I’m not sure PS3111-S11 how keep good performance when filled in over half capacity until now, I will continue to write in later for getting more experiences.

Anyway, “Inland” sold their trust to money for thir profit.

Create HBITMAP from Fl_RGB_Image

Here is a simple code for convert Fl_RGB_Image to HBITMAP.

It should be help to convert Fl_RGB_Image ( must have depth 4 for RGBA ) to HBITMAP. And it works for changing Fl_Window to Layered window easily like this.

And it may runs as this.

How to set debug mode easily for libusb and libuvc.

Here is a tip for programer for debug any application with using libusb(x) or libuvc.

There’s many way to debug what it going on with gbd when you are using gcc or MinGW (incl. MinGW-W64) , you may feels somehow difficult to control gdb to debug in deep call stacks without IDE like Code::Blocks.

You can use putenv() to set debug mode to print all messages to ‘stdout’ (aka. console, or terminal) .


Enable debugging message

Meaning of number appends LIBUSB_DEBUG is this level :

When you enabel this, you can see all debugging messages on your terminal or console.

Developing libuvc for MinGW-W64, day 1

Now I am trying to get YUV2 buffer from formal USB camera, but it doesn’t easy on Windows system. MS designed most of USB video devices need to use Direct media layer, but it occurs many different problems while using OpenGL or hardware accelerated surface at same instance of Windows application.

So I made it from starting understand UVC and common library of libuvc.

And I understood it depends on libusb that is well known libraray for multiple platforms except Windows. So I have to make it building ways as like Makefile on MSYS and for MinGW-W64, then it comes to Josh Blake’s libusbx to customized for build in MinGW-W64 and MSYS easily.

But it still has many problems, exactly same failure for -12 ( UNSUPPORTED ).

It belongs to failure of libusb_open() returns -12 through libuvc error result. Testing open USB HD Camera with libusb or libusbx always same.

It must be study for what different Windows USB drivers, and why UVC not able to open with formal libusb, further need to understand libusb-win32 or libusbk.

So I reached same position again, Windows is not my option, really.

Server recovered back.

Everytime to updating latest versions of each plug-ins and theme makes me have check what it chnaged. And I didn’t wait for what it done for updating previous theme.

It was recovered easily to putting definition for exactly what domain name to Word Press configuration.

Raph & Emily, we are writing stories