[U-Boot] U-Boot 2015 and u-boot-fw-utils 2017.09

[U-Boot] U-Boot 2015 and u-boot-fw-utils 2017.09

[Diaz]

Hi,

I am using U-Boot 2015.04, and the new root file system for my platform includes u-boot-fw-utils 2017.09. I have noticed that fw_{print,set}env utilities are no longer working. 

Should these be compatible and work properly? Or are there any changes regarding how the environment is read and written between v2015.04 and v2017.09 that would explain this incompatility?

Thanks

[U-Boot] U-Boot 2015 and u-boot-fw-utils 2017.09

[Lukasz Majewski]

On Tue, 9 Jan 2018 11:17:06 +0000
"Diaz de Grenu, Jose" <Jose.DiazdeGrenu@digi.com> wrote:

> Hi,
> 
> I am using U-Boot 2015.04, and the new root file system for my
> platform includes u-boot-fw-utils 2017.09. I have noticed that
> fw_{print,set}env utilities are no longer working. 

Strace output would be helpful here....

The fw_* utils were a bit reworked around 2017.09 (there were some
build breaks of it IIRC), so yes you may see some problems.

> 
> Should these be compatible and work properly? Or are there any
> changes regarding how the environment is read and written between
> v2015.04 and v2017.09 that would explain this incompatility?

U-boot is rapidly changing - due to DM, Kconfig, introduction.

Some debug data would be helpful.

Is your 2015.04 u-boot working with older fw_* utils?

> 
> Thanks
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot



Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180111/8d50574b/attachment.sig>

[U-Boot] U-Boot 2015 and u-boot-fw-utils 2017.09

[Wolfgang Denk]

Hello,

In message <20180111100422.7957c7f3@jawa> you wrote:
>
> > I am using U-Boot 2015.04, and the new root file system for my
> > platform includes u-boot-fw-utils 2017.09. I have noticed that
> > fw_{print,set}env utilities are no longer working. 
>
> Strace output would be helpful here....

Definitely.  Ideally both for the old, working, and for the new,
failing, version.

> The fw_* utils were a bit reworked around 2017.09 (there were some
> build breaks of it IIRC), so yes you may see some problems.

But then, the actual format of the environment data has never been
changed, so we really need more details.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
If it happens once, it's a bug.
If it happens twice, it's a feature.
If it happens more than twice, it's a design philosophy.

[U-Boot] U-Boot 2015 and u-boot-fw-utils 2017.09

[Diaz]

-----Original Message-----
From: Wolfgang Denk [mailto:wd at denx.de] 


> But then, the actual format of the environment data has never been changed, so we really need more details.

Correct. The problem was a custom patch. I can confirm now that I am able to write and read the environment with no problems using U-Boot 2015.04 and u-boot-fw-utils 2017.x.

Thanks and sorry for the false alarm.

[U-Boot] U-Boot 2015 and u-boot-fw-utils 2017.09

[Lukasz Majewski]

On Thu, 11 Jan 2018 11:58:19 +0000
"Diaz de Grenu, Jose" <Jose.DiazdeGrenu@digi.com> wrote:

> -----Original Message-----
> From: Wolfgang Denk [mailto:wd at denx.de] 
> 
> 
> > But then, the actual format of the environment data has never been
> > changed, so we really need more details.  
> 
> Correct. The problem was a custom patch. I can confirm now that I am
> able to write and read the environment with no problems using U-Boot
> 2015.04 and u-boot-fw-utils 2017.x.
> 
> Thanks and sorry for the false alarm.

No problem, You are welcome.

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180111/c8e63973/attachment.sig>

[U-Boot] U-Boot 2015 and u-boot-fw-utils 2017.09

[Joakim Tjernlund]

On Thu, 1970-01-01 at 00:00 +0000, Wolfgang Denk wrote:
> 
> Hello,
> 
> In message <20180111100422.7957c7f3@jawa> you wrote:
> > 
> > > I am using U-Boot 2015.04, and the new root file system for my
> > > platform includes u-boot-fw-utils 2017.09. I have noticed that
> > > fw_{print,set}env utilities are no longer working.
> > 
> > Strace output would be helpful here....
> 
> Definitely.  Ideally both for the old, working, and for the new,
> failing, version.
> 
> > The fw_* utils were a bit reworked around 2017.09 (there were some
> > build breaks of it IIRC), so yes you may see some problems.
> 
> But then, the actual format of the environment data has never been
> changed, so we really need more details.

Speaking of the fw tools, I have always wanted to be able to specify
"whole mtd device" for plain NOR flash in fw_env.config so instead of 
 /dev/mtd1		0x0000		0x4000		0x4000
One could jsut say 
 /dev/mtd1		0x0000		0x4000
like one can do for SPI flash. Thoughts ?

 Jocke
 

[U-Boot] U-Boot 2015 and u-boot-fw-utils 2017.09

[Lukasz Majewski]

Hi Joakim,

> On Thu, 1970-01-01 at 00:00 +0000, Wolfgang Denk wrote:
> > 
> > Hello,
> > 
> > In message <20180111100422.7957c7f3@jawa> you wrote:  
> > >   
> > > > I am using U-Boot 2015.04, and the new root file system for my
> > > > platform includes u-boot-fw-utils 2017.09. I have noticed that
> > > > fw_{print,set}env utilities are no longer working.  
> > > 
> > > Strace output would be helpful here....  
> > 
> > Definitely.  Ideally both for the old, working, and for the new,
> > failing, version.
> >   
> > > The fw_* utils were a bit reworked around 2017.09 (there were some
> > > build breaks of it IIRC), so yes you may see some problems.  
> > 
> > But then, the actual format of the environment data has never been
> > changed, so we really need more details.  
> 
> Speaking of the fw tools, I have always wanted to be able to specify
> "whole mtd device" for plain NOR flash in fw_env.config so instead of 
>  /dev/mtd1		0x0000		0x4000
> 0x4000 One could jsut say 
>  /dev/mtd1		0x0000		0x4000
> like one can do for SPI flash. Thoughts ?
> 

Apparently you are the first one, who see such functionality as useful.

I don't mind - feel free to prepare patches :-)

>  Jocke
>  


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180111/0aff5971/attachment.sig>