embedded

What best practices have you used in unit testing embedded software that are peculiar to embedded systems? Embedded software may have come a long way in the last 10 years but we generally did the following: for algorithms that didn't depend on the target hardware, we simply had unit tests that were built and tested on a non-embedded platform. for stuff that did require the hardware, unit tests were conditionally compiled into the code to use whatever hardware was available. In our case, it was a serial port on the target pushing the results to another, more capable, machine where the tests

I have a computer with 1 MB of RAM and no other local storage. I must use it to accept 1 million 8-digit decimal numbers over a TCP connection, sort them, and then send the sorted list out over another TCP connection. The list of numbers may contain duplicates, which I must not discard. The code will be placed in ROM, so I need not subtract the size of my code from the 1 MB. I already have code to drive the Ethernet port and handle TCP/IP connections, and it requires 2 KB for its state data, including a 1 KB buffer via which the code will read and write data. Is there a solution to this

I've written a small program that uses a button on an STM32 Discovery board to act as a counter in either Binary/Decimal/Hexadecimal mode (screen cycles through the 3 options and once pressed, counts up to 16 for each press before resetting to cycling through options). I'm encountering one small "bug" (read, not really) that has me a little confused. If I count up in Decimal/Hexadecimal, it returns to cycling through the options immediately but if I have counted up in Binary it takes ~1sec or so before doing so (a noticeable delay). int main(void) { RCC_APB1PeriphClockCmd(RCC_APB1Periph_TIM6,

I would like to monitor the the context switching behavior in a multi-threaded pthread application. In other RTOSes(Micro C OS) I have been able to register a context switch callback for each thread in the application, and then log (or toggle a gpio) and watch the thread context switching in real time. This was a valuable tool for debugging the real time behavior and interaction of the multiple threads. My current environment is embedded linux utilizing the pthread api. Is there a way to monitor each of the context switches? Not in the way you describe, however there are various profiling

一、开发环境的构建 1.下载Qt源代码，包括桌面版和嵌入式版 如4.7.4版：qt-everywhere-opensource-src-4.7.4.tar.gz qt-everywhere-opensource-src-4.7.4[embedded].tar.gz 解压缩到当前目录：tar -xzvf qt-everywhere-opensource-src-4.7.4.tar.gz 2.编译安装桌面版和嵌入式版 桌面版一般为默认配置安装：./configure ; sudo make; sudo make install; 嵌入式版安装作为开发用，也一般可以为默认安装，但必须指定目标类型与主机类型 (1) 首先需要指定目标类型，利用现有的或者修改、添加目标类型 a.进入mkspecs/qws/文件夹中：cd mkspecs/qws b.找到你的目标类型文件夹并且拷贝一份：cp linux-arm-g++ linux-omapl138-g++ -a c.进入你的目标文件夹中以修改qmake.conf配置文件，主要是修改交叉编译器： cd linux-omapl138-g++;gedit qmake.conf 修改文件中的如下内容以符合你的交叉开发环境： # modifications to g++.conf QMAKE_CC = arm-none-linux-gnueabi-gcc