Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Orange Pi Lite (Slim Version)
I am interested in trying an Slim version for OPI Lite.

Is there any chance to provide a BETA version for test? I am on my vacation so I will have enough time for testing.
you can try this one for now
i dont know if it boots as i dont have an opi lite to test
Dear alexkidd,
thanks for sharing an attempted image for the OrangePi Lite.

I attempted to boot from it, it fails with the following result on screen:
Download the file and copy to /boot/dtb-5.2.14-sunxi
You must be able to read ext4 partitions (native Linux or windows with app like paragon extfs)
Let me know which error you get now
Still "Could not find a valid device tree". FWIW, the file already existed but was different, so I overwrote with yours.
Can you edit /boot/armbianEnv.txt and move the fdtfile line to first one?
Dear alexkid, it doesn't change anything.

I have to admit that I expected that. The armbianEnv.txt appears to be loaded correctly.
Attempting to load the fdtfile (line 53 of /boot/boot.cmd I assume) still results in a FDT_ERR_BADMAGIC error.
Then it complains that we should configure the FDT address via "fdt addr <address>" command.

Based on that boot.cmd, and other examples I've found, I assume that the fdt_addr_r variable is loaded from the dtb file. The "fdt addr" call, right below, fails as a result of the "invalid" dtb file. Now, I don't know how to generate a valid dtb file... But neither the original one that was on the image nor the one you provided me with after are read as "valid".

I wanted to make some experiments but apparently the boot.scr is actually the one loaded and I need some tools (mkimage at least) to generate the boot.scr from the boot.cmd ...

As stupid as it may sound, I'm under the impression that the fix would be to change:
`load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile}`
`load ${devtype} ${devnum} ${fdt_addr_r} ${fdtfile}`
in boot.cmd and to recreate the boot.scr from it.

Indeed, hooking up a keyboard and executing the later myself, the commands appears successful and $fdt_addr_r is defined.

Yup. Installed u-boot-tools, created a new boot.scr with `mkimage -C none -A arm -T script -d boot.cmd boot.scr`, where I changed boot.cmd as mentioned above.

After partition resize, reboot, ended up with a MS-DOS then Win 3.1 bootscreen. WAT?!
Hahaha, trolling us?
After waiting a bit, ended up in RetroPie, configured a gamepad, just tested one of the default Megadrive games. Appears to work as expected.

Awesome news! Thanks for debugging
report any bugs you find

p.s.: and yes, you've been "dos rolled"
Not sure whether you want the bug reports in this thread or in separate threads...

Had some time to test the image a bit more.
Turns out that the sound worked at bootup (heard the iconic SEGA sound) but it doesn't work in emulators (at least for Genesis and N64).
Currently investigating.

Possibly Related Threads...
Thread Author Replies Views Last Post
  Orange pi PC2 davide84e31 152 27,567 03-26-2020, 10:30 PM
Last Post: alexkidd
  Latest orange PI PC2 what is working and what is not: Lamerjack 25 2,561 03-11-2020, 07:25 PM
Last Post: alexkidd
  Retrorange for Orange Pi 3 jurjur 0 197 03-04-2020, 07:00 PM
Last Post: jurjur
  4.3 Full for Orange Pi One giankyfava 47 13,362 03-01-2020, 04:35 AM
Last Post: akira84
  Orange PI Win PLus - restarting djmcg 24 4,907 02-20-2020, 05:12 PM
Last Post: Lamerjack
Bug Orange Pi PC - reporting bugs found caioandrade 22 6,591 02-18-2020, 05:04 AM
Last Post: PREngineer
  Orange Pi Pc+ GemRB / Stratagus Hotab777 5 543 02-15-2020, 04:40 PM
Last Post: Hotab777
Bug Orange Pi PC - random audio error caioandrade 9 1,069 01-24-2020, 08:53 PM
Last Post: alexkidd
  Orange Pi Pc+ DosBox troubles Hotab777 4 709 01-18-2020, 10:13 AM
Last Post: Hotab777
  will work on orange pi plus 2? Folko 1 409 01-13-2020, 09:29 PM
Last Post: alexkidd

Forum Jump:

Users browsing this thread: 1 Guest(s)