-
-
Notifications
You must be signed in to change notification settings - Fork 11
no issue - question about composite video #9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Bitluni's video generation code and the one in ESP_8_BIT are very different. They both worked on the monitors I tried, but the code in ESP_8_BIT seemed superior and was more capable. I do not understand either code well enough to say why that might be. You didn't mention why you you were looking to use Bitluni's code, but if you simply want to run his demos, I made a fork of his code and demos which have been adapted to use the video generator backend from ESP_8_BIT: https://github.com/marciot/ESP32CompositeColorVideo You may have better luck with that one. |
Thank you for your answer. |
This took me like 3 evenings of swearing to figure out, but you need to downgrade your esp32 tool chain to the one the code was originally written for. Bitluni's code works fine for me on esp32 v1.0.1. and Arduino IDE 2.2.1(Latest). |
Hello M0NWY and thank you so much for sharing your solution. |
I meant the esp32 toolchain that can be integrated into the arduino IDE via
the board manager and the external URL that you add in to the preferences..
V1.0.1 worked for me, even with the latest arduino IDE (v2.2.1).
…On Tue, 9 Jan 2024 at 21:58, Bob Sleigh ***@***.***> wrote:
Hello M0NWY and thank you so much for sharing your solution.
However I never compiled bitluni's examples with Expressif toolchain but
with Arduino IDE
Which version of toolchain worked for you ?
—
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACTFGWDIGWG4VFRNIVJJP2LYNW4QLAVCNFSM6AAAAABAR6RAGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBTHA3DGMZXG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
@BobSleigh38: Can you provide a link to the two commits you mentioned? I have a hunch the problem has something to do with the initialization of the APLL hardware. If I can see what changed between the two commits, maybe I can see if anything might have affected the way the APLL hardware is initialized. |
Hi Marciot ! |
The guilty commit is here : espressif/arduino-esp32@00214d5 |
Ah, so I searched that repo for "rtc_clk_apll_enable", which is the function I suspect might have changed, and I did not find it. It looks like the "espressif/arduino-esp32" is just the code that links the Arduino IDE to the underlying espressif code. That code we care about is this other repo: https://github.com/espressif/esp-idf So, now the challenge is to figure out which versions of the esp-idf introduced the change. I appears as if the arduino-esp32 repo has commits such as this one which indicate when the underlying IDF is changed: So with this, it should theoretically be possible to cross reference to the other repo. |
Okay, so here are my finding based on the information you provided:
|
So, where I am at. I suspect the code in espressif/esp-idf@c69f0ec from July 26, 2021 is the last working code, which was included in arduino-esp32 2.0.0 which was released on August 31, 2021. However, it is unclear which version of the esp-idf code is used in the October 25, 2021 release of 2.0.1 RC, as the last reference to the esp-idf repository occurs on October 13, 2021. From that point on, I cannot find valid identifiers I can cross-reference between the two repos. |
So I am falling down a rabbit hole here. Here is what I don't understand. In the video code, there is a function call that configures the timers. It looks like this:
Notice it takes five arguments. When I search the esp-idf repo for that function, I get a much shorter version which does not have the extra arguments: https://github.com/search?q=repo%3Aespressif%2Fesp-idf%20rtc_clk_apll_enable&type=code I cannot locate the five argument code in the esp-idf repo, which suggests maybe it isn't the correct code. If I randomly Google for "rtc_clk_apll_enable", I get what appears to be a fork of esp-idf that does appears to have a "rtc_clk_apll_enable" with the correct number of arguments: So I am wondering whether at some point, those extra arguments were removed from esp-idf. Could this possibly be the reason things broke? I wonder whether it would be possible to take the function out of chunhuajiang's repo and see if using that to initialize the APLL hardware instead of the current function would solve the problem. |
Thank you so much much for your investigation !! I did add those lines in bitluni's simple composite demo, right before the hack to get the 13MHz I2S frequency. Right now I'm using FabGL, but it's using a huge library only for the video part, it takes ages (and memory?) to compile. I'm coding a pinball game, based on fantastic 1ko js demo from this guy Thank you again :) |
Hello and thank you for sharing your work
I understand that your code for composite video is between bitluni library (esp32lib) and ESP_8_BIT library
Your demo for the clock works fine for me on a car dvd player screen
However I have no image when I use any of bitluni code.
Did you have the same issue than me ? How did you solve it ? Does it have something to do with bad syncing (PLL/APLL) ?
I really enjoy the clock :)
The text was updated successfully, but these errors were encountered: