I’ve used the following commands for cross-compilation on ubuntu to run simple.s but am getting an error The commands are: I tried to obtain the binary’s architecture by and my machine’s architecture by and found that they were different. I believe getting the right binary for the architecture will solve the problem. Is that true? Here is simple.s How can
Tag: arm
Error while cross-compiling chromium for ARM from x_64
I am trying to build chromium from source code following instructions at https://chromium.googlesource.com/chromium/src/+/master/docs/linux/build_instructions.md I have successfully built and tested chromium for amd device, Now I am trying to cross-compile it for arm device, However when I set the flag target_cpu = “arm” using gn gen out/Debug –args=’target_cpu=”arm”‘ I get the following error Any leads would be appreciated Answer I have
How are memory regions on ARM Cortex A denoted as “device” or “strongly ordered” under Linux
On the ARM Cortex-A9 that comprises part of the Zynq SoC I’m using, regions of memory are labelled as “normal”, “device” or “strongly ordered”. This is described in the Zynq technical reference manual, but I understand it is a property of ARMs more generally. Obviously, the ability to have strongly ordered memory accesses for memory mapped devices (which includes many
Using perf_event with the ARM PMU inside gem5
I know that the ARM PMU is partially implemented, thanks to the gem5 source code and some publications. I have a binary which uses perf_event to access the PMU on a Linux-based OS, under an ARM processor. Could it use perf_event inside a gem5 full-system simulation with a Linux kernel, under the ARM ISA? So far, I haven’t found the
Linker –whole-archive option
I am using C language. I am linking static libraries with –whole-archive. Linker is arm-none-eabi-ld For example, giving the following option to the linker: But still I get linking error: Why is the linking error happening? EDIT: Full command with output: Out put of: readelf -Ws kunit.a hal.a fs.a | egrep ‘ (mmu_init|exec_array|mmu_pagetable|_enter_kernel)’ is: Answer Why is the linking error
Why is the pthread_mutex_t struct all zeros in gdb?
What causes pthread_mutex_t struct to be all zeros? Core of a deadlocked ARM test application in a gdb session: Answer pthread_mutex_t is used for all mutex types and some of its members are only used for specific mutex types. owner member is set for at least the following mutex types: PTHREAD_MUTEX_ERRORCHECK_NP PTHREAD_MUTEX_RECURSIVE_NP See glibc implementation of pthread_mutex_trylock for full more
gdb can’t cross-compile for arm-linux
The Linux already having both gcc & arm-gcc in the environment path: So I configure the gdb 6.6: compiled without error, but looks like gdb used the wrong compiler. So How to indicate the correct CC for gdb? I tried make CC=arm-none-linux-gnueabi-gcc, but will get the error: Answer Don’t use –target. It means something else to Autotools. Use –build and
Interpreting basic ARM instructions
I have been a set few questions, one of them is: Which of these ARM instructions clears register r5, so that all of it’s bits are set to ’0’? From my understanding sub r5, r5, r5 clears the register as it subtracts the number from itself. The and and eor ones clearly look wrong. Does the lsr r5, #32 also
Segmentation fault when maping /dev/mem
I’m trying to mmap a memory from my FPGA on a linux running on my Zedboard SoC. I can read the contents correctly using devmem on the command line, but when trying to read it through C I get a segmentation fault. The barebones code shown below throws the segmentation fault when trying to print the contents of the memory.
ARM GDB cannot access memory only on Linux
Trying to switch development to Linux, but running into a (probably simple newbie) problem. On my Mac, I can use ARM GDB (arm-eabi-none-gdb from the GNU ARM Embedded Toolchain) to load my elf to my STM32L432, then at my breakpoints a simple i lo (or examine, or whatever) gives me the local vars. On Linux, however, the exact same code