@TE-KarlKomierowski I joyfully bought the Spresence kit partly because it is open source, open hardware. But I'm disappointed that it is so difficult to get detailed datasheets for Sony image sensors without signing an NDA. I don't want to worry about violating an NDA if I release hardware designs (e.g. an image sensor board) or code (e.g. driver for the image sensor) as open source. And I really don't see what is accomplished by keeping datasheets for released products confidential. Once a product is released, anyone can reverse engineer the pinouts, voltage levels, measure sensitivity, compare with competing products, etc.
Whoever came up with the idea of the open source open hardware Spresence kit - I applaud them. And I wonder if we can prevail upon them to encourage the image sensor division to make their detailed datasheets for released products easily accessible from the company website? For example, at https://www.sony-semicon.co.jp/e/products/IS/industry/product.html
I did manage to find ONE detailed, preliminary, non-confidential datasheet, for the IMX290LQR-C, at https://static6.arrow.com/aropdfconversion/c0c7efde6571c768020a72f59b226308b9669e45/sony_imx290lqr-c_datasheet.pdf . That's incredibly helpful, and if I can find someone to sell me a few of those sensors, I'll try to produce a camera board with that sensor that is compatible with the Spresence kit. And make it open hardware so anyone can make them, and maybe sell a few for a reasonable price if anyone wants them. Having an IMX290 camera board available would make it easier for other developers to use that sensor - which would benefit Sony. So there is a reason why datasheets should be made freely available!
Really, I'd prefer to use the monochrome IMX290LLR, and I'd also like to compare and consider the IMX430LLJ and IMX433LLJ sensors as well. Could I get detailed datasheets for those 3 sensors?
Hi @TE-KarlKomierowski as you said I pressed the SPRESENSE a bit on the extension board and seems the SD card is now working. So the issue was the SPRESENSE was not connected properly on the extension board.
Actually it looks like this developer is saying that the ESP8266-01 won't work with Spresense so he had to use the AdaFruit Feather. I can confirm that I have been able to get my ESP8266-01 module working at one point with Spresense, but for some reason it has completely stopped working. I wonder if my module is damaged somehow even though I am able to connect my module using an adapter board and run simple commands like blinking the lights.
Thanks for the link and advice @TE-KarlKomierowski . I just need to do a quick and dirty demo without burning the Spresense in the process. I won't use those batteries on real deployments because they can easily leak toxic fluids.
Probably I get an error message when I try the git command because the ZIP download already exists. I thougt that the library file wasn't installed.
But the next problem is that the example Sketch audio_scope already gives an error message by compiling it, and I don't have the knowledge to understand the code completely.
Until now I thougt that the Sketch wouldn't work because the required library wasn't available.
I have taken over the Sketch litterally from the Sony Spresense Sample Projects tutorials.
What is here going wrong?
I enabled the DMA option as you suggested, but I did not notice any change to the severity of the flickering. I also checked ILI9340_SPI_MAXFREQUENCY and it was set to 40000000 just as your example.
I agree regarding the NX graphics + framebuffer usage. No sense in re-inventing the wheel. Now that I have discovered a "hook" into the framebuffer, the NX documentation might make a little more sense. I will revisit and research a bit more.
I will definitely keep this thread updated...I also think it is an important dev topic and worth digging into. Stay tuned!