-
Notifications
You must be signed in to change notification settings - Fork 28
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
Jama Func microSD test function #43
Comments
Hey, this is really cool! :) You didn't have the SDCard library in your MicroPython Port, right ? ( So here you can actually choose the SPI GPIOs for testing the particular ESP32 boards. Also, in the information of the "Jama Func", you can put your mail (see the template) and your site or github in www :) |
Hi,
when I try to start the SD Card function I get the error "No SD Card present".
The SDCard library is available, but (till now) I can't run it for my boards.
I try to find the position in your prog. where you set or I can change some parameter.
But I see also that there are prefferred slots (card wiring) and none of them hit my wiring.
If you like the JamFunc feel free to use/modify it,
I am be silent in the background (no active repository).
…On 05.05.23 21:59, Jean-Christophe Bos wrote:
Hey, this is really cool! :)
You didn't have the *SDCard* library in your MicroPython port right ?
So here you can actually choose the SPI GPIOs for testing the
particular ESP32 boards.
But indeed, the SD Card menu in the software doesn't work for you I
see, what exact message do you get when you try to activate it from
this page ?
Also, in the information of the "Jama Func", you can put your mail
(see the template) and your site or github in www :)
I could add it to the repository without problem then with an info in
the main readme!
—
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A56V3ZQVJRKL2ADT7TEK2YDXEVLY7ANCNFSM6AAAAAAXXNI5CM>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi @ghvau, in fact, the SD Card part of the program simply uses the default SD Card slot of the ESP32 which works on most boards. However, if you get this error message, it means that the library is indeed supported on your MicroPython and in that case, it should be usable with your boards. You could use it by proposing to configure these options instead of integrating another more restricted library in the Jama Func? At what level did you manage to use this library? (there is the SLOT option which can be important too). It would be a pleasure to add your code :) |
SDCard_var-native.zip Hi @jczic, following your mind, I try the "native" SDCard Class, w/o any additional libs. I thing the native solution is not usable for each board config (exotic card wiring). |
Hello, yes I think it is more logical to use the built-in library and why not test if it's supported during the In fact, if sometimes the configuration crashes the board, it's simply because the selected GPIOSs are already used for something else and that causes a hardware error on the board. Also, slots 0 and 1 are, for the ESP32, the default slots without indication of GPIOs. Only slots 2 and 3 can be set via an SPI interface. Your SD Card test is an excellent idea and actually, does it work well on your exotic cards? |
Hi @jczic, good news for me, when I support Line 1726: ' ___jama["sdCard"] = SDCard(xyz)\n' with the parameter, I used in the above test prog. I have also "full" access to the SDCard via the main function. Tested with the ESP32-CAM board/data. Maybe this is an stimulation for you to make this point also variable. :-) |
Yes, indeed, I had thought to tell you too, I use this variable to keep the instantiation of the SD Card object in memory :) |
jama-func-sd.zip
I have problems the find the right connection data of the "SD Card" function in the main menu.
Therefore I build a "quick and dirty" test for the Jama Funcs with some good segments from github.
Maybe you are interested.
The text was updated successfully, but these errors were encountered: