uboot | directory contains the source code

by kittyhawk C Version: Current License: Non-SPDX

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

kandi X-RAY | uboot Summary

uboot is a C library. uboot has no bugs, it has no vulnerabilities and it has low support. However uboot has a Non-SPDX License. You can download it from GitHub.

# # Copyright 2000 - 2005 # Wolfgang Denk, DENX Software Engineering, wd@denx.de. # # See file CREDITS for list of people who contributed to this # project. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License as # published by the Free Software Foundation; either version 2 of # the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 59 Temple Place, Suite 330, Boston, # MA 02111-1307 USA #.

Support

Quality

Security

License

Reuse

Support

uboot has a low active ecosystem.

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

It had no major release in the last 6 months.

uboot has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of uboot is current.

Quality

uboot has 0 bugs and 0 code smells.

Security

uboot has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

uboot code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

uboot has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

uboot 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 1742 lines of code, 31 functions and 19 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 uboot

Get all kandi verified functions for this library.

uboot Key Features

No Key Features are available at this moment for uboot.

uboot Examples and Code Snippets

No Code Snippets are available at this moment for uboot.

Community Discussions

Trending Discussions on uboot

buildroot defconfig for pocketBeagle is not working

SAMA5d31:The Uboot cannot be started

Enable HDMI output for AM3358 Debian 10.3 2020-04-06 4GB SD IoT (BeagleBone Black)

ARM TrustZone: Accessing a non-secure buffer from a secure monitor runtime service

In embedded programming, when using uboot which dts files should i modify?

About Beaglebone Black CAN protocol setting

feature 'postinstall' required for "adu-swupdate.sh" in sw-description is absent

U-boot Script Bad Header CRC

aarch64 KVM guest hangs on early linux boot

Need 'built-in.o' error when compiling U-Boot

QUESTION

buildroot defconfig for pocketBeagle is not working

Asked 2022-Mar-22 at 05:11

I have a pocketbeagle board and I was trying to build an os image for it using buildroot. so I downloaded the latest buildroot, there was no defconfig file for pocketbeagle. so decided to use beaglebone_defconfig. The build was successful but when I try to boot the pocketbeagle with this image it is continuously printing this message on the uart console:

Could not initialize timer (err -19)
Could not initialize timer (err -19)
Could not initialize timer (err -19)
Could not initialize timer (err -19)
Could not initialize timer (err -19)
Could not initialize timer (err -19)

I think this message is coming from uboot.

This is the steps I used to build the image:

...

ANSWER

Answered 2022-Mar-22 at 05:11

Obviously there are differences in the 2 boards. Your build would succeed but wont run on pocket beagle because it is not meant to run on it.

specifications pocket beagle Beagle bone SoC OSD3358-SM AM3358/9 CPU Sitara AM3358 M Cortex-A8 Cortex-A8 + Dual PRU (200 MHz) Frq (MHz) 1000 720

To build BSP for pocket beagle follow below steps,

In Target options – Change Target architecture to ARM (little endian) – Change Target architecture variant to Cortex-A8
In Build options, set global patch directories to board/e-ale/pocketbeagle/patches/. This will allow you to put patches for Linux, U-Boot other packages in subdirectories of board/e-ale/pocketbeagle/patches/.
Toolchain - you can use external or internal.
In Kernel – Enable the Linux kernel, obviously! – Choose Custom version as the Kernel version – Choose 4.14.24 as Kernel version – Patches will already be applied to the kernel, thanks to us having defined a global patch directory above. – Choose omap2plus as the Defconfig name – We’ll need the Device Tree of the PocketBeagle, so enable Build a Device Tree Blob (DTB) – And use am335x-pocketbeagle as the Device Tree Source file names
Target packages - as per your requirement.
In Filesystem images, enable ext2/3/4 root filesystem, select the ext4 variant.
In Bootloaders, enable U-Boot, and in U-Boot: – Switch the Build system option to Kconfig: use U-Boot – Use a Custom version of value 2018.01. – Use am335x_pocketbeagle as the Board defconfig

As you have noticed, in the configuration, you have referenced board/e-ale/pocketbeagle/ patches as a directory containing patches for various packages. We now need to add the U-Boot and Linux patches that add support for the PocketBeagle, which are not upstream. Use patches, and just copy it to board/e-ale/pocketbeagle so that you get the following directory hierarchy:

Then build the BSP and run on your device.

source

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

QUESTION

SAMA5d31:The Uboot cannot be started

Asked 2022-Feb-24 at 12:14

I currently use a custom board based on SAMa5D31:

Emmc is currently used for boot
The Uboot fails to be started

Stuck in SD/MMC: Done to load image without any reaction

...

ANSWER

Answered 2022-Feb-24 at 12:14

Modify the following

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

QUESTION

Enable HDMI output for AM3358 Debian 10.3 2020-04-06 4GB SD IoT (BeagleBone Black)

Asked 2022-Jan-16 at 20:12

I am trying to get my BeagleBone Black to post to my monitor, to be able to use it as a stand-alone PC.

This was possible with the image that the BeagleBone shipped with.

I have just installed a new image on my BeagleBone Black Rev C.

The new image is AM3358 Debian 10.3 2020-04-06 4GB SD IoT.

I am able to SSH to it using PuTTY, and this way I have succesfully performed some actions with it, like using wget to download files from Google Drive etc.

So it seems like the board is working well, and that the HDMI output is disabled somewhere.

I have copied the contents of the uEnv.txt-file below, to show that the lines regarding disabling of video are commented out:

...

ANSWER

Answered 2022-Jan-16 at 20:12

I solved the problem, following a solution found here.

The solution was to run a kernel update:

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

QUESTION

ARM TrustZone: Accessing a non-secure buffer from a secure monitor runtime service

Asked 2021-Dec-07 at 16:09

My setup consists of a STM32MP157C-DK2 which uses Trusted Firmware-A to load SP-MIN as BL32 and uBoot+Linux as BL33.

I am trying to get a small example working where I create an SMC from the Linux Kernel which passes a reference to non-secure memory. The data at that location should be altered by the runtime service handling the SMC.

The problem I'm facing is that I can't find any information on what steps are required in order to translate the virtual address from the Linux Kernel at NS:EL1 to the translation regime of EL3.

The code of my runtime service looks like this:

...

ANSWER

Answered 2021-Dec-07 at 16:09

The problem I'm facing is that I can't find any information on what steps are required in order to translate the virtual address from the Linux Kernel at NS:EL1 to the translation regime of EL3.

The TrustZone protection is based on a physical address. For either NS:EL1 or EL3, you can map using an MMU in various ways, but both must map to the same physical address. For Linux kernel, you need to add a mapping of the shared memory that is backed by the physical address. You can use virt_to_phys() with such a mapping to find the physical address.

You need to have the same mapping available in the EL3. The simplest is to have a flat virt==phys mapping with sections and super-sections.

Another portion is that you MUST setup the TZASC to have permissions of the physical portion as world shareable. An example of code manipulating TZASC. This depends on your hardware, often this information is only given under NDA with chip manufacturer.

The other caveat is that you SHOULD map the memory as non-cacheable or you rely on flushes, which is error prone and could be a security issue, if the system has a VIVT cache. Some ARM CPUs have a VIPT cache and it maybe possible to use cached memory on those systems.

I would also recommend you do not pass addresses via the SMC API. You know the fixed world shareable buffer size. So, it is better to pass an index that is 0..extent-1 and immediately give an error if the address is outside the range. In this way only your initial Linux code needs to create the mapping and then you can use the virtual address given and only pass the index. Naively this seems more secure. Most attacks against TrustZone will be on the API itself.

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

QUESTION

In embedded programming, when using uboot which dts files should i modify?

Asked 2021-Nov-29 at 22:44

I need more references besides the uboot documentation. Is there anything that i can read to futher my understanding?

I am confused on what dts files my build is using when using uboot. Do I modify all the relevant dts files, for both kernel/ and uboot/ directories.

Or do i set it in a specific file? Can i tell which dts I used once I am booted into linux?

for example I am using an imx8mq-evk board, but there are many dts files to choose from.

...

ANSWER

Answered 2021-Nov-29 at 22:44

Well, there's many parts to your question. Lets start by looking at configs/imx8mq_evk_defconfig in U-Boot and in there we can see:

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

QUESTION

About Beaglebone Black CAN protocol setting

Asked 2021-Nov-25 at 07:16

Thank you for watching this.

I'm having difficulties with my BBB on CAN communication like for months... I'd be really pleased if you could give me just a little help!

I'm working on CAN protocol between BBB and another CAN device. The another device is confirmed to be working alright with CAN. I'm using my BBB with Cloud9 platform on windows laptop, and on the another device, it's using CAN0.

I have set the 'config-pin' on BBB like below using CAN1, and I tried 'cansend' utility. The bitratre value on the another device is also set to be equal.

...

ANSWER

Answered 2021-Aug-07 at 03:47

Some help on can or socketCAN will be found here for the BBB or other family board:

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

QUESTION

feature 'postinstall' required for "adu-swupdate.sh" in sw-description is absent

Asked 2021-Nov-15 at 16:17

I am currently working on Azure Device Update using layers meta-azure-device-update and meta-swupdate. I want to run a post-install script. I have followed sources mentioned below:

1.sw-description.rst https://git.rigado.com/vesta/swupdate/-/blob/acf50e361a8752db48e69ffe3c20a167c402d35f/doc/source/sw-description.rst#board-specific-settings

2.adu-swupdate.sh https://github.com/Azure/iot-hub-device-update/blob/main/src/adu-shell/scripts/adu-swupdate.sh

The image was built successfully and I was able to locate adu-swupdate.sh in .swu file which I provided Azure Device Update. The install failed giving below mentioned error:

Sep 21 07:21:30 rpi AducIotAgent[281]: -> 07:21:29 PUBLISH | IS_DUP: false | RETAIN: 0 | QOS: DELIVER_AT_MOST_ONCE | TOPIC_NAME: $iothub/twin2021-09-21T07:21:30.2396Z [E] Install failed, extendedResultCode = 1 [Install]

Sep 21 07:21:30 rpi AducIotAgent[281]: 2021-09-21T07:21:30.2398Z [E] Install failed. error 0, 1 - Expecting service to send Cancel action [ADUC_Workflow_WorkCompletionCallback]

The sw-update log is as given below:

...

ANSWER

Answered 2021-Nov-15 at 16:17

So, After hours of exploration and reading each page of SW-UPDATE Wiki, I figured out that there are handlers for each function which we must enable before using it.

you can read more about them here. https://sbabic.github.io/swupdate/handlers.html

These handlers are available in the meta-swupdate/recipes-support/swupdate/defconfig

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

QUESTION

U-boot Script Bad Header CRC

Asked 2021-Sep-16 at 13:23

I have a "flashing" script being loaded into a Uboot, on an iMX6, from a host PC via sdp. The script has been run through mkimage, so it has an image header. Here's the mkimage command:

...

ANSWER

Answered 2021-Sep-15 at 01:55

What am I doing wrong?

U-Boot almost always assumes hexadecimal values for command arguments, so using the 0x... prefix is actually superfluous. AFAIK there is no way to input decimal values.

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

QUESTION

aarch64 KVM guest hangs on early linux boot

Asked 2021-Sep-01 at 06:37

I'm trying to set up a very minimal aarch64 KVM-capable system.

My design requires a minimalist kernel with few drivers linked to the kernel image. My objective is to bring up a virtual machine running a bare-metal application as quickly as possible. The same hypervisor is required later to be able to run a full-fledged Linux distribution.

It happens to me that when this aarch64 hypervisor starts a Linux VM with qemu -M virt,accel=kvm the VM executes the bootloader, the kernel's efi stub, but hangs in the kernel's arch-specific initialization. To be more precise, running the qemu and peep into the hung system, I found the PC to be often around this position:

...

ANSWER

Answered 2021-Sep-01 at 06:37

At last, I managed to make the KVM host run in the environment described up there.

Resuming here the issue:

Minimal Linux with KVM support
Minimal Linux system with its bootloader and kernel image to run in the virtualized context
Linux kernel slightly modified in the start_kernel() by adding a few printk() to emit timestamps
The image is proved to be working on qemu without the KVM extension

Test with qemu and the KVM extension gives the following results:

As the qemu starts

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

QUESTION

Need 'built-in.o' error when compiling U-Boot

Asked 2021-Aug-25 at 08:17

I am trying to compile U-Boot for the developer board with armv7 processor. It has a Rockchip RK3288 processor. The commands I use are: