On Mon, 2018-12-03 at 14:26 +0100, Sascha Hauer wrote:
> On Mon, Dec 03, 2018 at 02:06:21PM +0100, Erwin Rol wrote:
> > On Mon, 2018-12-03 at 13:58 +0100, Sascha Hauer wrote:
> > > Hi Erwin,
> > >
> > > On Mon, Dec 03, 2018 at 01:42:11PM +0100
On Mon, 2018-12-03 at 13:58 +0100, Sascha Hauer wrote:
> Hi Erwin,
>
> On Mon, Dec 03, 2018 at 01:42:11PM +0100, Erwin Rol wrote:
> > Hallo all,
> >
> > I want to create empty ubifs volumes, like this;
> >
> > 1) ubiformat -y -q /dev/nand0.system
&
Hallo all,
I want to create empty ubifs volumes, like this;
1) ubiformat -y -q /dev/nand0.system
2) ubiattach /dev/nand0.system
3) ubimkvol -t dynamic /dev/nand0.system.ubi system 0
4)
5) mount -t ubifs -o rw /dev/nand0.system.ubi.system /mnt/system/
Is this possible with barebox?
file, so I can call barebox_update ?
Or what would be the "barebox" way to do it ?
TIA,
Erwin
On Fri, 2018-11-30 at 14:49 +0100, Erwin Rol wrote:
> Hallo all,
>
> I have my barebox running on a iMx6 (phyBOARD-Segin + phyCORE-i.MX 6UL
> Modul).
>
> Loading via USB wor
Hallo all,
I have my barebox running on a iMx6 (phyBOARD-Segin + phyCORE-i.MX 6UL
Modul).
Loading via USB works fine, and via DFU I can upload a barebox image
and use barebox_update to flash barebox in NAND.
Is it possible to have DFU correctly flash barebox, without first
upload a image to /tmp
Hallo All,
I am trying to get USB device (DFU) to work on my Phytec Segin board
(imx6ul SOC).
I can upload barebox with imx-usb-loader and it starts fine (so USB
hardware is working)
Than when barebox runs I want to put that same USB port in DFU mode and
update the nand flash (barebox, env, ker
Hallo Sascha,
On Wed, 2018-11-21 at 09:18 +0100, Sascha Hauer wrote:
> Hi Erwin,
>
> On Tue, Nov 20, 2018 at 09:08:01PM +0100, Erwin Rol wrote:
> > Hallo,
> >
> > as long time u-boot user I have several projects where we have a dual
> > dataflash "sector&qu
Hallo,
as long time u-boot user I have several projects where we have a dual
dataflash "sector" in wich we store our env variables. And dual so we
always have or the correct old version or the correct new version even
if there is a power fail during saveenv.
Is powerfail robust env writing also a
Hey all,
I saw some mails and patches passing by for the Rockchip RK3188. Since I
am just starting a project with a RK3188 I was wondering if there are
ppl that have more info than the pathetic databook from Rochchip.
Also it seems large parts (even essential things like the NAND
controller) are
You could use a small Linux system with an adapted kexec to boot
barebOS. That way barebOS doesn't have to bother with the boot processes.
- Erwin
On 1-4-2014 11:02, Sascha Hauer wrote:
> Hi All,
>
> barebox more and more comes in the area that is has everything an
> operating system needs:
>
Hey all,
what ist the status of the Tegra 2 and Tegra 3 support in Barebox ?
One very important question is;
Can it be updated from within barebox or linux (running on the Tegra) or
does it need nvflash like tools?
TIA,
Erwin
___
barebox mailing list
On 31-7-2012 17:51, Jean-Christophe PLAGNIOL-VILLARD wrote:
On 17:16 Tue 31 Jul , Erwin Rol wrote:
Hey Sascha,
On 31-7-2012 15:13, Sascha Hauer wrote:
Hi Erwin,
On Tue, Jul 31, 2012 at 12:49:29PM +0200, Erwin Rol wrote:
Hey x86-asm-experts,
Surely you do not mean me ;)
On 31-7-2012
Hey Sascha,
On 31-7-2012 15:13, Sascha Hauer wrote:
Hi Erwin,
On Tue, Jul 31, 2012 at 12:49:29PM +0200, Erwin Rol wrote:
Hey x86-asm-experts,
Surely you do not mean me ;)
On 31-7-2012 0:36, Erwin Rol wrote:
So when I use the memset code the asm looks like this below. As you
can see the
Hey x86-asm-experts,
On 31-7-2012 0:36, Erwin Rol wrote:
Hallo,
after I had successfully "ported" barebox to about 5 different embedded
x86 (mostly N270 and Z510 Atom boards) I ran into problems with a
Celeron SU2300 CPU based board. After a lot of trail and error, which
in
Hallo,
after I had successfully "ported" barebox to about 5 different embedded
x86 (mostly N270 and Z510 Atom boards) I ran into problems with a
Celeron SU2300 CPU based board. After a lot of trail and error, which
included the implementation of a BIOS based console cause the board does
not h
On 3-2-2012 20:17, Erwin Rol wrote:
Hey all,
when I try to compile barebox for x86 with GCC 4.6.2 I get the following
error at the linking stage ;
i686-n270-linux-gnu-ld: section .eh_frame loaded at
[00018c10,000219eb] overlaps section .barebox_initcalls
loaded at
Hey all,
when I try to compile barebox for x86 with GCC 4.6.2 I get the following
error at the linking stage ;
i686-n270-linux-gnu-ld: section .eh_frame loaded at
[00018c10,000219eb] overlaps section .barebox_initcalls
loaded at [00018c10,00018c63]
Any hints
17 matches
Mail list logo
