embedded

I have a strange problem that I can't solve. Please help! The program is a multithreaded c++ application that runs on ARM Linux machine. Recently I began testing it for the long runs and sometimes it crashes after 1-2 days like so: *** glibc detected ** /root/client/my_program: free(): invalid pointer: 0x002a9408 *** When I open core dump I see that the main thread it seems has a corrupt stack: all I can see is infinite abort() calls. GNU gdb (GDB) 7.3 ... This GDB was configured as "--host=i686 --target=arm-linux". [New LWP 706] [New LWP 700] [New LWP 702] [New LWP 703] [New LWP 704] [New LWP

I would create a python script that decode a Base64 string to an array of byte (or array of Hex values). The embedded side of my project is a micro controller that creates a base64 string starting from raw byte. The string contains some no-printable characters (for this reason I choose base64 encoding). On the Pc side I need to decode the the base64 string and recover the original raw bytes. My script uses python 2.7 and the base64 library: base64Packet = raw_input('Base64 stream:') packet = base64.b64decode(base64Packet ) sys.stdout.write("Decoded packet: %s"%packet) The resulting string is a

I have three fonts i want to use in my software: FontA: contains Latin, Greek, Cryllic characters FontB: contains Korean characters FontC: contains Japanese, Chinese characters These fonts have no overlap. I want to setup my application such that all of these fonts are used at once since characters from different languages may appear in the same context in my software. If a character is found in FontA, use it. Otherwise, look at FontB, if found use it. Look at FontC as last resort, if found, use it, otherwise do nothing. How can i setup Qt to function that way? (My environment is embedded

I am working on an embedded application that uses NAND flash for storage. As it looks now, we won't use Linux or any other RTOS. The application must handle unexpected power downs. We have been looking on different file system solutions, including YAFFS2, JFFS2, FAT+FTL as well as solutions from HCC Embedded . I have heard FAT+FTL is a normal choice, but I am worried about data loss in case of unexpected power downs as well as performance. Would be grateful if anyone could share insights and experience about this FAT-FTL is a "normal choice", but not necessarily a good choice. YAFFS2 is newer

I have an application that I am porting from the Keil IDE to build with the GNU toolchain due to license issues. I have successfully be able to set up, build, flash and run the application on the device. The application on the GNU side is for some reason is getting stuck in the weak linked IRQ handler for the WWDG which is an infinite loop. The application does not enable the WWDG, and it is disabled at reset by default. I have also verified that the configuration registers are at their default startup values. The only difference, other than compilers, are the linker and startup files. However