embedded

Here i want to know about strcpy() and strcat() disadvantages i want to know about these functions danger area in embedded domain/environment. somebody told me we never use strcpy,strcat and strlen functions in embedded domain because its end with null and sometimes we works on encrypted data and null character comes so we cant got actual result because these functions stop on null character. So i want to know all things and other alternative of these functions. how we can use other alternatives functions The str* functions works with strings. If you are dealing with strings, they're fine to

I need to compute the mathematical expression floor(ln(u)/ln(1-p)) for 0 < u < 1 and 0 < p < 1 in C on an embedded processor with no floating point arithmetics and no ln function. The result is a positive integer. I know about the limit cases (p=0), I'll deal with them later... I imagine that the solution involves having u and p range over 0..UINT16_MAX , and appeal to a lookup table for the logarithm, but I cannot figure out how exactly: what does the lookup table map to? The result needs not be 100% exact, approximations are OK. Thanks! Since the logarithm is used in both dividend and

I'm new to the software engineering side of C development; does anyone have a good guide on how to design an error tracking or error control system for a C project (especially embedded)? Something talking about error tracking for C libraries would be helpful too. In my experience the strategies here fall into a few camps. Use of global variables ala errno . How this works is essentially any function can store an error code in the global variable, so after executing the function you can read the error code to see if it executed properly. There are some obvious issues here when working in a

I've got a project and a part of it is incorporating encryption into a FAT file system. The goal of the project is not the encryption, so I'm free to use open-source pre-done libraries. Ideally what I'm after is a C library which uses RSA, that already has the methods for computing keys and encrypting/decrypting files. You might want to check out NaCl (pronounced as "salt"), especially since this is for an embedded system. It has CPU-specific tunings and doesn't require any dynamic memory allocation. As for licensing, the page (linked above) says "All of the NaCl software is in the public