On Thu, Feb 21, 2019 at 02:30:36PM +, Patrick Schneider wrote:
> Hi Sascha,
>
> $ otg.mode=host
>
> Did the trick for me. Now I can flash the nand from usb-stick data on
> /dev/disk0.0
> Works like a charm, thanks!
Well if you like that, try otg.mode=peripheral and
https://www.barebox.org/d
On Thu, Feb 21, 2019 at 12:13:50PM +, Thomas Hämmerle wrote:
> From: Thomas Haemmerle
>
> Port Xilinx Zynq MPSoC Firmware layer driver from linux.
>
> Signed-off-by: Thomas Haemmerle
> ---
> arch/arm/Kconfig | 1 +
> arch/arm/mach-zynqmp/Makefile
On Thu, Feb 21, 2019 at 10:28:48AM +0100, Tomaz Solc wrote:
> When booting a Raspberry Pi, it is useful to extract bootargs from the
> device tree that was created by the VideoCore firmware. These bootargs
> contain for example settings for the framebuffer that the kernel needs
> to properly set th
On Thu, Feb 21, 2019 at 09:34:47AM +0100, Tomaž Šolc wrote:
> Hi Sascha,
>
> On 20. 02. 19 12:28, Sascha Hauer wrote:
> > Right, I missed the environment snippet that is generated from
> > CONFIG_DEFAULT_ENVIRONMENT_PATH which is generated at a different place.
> > Please try this updated patch.
>
On Tue, Feb 19, 2019 at 11:29:05PM -0800, Andrey Smirnov wrote:
> Everyone:
>
> This series contains changes I made while working on adding USB
> support for ZII i.MX8MQ boards. There are several distinct parts in
> this series:
>
> 1. xHCI fixes, features and improvements
> 2. PHY driver defer
On Tue, Feb 19, 2019 at 03:16:46PM +0100, Ahmad Fatoum wrote:
> At the moment
> grep -r --exclude-dir=.git 'SPDX-License-Identifier:' | \
> grep -v 'GPL-2.0'
>
> shows me 39 non-dually-licensed source code files (SoCFPGA) that have a
> BSD-3-Clause license _identifier_.
> There seems to be n
The phyCORE-i.MX8M aka PCL-066 is a SoM containing a i.MX8M SoC.
phyCORE-i.MX8M:
- 1GB LPDDR4 RAM
- eMMC
- microSD
- Ethernet
Signed-off-by: Christian Hemp
---
Changes since v1:
- simplify bootsource detection
- replace pathname by phandle
- use name tag "imx8mq"
- update to new barebox
Hi Sascha,
$ otg.mode=host
Did the trick for me. Now I can flash the nand from usb-stick data on
/dev/disk0.0
Works like a charm, thanks!
Regards,
Patrick
> > Hi Sascha,
> > thanks for the reply.
> > It seems that I am lacking something in the usb configuration. I am always
> getting:
> >
> >
it is needed for raw dmesg output
Signed-off-by: Oleksij Rempel
---
common/console_common.c | 35 ++-
1 file changed, 18 insertions(+), 17 deletions(-)
diff --git a/common/console_common.c b/common/console_common.c
index 4aa54de97a..a4d2636753 100644
--- a/common
On Thu, Feb 21, 2019 at 12:01:40PM +, Patrick Schneider wrote:
> Hi Sascha,
> thanks for the reply.
> It seems that I am lacking something in the usb configuration. I am always
> getting:
>
> couldn't find an available UDC
> usbgadget: No such device
I don't know which hardware you are on, b
Same as linux dmesg, barebox dmesg will be able to restrict output level
by using -l option. For example "dmesg -l err,warn"
This functionality can be used for test automation.
Signed-off-by: Oleksij Rempel
---
commands/dmesg.c| 48 ++---
common/consol
Add -r option to mimic functionality of linux dmesg.
It will prefix log level and timestamp to each buffer:
<6>[ 460us] barebox 2019.02.0-00266-g6aea757067-dirty #355 Thu Feb 21
11:51:43 CET 2019
<6>[ 6279us] Board: DPTechnics DPT-Module
<6>[209281us] mdio_bus: miibus0: probed
<6>[
From: Thomas Haemmerle
Changes since v1:
- return -EIO (instead of -1) if API version or trustzone version are
earlier than v1.0 in probe function
Thomas Haemmerle (1):
firmware-zynqmp: port from linux
arch/arm/Kconfig | 1 +
arch/arm/mach-zynqmp/Makefi
Hi Sascha,
thanks for the reply.
It seems that I am lacking something in the usb configuration. I am always
getting:
couldn't find an available UDC
usbgadget: No such device
$ fastboot devices -l
Delivers nothing on my windows host side.
Before I proceed, wouldn't it be also possible to just pl
Hi Patrick,
On Thu, Feb 21, 2019 at 10:01:27AM +, Patrick Schneider wrote:
> Hi guys,
> I'm trying to find out if the following is possible: In a production
> environment, there is only the USB connection present, no console
> access to the device. The USB serial downloader mode starts and I
With this patch the two last lines are added to the output of the
following command:
$ ./scripts/bareboximd
images/barebox-phytec-phycore-imx6dl-som-emmc-1gib.img
build: #15 Thu Feb 21 11:20:23 CET 2019
release: 2019.02.0-00235-gb03cf6f145ae-dirty
parameter: memsiz
Signed-off-by: Uwe Kleine-König
---
include/image-metadata.h | 4
scripts/gen-dtb-s| 4 ++--
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/include/image-metadata.h b/include/image-metadata.h
index 8739bffb92e1..5904d95acd37 100644
--- a/include/image-metadata.h
+++ b
Hello Patrick,
On 2/21/19 11:01 AM, Patrick Schneider wrote:
> Hi guys,
> I'm trying to find out if the following is possible:
> In a production environment, there is only the USB connection present, no
> console access to the device.
> The USB serial downloader mode starts and I am able to load
On Raspberry Pi, VideoCore firmware creates a device tree that contains
information about peripherals that were initialized by VideoCore based
on settings in config.txt. Normally this device tree is passed to the
Linux kernel via a pointer in the r2 register. A bootloader needs to
pass this device
Hi guys,
I'm trying to find out if the following is possible:
In a production environment, there is only the USB connection present, no
console access to the device.
The USB serial downloader mode starts and I am able to load a barebox image to
the i.MX6ul RAM. That works either with MFGTools or
Knowing the address of the end of the memory area used by Barebox is
useful if PBL stores some extra data after it, so that board init code
can later retrieve it from there.
---
arch/arm/cpu/start.c | 8
arch/arm/include/asm/barebox-arm.h | 1 +
2 files changed, 9 insertions
Dear all,
these patches make Barebox aware of the device tree and boot arguments that are
constructed by the VideoCore firmware on Raspberry Pi. This fixes many problems
with hardware that is initialized from VideoCore when booting a kernel shipped
with Raspbian (e.g. when using dtoverlay directiv
When booting a Raspberry Pi, it is useful to extract bootargs from the
device tree that was created by the VideoCore firmware. These bootargs
contain for example settings for the framebuffer that the kernel needs
to properly set the video output.
This commit adds an of_bootargs command that extrac
Hi Sascha,
On 20. 02. 19 12:28, Sascha Hauer wrote:
Right, I missed the environment snippet that is generated from
CONFIG_DEFAULT_ENVIRONMENT_PATH which is generated at a different place.
Please try this updated patch.
Thanks, as far as I can see this patch works correctly now.
I suggest addi
24 matches
Mail list logo