u-boot | Mirror

by qemu C Version: v2023.04-rc4 License: No License

X-Ray Key Features Code Snippets Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | u-boot Summary

u-boot is a C library. u-boot has no bugs and it has low support. However u-boot has 16 vulnerabilities. You can download it from GitHub.

Mirror of git.qemu.org/u-boot.git

Support

Quality

Security

License

Reuse

Support

u-boot has a low active ecosystem.

It has 54 star(s) with 42 fork(s). There are 9 watchers for this library.

It had no major release in the last 6 months.

u-boot has no issues reported. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of u-boot is v2023.04-rc4

Quality

u-boot has 0 bugs and 0 code smells.

Security

u-boot has 16 vulnerability issues reported (9 critical, 6 high, 1 medium, 0 low).

u-boot code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

u-boot does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

u-boot releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

It has 38848 lines of code, 2831 functions and 280 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of u-boot

Get all kandi verified functions for this library.

u-boot Key Features

No Key Features are available at this moment for u-boot.

u-boot Examples and Code Snippets

No Code Snippets are available at this moment for u-boot.

Community Discussions

Trending Discussions on u-boot

Reading file would overwrite reserved memory. Failed to load 'hello_world.bin

Kconfig: How to prevent a specific CONFIG_* switch, when this leads to an issue?

U-Boot - multiple same output formats in linker scripts for ARM

confused about stack pointer in arm64, sp is not same as SP_EL2 register when kernel is running at EL2

What is config_whitelist.txt file and how is it used in u-boot?

Beaglebone / Yocto / Kernel configuration

What type of memory is Uboot able to see using "md"?

How should I apply add-symbol-file command during u-boot linux boot debug?

U-Boot error while decompressing gzipped kernel

Fail to build Yocto extensible SDK

QUESTION

Reading file would overwrite reserved memory. Failed to load 'hello_world.bin

Asked 2022-Apr-01 at 19:14

I have imx7d-pico with Carrier board. This tiny computer was used a lot for Android Things. PDF (datasheet) easily found.

I stay (during the last two weeks) trying this tutorial: https://github.com/TechNexion/freertos-tn/tree/freertos_1.0.1_imx7d

...

ANSWER

Answered 2022-Apr-01 at 19:14

I solved with two changes in device-tree files:

in imx7d.dtsi
I put status = "okay";
in rpmsg: rpmsg{

in imx7d-pico-pi-qca-m4.dts
I put:

reserved-memory {
        rpmsg_vrings: vrings0@0x8ff00000 {
            reg = <0x8fff0000 0x10000>;
            no-map;
        };
    };

&

&rpmsg{
    memory-region = <&rpmsg_vrings>;
    vdev-nums = <1>;
    reg = <0x9fff0000 0x10000>;
    status = "okay";
};

Source https://stackoverflow.com/questions/71073386

QUESTION

Kconfig: How to prevent a specific CONFIG_* switch, when this leads to an issue?

Asked 2022-Mar-12 at 16:20

Is there an opposite for depends on in Kconfig? Which at least prints a warning when a specific CONFIG_* switch is set, which isn't compatible after the full configuration is written (.config) after a make *_defconfig?

My current problem:
I'm working on a new driver for the ARMv7-M Systick timer. There exists an old version, but this version lacks in some functionality and isn't ported to the new U-Boot device model (DM). When a new vendor use both driver, then this leads in an linker error.

So I want prevent with Kconfig to use my driver, when the old driver is selected.

Or any other suggestion how to solve this?

(This is a generic question for projects which use Kbuild/Kconfig as build system.)

...

ANSWER

Answered 2022-Mar-12 at 16:16

The documentation states you can use depends on , so you can do:

Source https://stackoverflow.com/questions/71446512

QUESTION

U-Boot - multiple same output formats in linker scripts for ARM

Asked 2022-Mar-02 at 07:53

I'm currently investigating the U-Boot source tree, because I want add support for a specific ARM architecture for the purpose of education.

Also investigated the linker scripts for ARM, but there is something what I currently don't understand:

...

ANSWER

Answered 2022-Mar-02 at 07:53

Binutil manpages are available at https://sourceware.org/binutils/docs/ld/Format-Commands.html

The first argument is the default output format the second one is for a user explicitly asking for big-endian with -EB passed to ld, the third for a user explicitly asking for low-endian with -EL.

If all are the same, using a single parameter for OUTPUT_FORMAT should have the same effect.

Source https://stackoverflow.com/questions/71315585

QUESTION

confused about stack pointer in arm64, sp is not same as SP_EL2 register when kernel is running at EL2

Asked 2022-Feb-26 at 17:02

While debugging linux booting on a virtual machine, I found the stack pointer registers are strange. I was in a printk routine early in the start_kernel function. (the serial port is not connected so the data is just wrtten to the log buffer at this time). When I'm in the function vsnprintf (linux-5.4.21), when I examine the stack pointers, it is seen like this(this is seen for the arm64 virtual machine running on qemu).

...

ANSWER

Answered 2022-Feb-26 at 06:37

https://developer.arm.com/documentation/ddi0595/2021-06/AArch64-Registers/SP-EL2--Stack-Pointer--EL2-

Holds the stack pointer associated with EL2. When executing at EL2, the value of SPSel. SP determines the current stack pointer:

Source https://stackoverflow.com/questions/71274570

QUESTION

What is config_whitelist.txt file and how is it used in u-boot?

Asked 2022-Feb-25 at 10:02

In u-boot source code, I see scripts/config_whitelist.txt with many CONFIG_XXX values.
What is the file and how is it used?

...

ANSWER

Answered 2022-Feb-25 at 10:02

since this commit:

Source https://stackoverflow.com/questions/70329549

QUESTION

Beaglebone / Yocto / Kernel configuration

Asked 2022-Feb-23 at 06:33

I want to change Kernel configuration.

I have my own layer created and inside my layer I have a _%.bbappend file which directly targets the recipe linux-ti-staging.bb (link). This recipe builds my kernel:

...

ANSWER

Answered 2022-Feb-14 at 12:45

Your directory structure should be like this

Source https://stackoverflow.com/questions/71111397

QUESTION

What type of memory is Uboot able to see using "md"?

Asked 2022-Feb-15 at 12:32

I am a complete newbie at this and I have stumbled upon something I cannot find the answer to. I am currently playing around with a Linux based system called Toradex Verdin iMX8MM. When I boot it into U-boot I can see some sort of memory. This is done by the standard "md" command. For fun I tried to print a bunch of different addresses and then display those address in u-boot. This seems to crash the system and I am not able to view those particular addresses. Does that mean its some sort of different memory, some sort of access denied or what is happening? I pasted the code I used below to print som adresses.

...

ANSWER

Answered 2022-Feb-14 at 13:47

What you're able to see depends on the memory map of the specific processor you're using. Generally speaking, if something is mapped to address X of physical memory, you can use md to read it and mw to write to it.

Now the code you're showing looks like a simple C program that would be run normally in user space. That's not going to work here as there's none of that support infrastructure in place really. And for just exploration of the system, that's not going to be the most useful path.

If you want to look around in memory, find the manual for the specific processor in question (it will say earlier in the startup log what it is) and then look at the different peripherals and where they're mapped to in memory by default. And possibly a little confusingly, keep in mind that DRAM is just another peripheral and that will show up in one range in memory while say a GPIO controller will show up in another spot in memory.

Source https://stackoverflow.com/questions/71109958

QUESTION

How should I apply add-symbol-file command during u-boot linux boot debug?

Asked 2022-Jan-19 at 05:25

I'm following linux bootloading using u-boot (using SPL falcon mode where u-boot-spl launches linux directly) on a qemu virtual machine. Now the code jumped to linux kernel and because I have done add-symbol-file vmlinux 0x80081000 I can follow the kernel code step by step using gdb connected to the virtual machine. Actually I loaded the kernel image to 0x80080000 but I had to set the address to 0x80081000 to make the source code appear on the gdb correctly according to the PC value(I don't know why this difference of 0x1000 is needed).
Later I found the kernel sets up the page table (identity mapping and swap table) and jumps to __primary_switched and this is where pure kernel virtual address is used first time for the PC. This is where the call is made at the end of the head.S file.

...

ANSWER

Answered 2022-Jan-19 at 05:25

I found my kernel load address was wrong (__PHYS_OFFSET was below physical ddr address start). After fixing it, the PC increments normally with kernel virtual address and I should just apply the add-symbol-file command using the virtual address.
This was the new section addresses.

Source https://stackoverflow.com/questions/70676679

QUESTION

U-Boot error while decompressing gzipped kernel

Asked 2022-Jan-18 at 22:27

I have an older embedded device (PHYTEC phyCORE-LPC3250) that runs the ancient U-Boot 1.3.3.

The Linux kernel uImage gets copied to the NAND flash at 0x200000, then booted with: nboot 80100000 0 200000;bootm

This works fine if the uImage is derived from the self-expanding zImage, but according to this mailing list post it is preferable to have U-Boot perform the decompression itself.

So I have tried creating a uImage that contains a gzipped version of the normal kernel image, but decompression fails:

...

ANSWER

Answered 2022-Jan-18 at 22:27

First U-Boot copies the uImage from NAND to RAM at the specified address 0x80100000. Then it unpacks the kernel to the load address specified in the uImage header, 0x80008000.

Since our kernel is about 8 MB uncompressed, that means the kernel's memory from 0x80008000 to approximately 0x80800000 overlaps where we copied the uImage at 0x80100000.

If the uImage is not compressed, unpacking the kernel can use memmove which handles overlapping address ranges without issue. (If the load address is the address where we copied it in RAM, the kernel gets executed in-place.)

But for compressed uImages, if we overwrite the compressed data while decompressing, decompression will obviously fail.

Source https://stackoverflow.com/questions/70762996

QUESTION

Fail to build Yocto extensible SDK

Asked 2022-Jan-02 at 13:11

I'm new to Yocto and I've been trying to setup for developing with devtool.

I've followed the instructions from from the Yocto Linux Kernel Development Manual, but I've made a change to Step #2, setting MACHINE = stm32mp1 since I'm targeting the STM32MP157D-DK1. However, Step #5 fails, where it asks you to build the SDK using the command bitbake core-image-minimal -c populate_sdk_ext with the following error:

...

ANSWER

Answered 2022-Jan-02 at 13:11

I've fixed the build issue. It required adding meta-python2 as I did; but instead of IMAGE_INSTALL_append = " python-dev", TOOLCHAIN_HOST_TASK_append = " nativesdk-python-core" is needed instead in local.conf.

Source https://stackoverflow.com/questions/70554998

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install u-boot

You can download it from GitHub.

Support

The Freescale QUICCEngine (QE) and Frame Manager (FMAN) both support the loading of "firmware", which is encoded in the QE firmware binary format. This firmware often needs to be loaded during U-Boot booting, so macros are used to identify the storage device (NOR flash, SPI, etc) and the address within that device.

Find more information at: