embedded

I am working on a group senior project for my university and I have run into a major hurdle in trying to get my code to work. The compiler that we have for our 8 bit Atmel microcontroller does not support the new or delete operators, and it does not support the C++ STL. I could program it in C, but I have to implement an A* algorithm which I have never done before. While I have tried C initially I soon realized that I never did pure C before. Trying to model objects with structs and functions is slowing me down since I am so used to the much cleaner C++ syntax. Regardless, the exact wording

What are some techniques in detecting/debugging memory leak if you don't have trace tools? Intercept all functions that allocate and deallocate memory (depending on the platform, the list may look like: malloc, calloc, realloc, strdup, getcwd, free), and in addition to performing what these functions originally do, save information about the calls somewhere, in a dynamically growing global array probably, protected by synchronization primitives for multithreaded programs. This information may include function name, amount of memory requested, address of the successfully allocated block, stack

QtCreator has a plugin named "Bare Metal". Bare Metal means a computer without an operating system. I have not seen much about Qt Bare Metal development. Is it a way to develop Qt for a bare metal system? Does Qt run on a system with no OS? If yes, what are the advantages of this approach for embedded system development? Is it a way to develop Qt for a bare metal system? No. Does Qt run on a system with no OS? No. Bare Metal means you usually have a few KB of RAM and ROM. I think you are confusing Qt (framework) with QtCreator (IDE). Tim Sander explains it clearly here at the Qt Developer Days

I have build the GCC4.7.1 cross-toolchain for ARM (cortex-m3). Now I'm linking an executable from C/C++ code that surely doesn't use some certain STL classes (e.g. std::string ). Furthermore exceptions and RTTI are turned off. Though when I'm looking to the target ELF (e.g. using nm), there's a lot of symbols (apparantly from the libstdc++) linked in I wouldn't expect to find there (e.g. std::exception , std::ios_base , etc.). Why is this there, and how can I get rid of this stuff to reduce the .text section size of my target? A coworker gave me a tip to override some GCC specific stub

I am looking for tools and techniques for prototyping (virtual prototyping), simulation, and testing of deeply embedded C code on desktop Windows, including building realistic embedded front panels consisting of buttons, LEDs, and LCD displays (both segmented and graphic). I'm specifically interested in a possibly low-level approach, using pure C code and raw Win32 API rather than MFC, .NET/C#, vxWidgets or Qt. I'd also like to use free development tools, such as Visual C++ Express with Platform SDK and ResEdit for editing resources. I'm looking for code examples to render graphic LCDs (from

I am novice in process/task management. I would like to schedule two tasks. suppose, fun1() { printf("It will be printed in every 1 min \n"); } fun2() { printf("It will be printed in every 2 min \n"); } main() { fun1(); fun2(); } So how to schedule them, so that I will get my desired output. I want it to run in Code::Blocks (Windows). I want fun1 to run 1 min and fun2 to run every 2 mins. If I can do it in two separate process also then tell me how can I do it. Do I need to use semaphore, mutex and all? Your example is trivial and can be scheduled without resorting to any OS provided

This question is related to diagraming a software process. As an electrical engineer, much of the software I do is for embedded micro-controllers. In school, we learned to illustrate our algorithm using a flowchart. However, nowadays, many of my embedded projects are heavily interrupt-driven where the main process runs some basic algorithm a variety of interrupt sources provide its stimulus. So, my question is, what are some diagramming techniques that I can use to illustrate my process such that future developers can understand what I am doing easily and get involved in development? Here are