@Lakshana
Hi,
We have 2 cameras for Spresense now and for both you don't need to change the connector.
Could you please let me know which camera you are using? 1) Spresense HDR camera (new) : https://developer.sony.com/develop/spresense/spresense-hdr-camera-board/
or 2) Spresense original camera: https://developer.sony.com/develop/spresense/specifications
By the way have you reported this on Edge Impulse forum?
https://forum.edgeimpulse.com/

Hey, @sisimonis-5-1-1
Here is a forum post that teaches you how to change stack size using the CLI:

https://forum.developer.sony.com/topic/624/error-in-running-tflite-program/3

Try using 8192 for stack size.

Hey, @sisimonis-5-1-1
I don't believe there is a function exactly for this purpose.
I think you'll have to use memcopy to copy the image from the camera buffer to the input tensor.

Hey, @sisimonis-5-1-1

The thing is.. In the SDK, unless you have ASMP enabled, the default value of RAM size is 1536KB.
You can check if you have the ASMP config enabled and disable that. Or if you need it, then you can control the ASMP shared memory size with the ASMP_MEMSIZE config.

@alfredoz

yaay! I'm so happy for you.
Thank you for sharing your solution.
Might help other developers in the future.

Hey, @RomainPC-0-1-1-1-1-1-1
Let's see if I can answer everything.

It's actually possible to store the application outside of the sdk repository.
Here is a link on how to do that:
https://developer.sony.com/develop/spresense/docs/sdk_set_up_en.html#_add_to_a_different_directory

The flashed kernel is always inside the sdk folder, yes. And it's called nuttx.spk.

About not seeing the Kconfig in the IDE apps:
We don't need a Kconfig file on the IDE because the whole point of this file is that we can see the configurations associated with our example once we open the configuration menu in the CLI.
In the IDE, this configurations are chosen for you by default in the application.mk file.
If you want to change the default values, you can go to your application Makefile and input the values you want. But if you notice, in the bottom of the Makefile of an application created with vscode, you have an include to .vscode/application.mk.

About compilation time:
I don't think the amount of examples have that big of an impact, since going in and out of directories is pretty fast. What I can recommend to improve compilation time in the VSCode IDE is going to .vscode/build.sh and changing adding -j after the make command.

Before:

cd ${SDK_PATH}/sdk make

After:

cd ${SDK_PATH}/sdk make -j

Hey, @Thaïs
Can you post code on how you're trying to read?

Hey, @Kaduwela
Thanks for sharing! 😄

Hello, @herve98-0-1
Try step 0 on this link:
https://www.mac-usb-serial.com/docs/support/troubleshooting.html
"This check is not dependent on any driver, and only verifies if OS X recognizes the device at USB level. If the device doesn’t show up, it is either a broken cable or broken chip."

Some USB cables work for charging but not for data... So I would try with a different cable just to be sure.

Hello, @RomainPC-0-1-1-1-1-1-1
I haven't actually tried it, but you could use git submodule or subtree.
I agree that it would be more interesting to track the folder that contains the applications, so you can create several examples.

Tip:
When you have a successful application, run $make savedefconfig to save the sdk configuration of that application. A defconfig file will appear under the sdk directory and that might be worth saving too.

How would you want to use both CLI and IDE?
The way they do the configuration of the SDK is slightly different and I believe to create an application in the IDE and be able to flash that with the CLI you would need to create the Kconfig file and then take a look at this part of our documentation:
https://developer.sony.com/develop/spresense/docs/sdk_set_up_en.html#_add_to_a_different_directory
(Assuming this is what you want to do)

I tried to disconnect the main board from the extension board and now the main board & extension board turns on. Solution solved! 😃

Hello, @nimish
I haven't found any evidence of compatibility in our documentation or in the CXD56 user manual, which you can find here:

https://www.sony-semicon.co.jp/e/products/smart-sensing/spresense/

Hey, @rauna
If you don't mind, I'll copy the same answer I gave in the Hackster discussion board 🙂

Have you already checked this example? -> https://developer.sony.com/develop/spresense/docs/sdk_tutorials_en.html#_tflmrt_sample_application

There is a note on section 5.1.4. Operation check about using your own model.

Since you have already trained your model, you can skip section 5.1.2. Train a TensorFlow Lite model.

I believe you can use this application, but modify how it processes the output tensor.
This is the code for the application:
https://github.com/sonydevworld/spresense/blob/master/examples/tflmrt_lenet/tflmrt_lenet_main.c

The output tensor is
TfLiteTensor *var = tflm_runtime_output_variable(rt, 0);

Here you can see some helper functions to work with the output tensor:
https://github.com/sonydevworld/spresense/blob/master/sdk/modules/include/tflmrt/runtime.h
Like tflm_runtime_output_num, tflm_runtime_output_shape, tflm_runtime_output_ndim, etc..

Hello, @sisimonis-5-1-1
Thank you for sharing your solution. It might be helpful for other developers in the future.

@RomainPC-0-1-1-1-1-1-1
Thank you for pointing it out!

@mithun
Perfect!
I'm glad to hear that.

Hey, @samasen-0-1-1

The camera example already enables the LCD device, so you don't even need to write that.
tools/config.py examples/camera is enough.

By default, the example uses the extension board. The picture you showed looks like the correct setup to me. Those are the pins I used last time I hooked an LCD display to my spresense board.

Thanks for notifying us, this should be fixed in the next publication.

@Armaghan This is perfect. Thanks!