Why aren't there any releases or flash instructions?

[ouroboros420]

Would be great.. Also are there any changelogs to see? since the commit description you are leaving kind of isn't existing :D

[32teeth]

Hi, thanks for getting in touch

The main markdown has

Retro Odroid Go Firmware

Something a little different

Based on the Retro ESP32 GUI

This is currently a WORK IN PROGRESS You can build from source. We will release a .bin file soon

We are working on a flashable bin currently and will be available soon

In the meantime you can run the ./ota script in the Scripts folder

[Jason2866]

My Odroid Go is just ordered... This should work esptool.py --chip esp32 --port COM5 --baud 460800 --before default_reset --after hard_reset write_flash --flash_mode dio --flash_size detect --flash_freq 80m 0xd000 ota_data_initial.bin 0x1000 bootloader.bin 0xf000 phy_init_data.bin 0x8000 partitions.bin 0x10000 Retro-Odroid-Go.bin You find the files in the build folder ;-)

[francoiswnel]

Hi, any chance you can please release the work-in-progress flashable bin for the Odroid Go? We know it's still in development, and we understand the caveats. A while ago I tried building it myself but ran into many issues, in both Windows and Linux environments. It seems the project is still very much tied to your dev environments, which is understandable, but it makes it more difficult to just pull it and build.

[32teeth]

Hi @francoiswnel

easiest thing to do on Linux is to

1. fork the repo
2. clone your repo
3. run ./ota from scripts folder and answer yes to recompile and clean
4. follow the rest of the instructions on ./ota gives you

[francoiswnel]

@32teeth

Thanks for the reply. Unfortunately those instructions are not working.

I've cloned a fresh copy of the repo, ran ./ota from the Scripts directory, but the build that it kicks off fails with various environment variable issues, like it can't find the Xtensa toolchain despite it sourcing helpers/paths.

Besides this, even when not rebuilding the binaries, the script still fails to flash them and just exits with "goodbye". I've updated it to point to /dev/ttyUSB0 where my Odroid Go is mounted, with no luck.

I may be mistaken but I still think the scripts may be relying on your own dev environments. It shouldn't be this hard to pull a repo and build it.

Any advice? Is it possible for you to attempt to build/flash the firmware in a fresh environment, like a VM?

[rzr]

or dockerfile ?

[tleb]

As said by others, build instructions would help a lot. Here is what I found out:

$ # install a few dependencies
$ sudo apt install flex bison gperf libncurses-dev
$ # install esptool, which should be in the path
$ pip install esptool
$ # you should have esp-idf installed (git clone esp-idf then run the install script, then the export script) and IDF_PATH set correctly

Even with this, the build doesn't succeed, missing some modules which I didn't look for. I wonder if we should be using the esp-idf version that is in the Tools folder but it's not recognized correctly by esptool.py if IDF_PATH is set to that. To find this out I commented every clear in the Scripts folder, which allowed me to see the build log outputs.

I hope this convinces @32teeth to push proper build instructions. I would be happy to provide feedback on those.

I have a Odroid Go that I plan on using for a non-gaming project. What is the tooling state right now? If I understand well, the upstream esp-idf cannot be used? What should I use? OtherCrashOverride's esp-idf fork (is there a quickstart guide somewhere)? Or is my best bet to use the Arduino lib?

Thanks for your work!

[32teeth]

Thanks for the feedback, and promise i will get back to it. Been busy with other work, and pandemic-mania-onium

You could alternately use the @OtherCrash version for now

Soon...

[tleb]

I've got a moving square using the latest esp-idf and odroid_display.(c|h) from the original firmware without any issue for the moment. :) I'll look at the patches made by OtherCrashOverride on his fork to see what is going on.

Don't hesitate pinging me when you need feedback.