Hi, @jens6151-0-1-1

Sorry for the delayed response.

I was just trying out the sketch here and everything worked well in all three boards (main, extension and LTE)

Using the LTE extension board I changed button 2 to PIN_D29.
To trigger the interrupt I connected it to GND, since we are using INPUT_PULLUP configuration.

So to answer the first question, the pins on the LTE extension board can be used as wakeup pins for cold sleep.
For the second question I think you already fixed it by using your own level shifter, right?

Let me know if you are still struggling with this topic and if I can provide any further help.

Hi @mikhailZ

Sorry it took me so long to answer.

In case you're still interested in this subject, I think the documentation of the start up script on the English page is not up to date.
I'll notify internally so the page can be updated.

On the meantime, I followed the steps on the japanese page and it worked.
I'll summarize here the instructions to automatically run the hello example.

Go to spresense/sdk and run $ ./tools/config.py exemplos/hello feature/startup_script $ make Create a new file in the sdk directory and name it init.rc
In this file write: echo Start up hello script hello Flash the script to spresense using $ ./tools/flash.sh -w init.rc Flash nuttx.spk using $ tools/flash.sh -c /dev/ttyUSB0 nuttx.spk Connect to the board and you should see this: Run /mnt/spif/init.rc. sh [13:100] NuttShell (NSH) NuttX-10.2.0 nsh> hello script Hello, World!!

Hey, @DidierC-3

Sorry to take so long to respond.

How is your project going? Did you solve your issue?

I tried taking a picture with size CAM_IMGSIZE_5M and I also cannot go up to 100% quality.
I can only go up to 90%, which gives me a picture of size 365KB.

I don't know if you're still interested in this topic, but I'm investigating internally and will post any progress in here for future reference.

Hi,

It sounds more like the lens is not compatible.

Hi @CamilaSouza, the issue was exactly how you stated, the SD card was formatted as exFAT32, I only had to go to my computer settings and format it is FAT32. The sample code finally was able to work and capture images while using the Arduino IDE. Although I’m using the Arduino IDE, my preference is VS code, but the camera example still fails to run while using the command “camera” to run it. Perhaps I’ll try another example. Please read through the earlier threads to see whether you’d be able to help resolve this issue. Thank you.

@mag-0
I am able to access pixels using the video stream. I could also convert the format.
Might it be that you try to take large images that do not fit into the 1.5MB memory?

Conversion should be independent of still images or stream because that works on the image object. It might be that initially you can choose only jpeg for the still images though.

If you do that periodically, you can sleep the callback function. With that you can be below the minimum setting of 5 FPS.

@leo-1
Spresense loads the whole program into SRAM. This is how it works. I and others asked similar before.
To my understanding, the issue is that Sony does not open up direct access from the application cores to the flash "because of security issue". There is a "system domain" in between that blocks direct access. So no XIP available.
See for example https://forum.developer.sony.com/topic/698/access-spi-flash-via-memory-map

In my opinion a serious flaw.

Hi Larry,

Using the TFT screen by only the main board is definitely possible. See also here https://forum.developer.sony.com/topic/658/slow-refresh-rate-streaming-the-camera-preview-to-a-display.

But before writing any instructions or hints I would like to have more information.

What environment do you use? Arduino or Spresense SDK? What driver or library do you use? Like Adafruit GFX, TFT_eSPI, NuttX? What is the exact display board? Is it https://www.adafruit.com/product/1743? What is the exact connection? Disclosing the code in use would be very helpful to find issues.

I had it running once with the combination Arduino, TFT_eSPI, ST7789. However it should be no big deal to adapt to other combinations.

Without having further info I guess the pin definition and/or connection has an issue. On the main board you have SPI5.

Hey, @Long-2-4-4-4
You can change the focus manually by rotating the camera lens.
It helps to have a display connected to the board too so you can see the image as the focus is changing.

@mikhailZ

Great news!

short addition.
Input and Output is different in my case.

Sony Hardware declared as of late the arrival of another product improvement unit (SDK) that empowers outsider designers and integrators to ...
Upsides and downsides: Industry-driving self-adjust. Online Shopping has lots of best quality product you should consider it. The SDK is focused on outsider designers and integrators and considers remote admittance to camera boundaries, trigger and live see as well

Hey, @Bhalaji-Kharthik

In the code for that example we can see the following structure for the model:

model = tf.keras.Sequential([ tf.keras.layers.Conv2D(16, kernel_size=(7, 7), strides=(1, 1), activation='relu', input_shape=(28, 28, 1), padding="valid"), tf.keras.layers.MaxPooling2D(pool_size=(2, 2), strides=(2, 2), padding='valid'), tf.keras.layers.Conv2D(30, kernel_size=(3, 3), strides=(1, 1), activation='tanh', padding='valid'), tf.keras.layers.MaxPooling2D(pool_size=(2, 2), strides=(2, 2), padding='valid'), tf.keras.layers.Flatten(), tf.keras.layers.Dense(150, activation='relu'), tf.keras.layers.Dense(10, activation='softmax'), ])

@Benediction-1-2

Regarding the includes, there is a Makefile inside your project file. You can set variables there. You should be able to add include paths. Can you try to add your include path here. Should be something like this.

# C compiler flags CFLAGS = -I/folder/to/include # C++ compiler flags CXXFLAGS =

Difficult to say what is messed up. If it worked before try reverting your latest changes or start over setting up your project. A guess: Did you rename anything?