Hi

You can use "time()" function for this.

Example:
time_t start_time;

void setup() {
Serial.begin(115200);
time(&start_time);
}

void loop() {
time_t cur_time;

sleep(1);
Serial.println(time(&cur_time) - start_time);
}

Best regards,
Kamil

Hi

The best practice is using device drivers. Unfortunately, the current implementation of the userled driver will not work. If you want to use leds you can see how they are used here: https://github.com/sonydevworld/spresense/blob/master/examples/prime/prime_main.c

Best regards,
Kamil

@TE-KarlKomierowski Yes, I'll be posting it to Hackster under the Make It Better contest.

So far it seems to be working as I hoped, although I've still got to figure out some details over the weekend.

yes a good idea to start with low voltages and actually see how it behaves.

as for scaling on the extension board only, that makes sense that the extension board is for Arduino compatibility and the main board is as "pure" as possible.

i was a bit frustrated to find the ADCs are only mapped to the B2B connector of the main board. but i guess there are only so many pins available.

i think the spresense has a lot of potential. i'm developing a few projects with the hope to base them on the spresense main board (but preferably not the extension board, for the sake of cost and simplified design). One is a marine robotics project which currently uses a Raspberry Pi A+ but would be more optimised and reliable using something like the spresense, ( http://robotics.catchpole.net/ - the camera integration, onboard GPS and low power consumption are the main attractions). It's a shame the chip set it only currently available on that board right now. Sony invite requests to purchase the MCU but only for large orders. so maybe the spresense will be used for general ARM cortex development but then actual devices will need to use something else which is more readily available but without as many features. <rant complete>

Hi Kamil,

thank you very much for the work with the Lib. I´ll try it out if there is time. At the moment I´m working on another project.

Best regards,
Daniel

Hi @Vassily98 ,

I think this question was also asked on Stackoverflow, but I will also post a copy of my answer here.
If you try this and run into new problems, please let us know and we can continue to investigate.

To analyze a stack dump the Spresense full SDK provide a tool where you can specify two files as arguments. One is your saved log file, and the other one is the system map file. Doing that you should be able to get the stack trace. If you have build your software with the Arduino IDE you should be able to find where your map file is located in the Arduino IDE log window. Go to File -> Preferences -> Settings -> Show verbose output during and select compilation and when you build your sketch you should be able to find where your build folder is. Normally this folder would be located in /tmp and look something like this:

/tmp/arduino_build_724727/

Fetch the full SDK from github:

git clone --recursive git@github.com:sonydevworld/spresense.git

Change directory to the SDK:

$cd spresense/sdk spresense/sdk$ ./tools/callstack.py -h Usage: python ./tools/callstack.py <System.map> <stackdump.log>

Now just specify the location of your files:

./tools/callstack.py /tmp/arduino_build_724727/output.map dump.log

Hi @timothythomas ,

Great that you are trying out the Spresense board.

To be able to give you assistance on this you would have to provide the source code that you tried to upload to the Spresense board. And also some sort of description of what you think goes wrong. Then we can take a look at it and see if we can reproduce it.

Thank you, BR

The current implementation of the Camera library does not support Camera.takePicture () function within the interrupt service routine (ISR). Kernel panic is expected. Unfortunately, but the same will be with the Spresense SDK.

Hi Felipe,
Each CPU runs on the same clock rate, so cxd56_get_cpu_baseclk() is useful for this purpose. It is placed at sdk/bsp/src/cxd56_clock.c. Each CPU has own SYSTICK.
Best regards,
Kamil Tomaszewski