embedded

问题 There are really two questions that revolve around the use of --add-section. The simple one is in the title. Based on my reading, I haven't been able to figure out how one could execute --add-section. To use add-section, I have to pass a section name. If I use an existing section name the program responds with "can't add section '.data': File in wrong format." Perhaps I just need to pass another parameter. If I use a new section name, which I would prefer to do, I'm warned that "allocated

问题 There are really two questions that revolve around the use of --add-section. The simple one is in the title. Based on my reading, I haven't been able to figure out how one could execute --add-section. To use add-section, I have to pass a section name. If I use an existing section name the program responds with "can't add section '.data': File in wrong format." Perhaps I just need to pass another parameter. If I use a new section name, which I would prefer to do, I'm warned that "allocated

问题 I stumbled upon very strange issue with GCC. The issue is 25% drop in performance. Here is the story. I have a pice of software which is fp32 compute intensive (neural networks compiled with TVM). I compile it for ARM (rk3399 device), here is info: gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/5/lto-wrapper Target: arm-linux-gnueabihf Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.12' --with-bugurl

问题 I stumbled upon very strange issue with GCC. The issue is 25% drop in performance. Here is the story. I have a pice of software which is fp32 compute intensive (neural networks compiled with TVM). I compile it for ARM (rk3399 device), here is info: gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/5/lto-wrapper Target: arm-linux-gnueabihf Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.12' --with-bugurl

问题 I stumbled upon very strange issue with GCC. The issue is 25% drop in performance. Here is the story. I have a pice of software which is fp32 compute intensive (neural networks compiled with TVM). I compile it for ARM (rk3399 device), here is info: gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/5/lto-wrapper Target: arm-linux-gnueabihf Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.12' --with-bugurl

问题 I am building an embedded linux distro on a Beaglebone Black (AM335x chip Cortex-A8 Arm-v7 Instruction set) using crosstool-NG, U-Boot, Kernel (5.5.5) and buildroot. When compiling the kernel I am getting this error message: /tmp/ccxFZlyN.s: Assembler messages: /tmp/ccxFZlyN.s:39: Error: selected processor does not support `isb ' in ARM mode /tmp/ccxFZlyN.s:90: Error: selected processor does not support `isb ' in ARM mode /tmp/ccxFZlyN.s:371: Error: selected processor does not support `isb '

问题 I am working with STM32F103C8T6 and would like to use CMSIS, which is essentially just register definitions and no code, to make my life easier while still staying at a low level. The problem is that I have no idea how to install the library for use on the command line with Makefile. All documentation seems to be bound with a vendor-specific IDE like STM32CubeIDE. I suppose the first thing to do is to download the CMSIS library, which I found on GitHub. However, after unzipping ARM.CMSIS.5.6

问题 I have written a Linux Loadable Kernel Module which attempts to attach to the FIQ to service GPIO edge transistions. The Pin in question is on GPIO0 (IRQ 49) so I attempt to configure the FIQ as follows: #ifndef GPIO_BASE #define GPIO_BASE 0x7E200000 #endif #define GPIO_LEN 0x60 #define GPIO_GPEDS0 0x10 #define GPIO_GPEDS1 0x11 #define GPIO_GPREN0 0x13 #define GPIO_GPREN1 0x14 #define GPIO_GPFEN0 0x16 #define GPIO_GPFEN1 0x17 #define AIR_BASE 0x7E00B200 #define AIR_LEN 0x28 #define AIR_IP2 2

问题 I'm struggling to properly implement printf from newlib into my esp32, using GCC. I've gone through the newlib documentation and it gives me general information about how printf is called, but doesn't explain the back end implementation to me. Based on my current research I have determined that printf outputs a formatted string to the STDOUT. On a PC this was simpler for me to understand because there's a console window that would display the formatted output from printf, however on an

问题 I'm struggling to properly implement printf from newlib into my esp32, using GCC. I've gone through the newlib documentation and it gives me general information about how printf is called, but doesn't explain the back end implementation to me. Based on my current research I have determined that printf outputs a formatted string to the STDOUT. On a PC this was simpler for me to understand because there's a console window that would display the formatted output from printf, however on an