Ismail: could you please post more of your code, especially the definition
of buffer? Also, do you have the word "float" in your call to stostrf, or
were you just letting us know that "number" is a float? The type of
"number" should not be in the call to dtostrf(). From some forum posts, it
loo
They may be different under the hood and have subtly different meanings,
but both work in Linux GCC and AVR-GCC without the __flash qualifier. I've
seen these statements used interchangeably in Linux C code, for instance.
The relevant question is, what is the behavior of __flash that causes one
t
What you're looking for is a hex editor. Three are countless programs that
will do the job. Use your favorite search engine to search for "hex editor
for Linux" or whatever other OS you're running, and that should get you
started.
Good luck,
~James
On Feb 3, 2014 12:30 AM, "dfx" wrote:
> Hi,
>
That particular #define is one of many that is set by the compiler. That
one is based on the architecture you selected in the "-mmcu" option to GCC.
In GCC, you can see all of the macros defined by using the "-dM -E"
options. For example, this will show you everything the compiler is adding
befo
Something like this:
void compute(char *a, int aLen) { // could also be "unsigned int aLen"
if (a == NULL || aLen < 1) {
// error
return;
}
a[0] = 'A';
// make sure to check the length of the array before referencing deeper
into it
...
...
}
char arr[20];
compute(arr, 20);
