Hi everyone and especially the team responsible for this amazing software project. We are all indebted to you for your dedication to Annex Basic.
Annex 32 has built-in support for the M5stack and as such pin assignments are hard coded into the executable image.
I notice that a handheld game emulator built by https://www.hardkernel.com (the Odroid-Go) is a nifty inexpensive ESP32-WROVER based gadget that has many useful built in features plus an expansion interface making it an ideal candidate to run the Annex32 Basic interpreter. There are a few pin assignments in the Odroid-Go that conflict with the pin assignments hard-coded into the Annex32 binary image but if these differences can be handled during initialisation of each device interface then perhaps the gadget will work fine running Annex32.
This is not meant to be an advertisement for the Odroid-Go however I do like this device and it would be brilliant if I could get Annex32 to run on it making use of its inbuilt hardware platform. (More details are available here:-
https://wiki.odroid.com/odroid_go/odroid_go
)
I note that in the original Annex basic for (ESP8266) the TFT.INIT command allows certain pin allocations to be provided during the initialisation phase of the display interface. Would it be possible to rework (expand) the TFT.INIT command on Annex32 to mirror the flexibility of the original TFT.INIT command? This would allow using the inbuilt display in the Odroid-Go.
With similar attention to initialisation code of other inbuilt devices on the gadget like the SDCard and the audio speakers the Odroid-Go could literally “sing” the praises of Annex32 basic.
I also notice on the Config Page of the running ESP32 device (192.168.4.1) there are some options relating to the M5stack under TFTdisplay however I cannot find any documentation on these “Options” items and how they can be manipulated.
Any thoughts on these ramblings would be greatly appreciated.
Cheers Peter.
Although Annex32 Basic is my first choice, I am able to use MicroPython to achieve my goals as Hardkernel have provided the appropriate software library.
Cheers Pete
Your offer is very much appreciated and I look forward to a time when you have had the chance to incorporate this additional native hardware support.
I hope, by doing so, that Annex32 Basic will reach an expanded audience allowing you and your supporters to get the kudos you deserve for your considerable efforts in providing this outstanding contribution to the ESP32 community.
Keep up the good work.