embedded

Can anyone please let me know what are the possible ways in which we can store a function(in C) at a fixed memory location. I am using IAR IDE for ARM cortex m3 core. How functions and data can be placed in memory is described in section "Controlling data and function placement in memory" of the IAR manual "IAR C/C++ Development Guide". The only way I see to place a specific function at a specific address is to define a section in memory where to place this and only this function. Example: void MyFunction( void ) @ "MyFunctionsSection" { ... } In the linker file you have to define the section

I'm working on an embedded c project and am having issues with global variable redefinition. I've split up the function declarations and definitions into a handful of .h and .c files. Many of these functions need access to global variables, which are defined in global_vars.h. Therefore, at the beginning of the header files, inside the #ifndef, #define section, "global_vars.h". If I don't, as you might imagine I get a bunch of undefined variable errors. However, even though global_vars.h has the #ifndef _GLOBAL_VARS_H_ #define... #endif, I get redefinition errors for all the global variables.

I am very new to embedded system programming, I just need to learn how to manipulate the given via c++ code. Given: Motor 1 is mapped to 0x60000000 Motor 2 is mapped to 0x50000000 the following are the definitions of current 32-bit registers REGISTER NAME | BYTE OFFSET | NOTES ---------------------------------------------------------------------- motor_interrupt 0x00 service interrupts motor_status 0x01 enable on demand access to status elements motor_command 0x02 enable command of the motor REGISTER NAME | NAME | BITS | ACCESS TYPE | DESC ------------------------------------------------------

What is Super Loop in Embedded C programming language? This refers to the eternal loop usually located in main() of a "bare metal" system (no OS), since such systems can never return from main. A typical bare metal embedded system looks like this: void main (void) { // various initializations for(;;) // "super loop" or "main loop" { // do stuff } } MCU is device which runs continuously or better, it executes instructions when power is on (in general). So while loop is here to force MCU to do something, even if loop is empty, it will just circle around. But it must do something as it is not the

Could someone explain me what is going on within the Contiki-OS when it transmits an UDP packet? Here is the current consumption of my device in details running with the CC2538 chip: My question is: why it takes so long to transmit an UDP broadcast packet (about 250ms) knowing that theoretically at 250kbps the packet of 408 bits length should be transmitted in approximately 2ms? I'd understand if the transmission last lets say ten milliseconds but here the difference is huge. I use the example in contiki/examples/ipv6/simple-udp-rpl/broadcast-example.c Does anyone have an idea? By default,

I'm trying to connect to an embedded device through ssh . However, when trying to connect, I always get a connection refused message even when I try changing the port number. I've tried everything to resolve this issue, from changing the file in /etc/ssh/ to accept the specific port number, to sudo iptables -A INPUT -p tcp --dport ssh -j ACCEPT . After reading some comments, it came to me that maybe one of the problems is that I don't have ssh installed on my embedded device. So, how do I infact install ssh on an embedded device? I'm working with a FOX G20 V board with an ATMEL AT91SAM9G20. I