CodeSourcery | ZYNQ交叉编译工具链
kandi X-RAY | CodeSourcery Summary
kandi X-RAY | CodeSourcery Summary
CodeSourcery
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of CodeSourcery
CodeSourcery Key Features
CodeSourcery Examples and Code Snippets
Community Discussions
Trending Discussions on CodeSourcery
QUESTION
I have downloaded the kernel source of my Samsung Galaxy Tab A 2018 (SM-T590) from Samsung Open Source website.
I'm trying to compile the unmodified source code using the instructions given with the kernel inside the archive, however the resulting kernel file is ~28MB, while the one which can be extracted from the stock ROM's boot.img is ~13MB.
Of course, the 28MB large compiled kernel won't boot the system up, when I select reboot to system in the recovery, it goes back to download mode.
Steps I have followed:
...ANSWER
Answered 2020-Dec-09 at 11:45Solved.
Basically the stock kernel inside boot.img is a compressed archive containing the kernel itself, that's why it was a different size.
QUESTION
I'm trying create an u-boot image file. But have i have some error.
...ANSWER
Answered 2020-Jun-19 at 12:23Your PATH is pointing to some 2011 GCC cross compiler. You need at least GCC 6 which was released in 2016. Please, install a current release of GCC.
On Debian or Ubuntu the C compiler for the host system and the cross compiler are separate packages. You can install the cross-compiler for 32bit and 64bit ARM with:
QUESTION
I am building a custom kernel using Buildroot 2020.02.1 for a PC mounting a AMD GX-222GC SOC.
The default external toolchain is amd-2016.11-19 from CodeBench. Kernel built with that toolchain boots correctly. Instead, if I build the same kernel, same configuration, with the toolchain automatically built by buildroot, the kernel doen not boot! Not even a kernel panic, machine just resets.
It is clear the problem is related to the toolchain.
These are the results of gcc -v
CodeBench:
...ANSWER
Answered 2020-Apr-27 at 19:07The early 4.4.x kernels do not boot when built with binutils >= 2.31. This was fixed in commit https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=073bb7ddd35ca8f17a170258dacbe384935a43c8 in the 4.4.x stable branch, which was merged in 4.4.124. So any 4.4.x earlier than that, when built with binutils >= 2.31, will not boot.
QUESTION
Before I get started. Yes, I could use leJOS, ev3dev, or some others, but I'd like to do it this way because that is how I learn.
I am using the CodeSourcery arm-2009q1 arm toolchain. I fetched the required libraries (bluetooth) from here: https://github.com/mindboards/ev3sources. I am uploading the programs to the brick by using this tool: https://github.com/c4ev3/ev3duder
I have also fetched the brick's shared libraries, but I can not get them to work properly and there is 0 documentation on how to write a c program for the ev3 using the shared libraries. If I could get that working I might be able to use the c_com module to handle bluetooth, but right now bluez and rfcomm in conjunction with: https://github.com/c4ev3/EV3-API for motor and sensor control seems to be my best bet.
Now, with that out of the way: I'd like to run the EV3 as a bluetooth "server" meaning that I start a program on it and the program opens a socket, binds it, listens for a connection, and then accepts a single connection. I am able to do open a socket, bind it to anything but channel 1 (I believe this might be the crux of my issue), I am able to listen. These all return 0 (OK) and everything is fine.
Then I try to accept a connection. That instantly returns -1 and sets the remote to address 00:00:00:00:00:00.
My code is pretty much the same as can be found here: https://people.csail.mit.edu/albert/bluez-intro/x502.html
Here it is:
...ANSWER
Answered 2019-Oct-10 at 14:10I figured it out. On my raspberry PI, the accept call worked as expected with no quirks. On the EV3 however, the accept call is non-blocking even if it has not been told to act like so. The solution was to place the accept call in a loop until an incoming connection was in the queue.
QUESTION
I'm creating driver for communication with FPGA under Linux. FPGA is connected via GPMC interface. When I tested read/write from driver context - everithing works perfectly. But the problem is that I need to read some address on interrupt. So I created interrupt handler, registred it and put iomemory reading in it (readw function). But when interrupt is fired - only zero's are readed. I tested every part of driver from the top to the bottom and it seems like the problem is in iomemory access inside ISR. When I replaced io access with constant value - it successfully passed to user-level application.
ARM version: armv7a (Cortex ARM-A8 (DM3730))
Compiler: CodeSourcery 2014.05
Here is some code from driver which represents performed actions:
...ANSWER
Answered 2019-Feb-12 at 08:23Looks like the problem was in code optimizations. I changed uni_RB_write function to pass physical address and data size, also read now performed via ioread16_rep function. So now everything works just fine.
QUESTION
The Linux already having both gcc
& arm-gcc
in the environment path:
ANSWER
Answered 2019-Feb-01 at 03:03QUESTION
I am trying to build rt5370 driver for my embedded board. I downloaded "DPO_RT5572_LinuxSTA_2.6.1.3_20121022.tar.bz2". First, I exeuted a make without any modification. So, the size of rt5370sta.ko is 942,330 bytes.
And I added my configurations arm-none-linux-gnueabi-, kernel directory.
In ./Makefile
PLATFORM = ARMV7 ifeq ($(PLATFORM),ARMV7) LINUX_SRC = /home/gykim/working/s1cam/bsp/linux/kernel CROSS_COMPILE = /opt/armv7/codesourcery/bin/arm-none-linux-gnueabi- endif
In ./os/linux/config.mk
ifeq ($(PLATFORM),ARMV7) EXTRA_CFLAGS := $(WFLAGS) -Wall -I$(RT28xx_DIR)/include endif
After make command, the size of rt5370sta.ko is 13,750,585. The file size is too big. How can I reduce the size?
Thanks all.
...ANSWER
Answered 2018-Mar-29 at 10:51It is likely that your build includes debug symbols. Either explicitly build for release by whatever means is documented for the build system or strip the symbols after with:
QUESTION
I compare three compilers:
- GCC (x86) from Debian (6.3.0) produces hugo_x86.so with 7.8K,
- GCC (ppc) from Codesourcery (4.6.0) produces hugo_46.so with 6.6K,
- GCC (x86) from Buildroot 2017.08 (7.2.0) produces hugo.so with 7.5K,
- GCC (ppc) from Buildroot 2017.08 (7.2.0) produces hugo.so with 67K,
- GCC (ppc) from Buildroot 2017.08 (6.4.0) produces hugo.so with 67K and
- GCC (ppc) from Buildroot 2017.08 (4.9.4) produces hugo.so with 67K
The code was taken from eli.thegreenplace.net:
...ANSWER
Answered 2018-Jan-17 at 14:48from How to reduce ELF section padding?:
It looks like this is due to binutils 2.27 increasing the default page size of PowerPC targets to 64k, resulting in bloated binaries on embedded platforms.
There's a discussion on the crosstool-NG github here.
Configuring binutils with --disable-relro should improve things.
You can also add -Wl,-z,max-page-size=0x1000 to gcc when compiling.
When adding BR2_BINUTILS_EXTRA_CONFIG_OPTIONS="--disable-relro"
to my buildroot configuration, the share object size is reduced.
QUESTION
so you might recognize me from the other day when I asked a similar question about running this code in an IDE. Eventually the advice I got was that I should learn to run them together from the command line. As such I took the advice and installed the GNU toolchain from Codesourcery Lite MentorGraphics (not sure if that makes sense). The commands I can do are things like
...ANSWER
Answered 2017-Oct-29 at 16:48In case anyone ever comes across this, the way I eventually got it working was to type these script lines into the Windows command-line:
QUESTION
Code:
...ANSWER
Answered 2017-Feb-13 at 14:40I'm almost certain, that you have a file named String.h
in your project. Because you compile that on Windows, which is not smart enough to notice a difference between your String.h
and toolchain's string.h
, the line #include
actually includes your String.h
, where you most likely don't have that declaration.
If you'd compile that on Linux, it would most likely work, because the case of file names matters there. For Windows you have no other solution than to name your file (especially the header) differently. Personally I'd propose to have a single global function per module (header + source) and then you can name the module after the function. So in above case you'd have StrCpy2.h
and StrCpy2.c
.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install CodeSourcery
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page