embedded

I am learning embedded development on the STM3220G-EVAL board with the STM32F207 microcontroller. I have tried to test the I2C interface by interfacing the two I2C2 and I2C3 modules on the same chip and sending/receiving a character. Here is the code I have currently written (using mdk-arm 5): #include <stm32f2xx.h> volatile uint8_t data = 'a', recv = 'x'; void i2c_init(void); void I2C2_EV_IRQHandler(void) { volatile uint16_t stat, dummy; stat = I2C2->SR1; switch(stat) { // SB set; read SR1 and write slave address in DR to clear case 0x01: dummy = I2C2->SR1; // Send address of slave I2C2->DR =

I want to use XCode as an IDE for developing some AVR code. I did the following 1) create new project 2) select external build system 3) indicated i want it to be make, and told it NOT to "Pass build settings in environment" 4) copied my .c/ .h/Makefile into the same directory i created the project in 5) added the .c/ .h files to the project/target 6) verified that i can build (make) from both command line and Xcode But I cannot use any of the refactor menu options, or jump to/reveal options. There appears to be no symbol information. Is there no way to use Xcode as more than just a simple C

I’ve just cross-compiled QT 5.2.1 for ARM and I am using it on a TI AM335x EVM (Starter Kit) board. I’de like to use the eglfs platform, but unluckily it shows some artifacts on the screen… I just made a simple program for showing the problem and captured some photos of my screen. The program basically draws a set of vertical black and white lines (alternated). If I run QT on platform linuxfb (that is I launch my program passing “-platform linuxfb” on command line) then the software works fine… Here is a photo of my screen: If instead I run QT on platform eglfs (that is I launch my program

I am looking for a high performance logging library that I will use on an embedded device. I also want to say that I previously used PaulBunyan logging library which provided an efficient method for transferring information. [By efficient I meant it had a solution for transferring only the __LINE__ and __FILE__ when sending data through a low speed interface (SERIAL for example) - of course a __LINE__ __FILE__ mapping was previously made by scanning the code]. Do you know such solutions or at least similar ones? Thanks in advance for any pointers/similar solutions, Iulian The decision is to

In my embedded project am using JTAG interface to download the code and to debug the downloaded application.But i don't know what is happening inside the JTAG set up. Can anyone please give me basic idea/flow(high level view) of the JTAG set up wich will really help me to understand my development system better. __Kanu To add to Cliffords answer, there are some pictures here: http://www.fpga4fun.com/JTAG2.html The tap controller state machine is something you will see published ad nauseum. It is really the key to JTAG. As Clifford said you access on chip debug registers. The tap controller

I am working on a Qt application running on embedded Linux. I am pretty new to this Qt business since I have just started it a month back, so understand that I'm not that object-oriented ... :P I have the Qt applications running on my target running Linux. The Qt documentation http://doc.qt.io/archives/qt-4.7/qt-embedded-pointer.html says that we have to enable touchscreen, USB keyboard, keypad, etc. by exporting certain variables. Namely, export QWS_MOUSE_PROTO=tslib:/dev/input/event1 export QWS_KEYBOARD="linuxinput:/dev/input/event0 usb:/dev/input/event2" well, as you can guess, first line

I am using an STM32 micrcocontroller to interface an SD card memory using the SPI peripheral. I have done tests with 2Gb , 4Gb , 8Gb and 16Gb SanDisk cards. When I perform a reset with the 2Gb and 8Gb cards , nothing happens and I keep going with my tests. However, with 4Gb and 16Gb , once the reset is performed intialization fails . In fact , at the first insert in the SD slot , these cards are quite good initialized but one I perform the reset it does'nt pass. When I tried to debug this problem, I discovered that when dealing a reset the response to command CMD0 is wrong . I get 0x00 instead