-
Notifications
You must be signed in to change notification settings - Fork 155
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
Board support (TTGO ESP32 Tm Music) #36
Comments
I found out why and how to solve it. Its basically the I2S library that got major updates lately. By using the latest IDF with the previous I2S library version, I managed to compile and get radio working. Now I have to figure out a way to get it working without downgrading. Need to investigate more. |
Ok, I will try to investigate too. |
The release notes of the latest IDF says:
I may test it these days and do a push if I see that it makes sense. |
Changed API to the new ones, but something else is wrong. Investigation again and again.... |
I saw some commits of yours. DO they solve the issue? Did you get it working with IDF v3? |
No. I plan to integrate the old i2s driver in KaraDio32. |
Ok. It may be a temporary solution right? By replacing the deprecated I2S functions with the new implementations doesn't do the job? |
No, in fact in the code the old api is simply a wrapper to call of the new api. |
look my repo https://github.com/pilnikov/KaRadio32_fork. I updated and patched problem with i2s (Replacing with old). My ttgo play music fine. |
updated to 1.3r1. Does not work at full strength (screen problems) in version 2 bugs promised (JP) to eliminate |
updated to 1.3R3 All ok! include buttons |
I think we can close it now ;-) |
I tried to flash my board without pre-cleaning - everything works very slowly. when I open the web page - i get fails. if set 255 for vs1053 ports -> SPI init error (no GPIO for use SPI) |
http://karadio.karawin.fr/ttgo.zip |
JP tnx, all work fine! Even with 255 for VS & display #199. Tnx!
|
Yes i noticed it. Will see it when i have some time. |
Must be ok now in 1.5 R5 |
Without changes. Incorrect display of the title on the splash screen only. |
Yes sorry, now it's ok in 1.6 R0 |
JP many tnx, all work fine! |
Great. I close it |
I've been trying to port your code to this board. The job tasks are simple. It includes changing a couple of IOs, configuring the proper LCD, push buttons, and It should be good. I'm specially interested on this board. Find the schematic here It uses the PCM5102 I2S DAC.
Its the most complete ready-to-run solution I found. relatively low cost.
But now, as I'm trying to do that, I went through one issue, and one question:
How do you think it is a good idea to have a complete board support? Instead of changing individual configs, but having a whole config-set for an specific board? I tough of having some pre-set config structures, that could be changed on the terminal (something like having renderer_config and board_config pre-sets for a given board. How does this sound? I could contribute on that. I'm quiet interested on getting this board to work smoothy.
My other issue, which is more technical one: I've been trying for the last couple of weeks to get the audio playing fine. Issue is that I'm always getting musics playing as if they were in fast-forward, with noise as well. I tried changing sampling rate, master clock, clock sources, etc.. Nothing solves the issue.
I found a fork of the the KaRadio from which, If I flash the binaries already compiled, it works, otherwise, it does not. Really dont know where to look more.
It seems that there is a related issue here, but not sure it solves the issue Im having.
The text was updated successfully, but these errors were encountered: