Writing to SDcard is possible with keil but not with embedded studio

RE: Writing to SDcard is possible with keil but not with embedded studio

awneil — Fri, 14 Jun 2019 07:36:27 GMT

Well done for finding it, and thanks for sharing the solution!

[quote userid="73638" url="~/f/nordic-q-a/48380/writing-to-sdcard-is-possible-with-keil-but-not-with-embedded-studio/192810"]fprintf was used to convert binary data to float[/quote]

You mean, convert float data to text ?

Yes, the handling of floating-point would be an area where toolsets differ - and whether it is enabled or not by default, and how to enable/configure it.

RE: Writing to SDcard is possible with keil but not with embedded studio

y001 — Fri, 14 Jun 2019 01:33:50 GMT

I understand the cause
When writing to SDcard, fprintf was used to convert binary data to float, which was a problem.
When I converted what was converted by% lf with fprintf to% d and made it an int type, I was able to write for the time being, so it will be a solution.

RE: Writing to SDcard is possible with keil but not with embedded studio

y001 — Fri, 14 Jun 2019 00:40:59 GMT

I looked at the signal line with an oscilloscope.
If you are able to write to the keil SD card, the SCK line was a clean square wave.
However, if you can not write to the SES SD card, it is thought that you can not write well because the SCK line has become trapezoidal. Why is this difference in the same code?

RE: Writing to SDcard is possible with keil but not with embedded studio

Jørgen Holmefjord — Thu, 13 Jun 2019 12:46:22 GMT

I just tested fatfs example from SDK 15.3.0. Bot SES and Keil work as expected. Please check your connection, or test with a different card.

RE: Writing to SDcard is possible with keil but not with embedded studio

awneil — Thu, 13 Jun 2019 08:58:35 GMT

[quote userid="73638" url="~/f/nordic-q-a/48380/writing-to-sdcard-is-possible-with-keil-but-not-with-embedded-studio/192526"]SPI is not working properly[/quote]

What, exactly, is "not working" ?

http://www.catb.org/esr/faqs/smart-questions.html#code

Again, have you looked at the SPI lines on an analyser or oscilloscope?

Have you compared the working & non-working versions - both within the software, and looking at the hardware - to find where they diverge?

[quote userid="73638" url="~/f/nordic-q-a/48380/writing-to-sdcard-is-possible-with-keil-but-not-with-embedded-studio/192526"]only one version of SDK can be used per chip[/quote]

The chip can only run 1 executable at a time.

An executable can only be built from 1 SDK.

RE: Writing to SDcard is possible with keil but not with embedded studio

y001 — Thu, 13 Jun 2019 02:03:20 GMT

Thank you for reply,jorgen!

Yes. I am using fatfs_example of SDK 15.0.0 as a sample to write to the SD card.
It works fine with keil, but not with SES.
In SES, there are no errors or warnings at compile time, but you can see that it is not working properly if executed.
Although BLE and nrf_gpio_pin_set () etc are working normally, only SPI is not working properly in SES.

I have a question here,
I have already edited the fatfs in SDK 15.0.0, so I downloaded SDK 15.3.0 to run the unedited sample in SES.
However, the fatfs of SDK 15.3.0 could not be run with keil. Are there any restrictions that only one version of SDK can be used per chip?

RE: Writing to SDcard is possible with keil but not with embedded studio

awneil — Wed, 12 Jun 2019 08:45:34 GMT

[quote userid="73638" url="~/f/nordic-q-a/48380/writing-to-sdcard-is-possible-with-keil-but-not-with-embedded-studio/192234"]I do not know the cause of this[/quote]

You need to find the cause - that's what debugging is all about!

Again:

[quote userid="6462" url="~/f/nordic-q-a/48380/writing-to-sdcard-is-possible-with-keil-but-not-with-embedded-studio/191800"]The thing to do is to use the debuggers in both tools to examine what is happening in the working case, and see where the non-working case diverges[/quote]

And:

[quote userid="6462" url="~/f/nordic-q-a/48380/writing-to-sdcard-is-possible-with-keil-but-not-with-embedded-studio/191800"]use an analyser or oscilloscope on the interface lines - again, examine what is happening in the working case, and see where the non-working case diverges[/quote]

(can't get the stupid forum to do that in a single quote)

Debugging is a key part of software development - and, in fact, any kind of development!

How To Debug

RE: Writing to SDcard is possible with keil but not with embedded studio

Jørgen Holmefjord — Wed, 12 Jun 2019 07:57:58 GMT

[quote userid="73638" url="~/f/nordic-q-a/48380/writing-to-sdcard-is-possible-with-keil-but-not-with-embedded-studio/192196"]fatfs only example[/quote]

Do you mean the SD Card Example from the SDK? If you get errors building this in SES, you should try with a fresh copy of the SDK, to make sure you did not modify anything.

If you are still not able to write the SD card, please check the connections, or test with a different card. Are you using an SD card socket board? If you are, please make sure it does not contain a 5 V level shifter.

RE: Writing to SDcard is possible with keil but not with embedded studio

y001 — Wed, 12 Jun 2019 07:49:03 GMT

I was able to compile the fatfs example in Embedded studio, but running it did not write numbers to the SD card.
Blanks were written instead of numbers.
I do not know the cause of this
Help me...

RE: Writing to SDcard is possible with keil but not with embedded studio

y001 — Wed, 12 Jun 2019 04:20:33 GMT

Thank you for reply.

I will try to find out the cause.

I tried to try the fatfs only example in Embedded studio.
"L6218E: Undefined symbol __initial_sp (referred from entry2.o)"
And could not be built successfully.
I do not know the cause of this either.

RE: Writing to SDcard is possible with keil but not with embedded studio

awneil — Mon, 10 Jun 2019 09:46:58 GMT

Both Keil & SES are just IDEs with associated toolchains - they are both perfectly capable of generating working code for their intended Targets.

However, they are entirely different toolchains - so the generated code will not be identical.

The 3 top suspects would be:

Your SES configuration;
Some (possibly subtle) timing differences;
Some flaw in your code which happens not to show (yet) any visible symptoms in Keil, but does in SES.

The thing to do is to use the debuggers in both tools to examine what is happening in the working case, and see where the non-working case diverges.

Also use an analyser or oscilloscope on the interface lines - again, examine what is happening in the working case, and see where the non-working case diverges.

EDIT

Have you tried using some unmodified SES examples from the SDK - to get you familiar with the setup, and give you a known-working basis to work from ?