doc/usage:Warning from PATMAN tool prevents uploading a cmd-usage help file for askenv

[Adarsh Babu Kalepalli]

Hi Heinrich,

Having prepared the documentation for "askenv" man page , getting stuck
with a warning (PATMAN tool )to submit the patch.
-
$git add doc/usage/askenv.rst
$git commit
$./tools/patman/patman -c1 send -n
--
vb@vb:~/uboot/temp/u-boot$ ./tools/patman/patman -c1 send -n
WARNING: Unknown setting ignore_warnings
Cleaned 1 patch
WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does
MAINTAINERS need updating?
#16:
new file mode 100644
total: 0 errors, 1 warnings, 0 checks, 87 lines checked

0 errors, 1 warnings, 0 checks for 0001-testing.patch:
:16: *warning: added, moved or deleted file(s), does MAINTAINERS
need updating?*
checkpatch.pl found 0 error(s), 1 warning(s), 0 checks(s)
Bad divisor in main::vcs_assign: 0
Not sending emails due to errors/warnings
Dry run, so not doing much. But I would do this:

Send a total of 1 patch with no cover letter.
   0001-testing.patch
  Cc:  GitAuthor: Adarsh Babu Kalepalli 
To:  u-boot@lists.denx.de
Version:  None
Prefix:  None
Email would not be sent
-
How do I update maintainers about this new file ??.

It was noticed that modifying
*my %ignore_type = ();*
to
*my %ignore_type = (FILE_PATH_CHANGES);*

skipped generating this warning message.

How do I overcome this blocker??,Please advise.

Regards,
Adarsh

Re: [PATCH] cmd:Update HELP text of ’askenv’

[Adarsh Babu Kalepalli]

Hi Heinrich,

> thanks for looking for a better description.

> This online help does not correctly describe the command syntax yet
> which is:
Was trying to keep the command HELP text(on the shell ) simple and mention
the available parameters.


> The logic needs some explanation. The last parameter is used as size if
> it can be converted to a decimal number. In most other commands we
> expect a hexadecimal number.

> We started adding man-pages for all commands to doc/usage/. Do you want
> to give it a try?
Sure.

I am trying to review the HELP text of the shell commands and improve them
(if need be).
In this process, do you recommend following any specific approach ??

Regards,
Adarsh

On Tue, 1 Jun 2021 at 22:12, Heinrich Schuchardt  wrote:

> On 6/1/21 9:09 AM, opensource@gmail.com wrote:
> > From: Adarsh Babu Kalepalli 
> >
> > Help text of ‘askenv’ cmd is updated
> >
> > Signed-off-by: Adarsh Babu Kalepalli 
> > ---
> >
> >   cmd/nvedit.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/cmd/nvedit.c b/cmd/nvedit.c
> > index d14ba10cef..910cf16aaf 100644
> > --- a/cmd/nvedit.c
> > +++ b/cmd/nvedit.c
> > @@ -1569,7 +1569,7 @@ U_BOOT_CMD(
> >   askenv, CONFIG_SYS_MAXARGS, 1,  do_env_ask,
> >   "get environment variables from stdin",
> >   "name [message] [size]\n"
> > - "- get environment variable 'name' from stdin (max 'size'
> chars)"
> > + "- display 'message' and get environment variable 'name' from
> stdin (max 'size' chars)"
>
>
> Hello Ardash,
>
> thanks for looking for a better description.
>
> This online help does not correctly describe the command syntax yet
> which is:
>
> askenv name [message ...] [size]
>
> => askenv foo
> Please enter 'foo': abcdefgh
> => echo $foo
> abcdefgh
> =>
>
> => askenv foo 4
> Please enter 'foo': abcdefgh
> => echo $foo
> abcd
> =>
>
> => askenv foo msg1 msg2 msg3 3
> msg1 msg2 msg3 abcdefgh
> => echo $foo
> abc
> =>
>
> => askenv foo msg1 msg2 msg3
> msg1 msg2 msg3 abcdefgh
> => echo $foo
> abcdefgh
> =>
>
> The logic needs some explanation. The last parameter is used as size if
> it can be converted to a decimal number. In most other commands we
> expect a hexadecimal number.
>
> We started adding man-pages for all commands to doc/usage/. Do you want
> to give it a try?
>
> Best regards
>
> Heinrich
>
> >   );
> >   #endif
> >
> >
>

Re: [PATCH] pytest:Shutdown power-supply to board after the pytest execution

[Adarsh Babu Kalepalli]

Hi Stephen,

> FWIW, this violates the original design of the test system. Turning the
> board off at the end of the test is a policy decision that not all
> use-cases will want,

Wasn't aware that powering OFF the board would not be a preferred choice
for certain test cases.
Executing python test cases on sandbox or Beaglebone Black with this
power-off feature, did  not
cause me any issues.So,thought this would be a 'good to use' feature in the
python test framework.Hence,this patch.

As recommended , will use this power-off outside the pytest environment.

Thanks ,
Adarsh

On Fri, 28 May 2021 at 03:12, Stephen Warren  wrote:

> On 5/27/21 2:33 AM, opensource@gmail.com wrote:
> > From: Adarsh Babu Kalepalli 
> >
> > After executing the test-cases from pytest ,the board
> > is still powered.Shutting down the board power supply at
> > this point ,would keep the board safe.
>
> FWIW, this violates the original design of the test system. Turning the
> board off at the end of the test is a policy decision that not all
> use-cases will want, and hence not something that the test system should
> mandate. Instead, the intention is for the user to invoke the test
> system using a script that does something like:
>
> 1) Power on board.
> 2) Run test.
> 3) Power off board.
>
> See ./doc/develop/py_testing.rst in the U-Boot source for more
> background info, or the following URL for an example script:
>
> https://github.com/swarren/u-boot-ci-scripts/blob/master/test.sh
>

Re: cmd:GPIO:TI: 'gpio' command Failure Error on Beaglebone Black

[Adarsh Babu Kalepalli]

Hi Lokesh,

> Error -19 is ENODEV. Can you check if you have gpio devices being probed?

The device is not being probed.Output of "dm tree" is captured in
log_uboot-2021.07-rc1.txt

Where as in uboot-2021.04-rc2.txt,the gpio is probed.
The output of "dm tree" is in log_uboot-2021.04-rc2.txt

>>
>> The "gpio" command is proper till "U-Boot 2021.04-rc2".
>> Error message is noticed from subsequent releases on-wards.

>Any chance you were able to bisect to the culprit commit?
No
>which defconfig are you using?
We have been using "*am335x_evm_defconfig*"

Regards,
Adarsh


On Thu, May 6, 2021 at 11:33 AM Lokesh Vutla  wrote:

> Hi Adarsh,
>
> On 06/05/21 11:28 am, Adarsh Babu Kalepalli wrote:
> > Hi,
> >
> > Error output "*Command 'gpio' failed: Error -19*" is occurring with
> "*gpio
> > status -a*"
> > command on Beaglebone Black.
>
> Error -19 is ENODEV. Can you check if you have gpio devices being probed?
>
> >
> > The "gpio" command is proper till "U-Boot 2021.04-rc2".
> > Error message is noticed from subsequent releases on-wards.
>
> Any chance you were able to bisect to the culprit commit?
> which defconfig are you using?
>
> Thanks and regards,
> Lokesh
>
> >
> > Problem is noticed on u-boot versions from *U-Boot 2021.04-rc3 to U-Boot
> > 2021.07-rc1*
> > The same command is  OK on "sandbox" and "rpi 0 wireless" .
> >
> > Not sure if the maintenance of code for old boards such as Beaglebone
> Black is
> > still actively persuaded.Trying to report the observations
> >
> > --
> > Code/Output :
> > ---
> > U-Boot SPL 2021.07-rc1-00179-g8ddaf94358 (May 03 2021 - 15:36:38 +0530)
> > Trying to boot from MMC1
> >
> >
> > U-Boot 2021.07-rc1-00179-g8ddaf94358 (May 03 2021 - 15:36:38 +0530)
> >
> > CPU  : AM335X-GP rev 2.1
> > Model: TI AM335x BeagleBone Black
> > DRAM:  512 MiB
> > WDT:   Started with servicing (60s timeout)
> > NAND:  0 MiB
> > MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> > Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
> >  not set. Validating first E-fuse MAC
> > Net:   eth2: ethernet@4a10, eth3: usb_ether
> > Hit any key to stop autoboot:  0
> > => gpio status -a
> > Command 'gpio' failed: Error -19
> > =>
> > ---
> > Regards,
> > Adarsh
> >
>
U-Boot SPL 2021.04-rc2 (May 05 2021 - 15:00:06 +0530)
Trying to boot from MMC1


U-Boot 2021.04-rc2 (May 05 2021 - 15:00:06 +0530)

CPU  : AM335X-GP rev 2.1
Model: TI AM335x BeagleBone Black
DRAM:  512 MiB
WDT:   Started with servicing (60s timeout)
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT... OK
Net:   eth2: ethernet@4a10, eth3: usb_ether
Hit any key to stop autoboot:  0 
=> dm
dm - Driver model low level access

Usage:
dm tree  Dump driver model tree ('*' = activated)
dm uclassDump list of instances for each uclass
dm devresDump list of device resources for each device
dm drivers   Dump list of drivers with uclass and instances
dm compatDump list of drivers with compatibility strings
dm staticDump list of drivers with static platform data
=> dm tree
 Class Index  Probed  DriverName
---
 root  0  [ + ]   root_driver   root_driver
 rsa_mod_ex0  [   ]   mod_exp_sw|-- mod_exp_sw
 simple_bus0  [ + ]   simple_bus|-- ocp
 simple_bus1  [ + ]   simple_bus|   |-- l4_wkup@44c0
 simple_bus2  [   ]   simple_bus|   |   |-- segment@0
 simple_bus3  [   ]   simple_bus|   |   |-- segment@10
 simple_bus4  [ + ]   simple_bus|   |   `-- segment@20
 simple_bus5  [   ]   ti_sysc   |   |   |-- target-module@0
 simple_bus6  [   ]   simple_bus|   |   |   `-- prcm@0
 simple_bus7  [   ]   simple_bus|   |   |   |-- clocks
 clk   0  [   ]   fixed_clock   |   |   |   |   |-- 
clk_32768_ck
 clk   1  [   ]   fixed_clock   |   |   |   |   |-- 
clk_rc32k_ck
 clk   2  [   ]   fixed_clock   |   |   |   |   |-- 
virt_1920_ck
 clk   3  [   ]   fixed_clock   |   |   |   |   |-- 
virt_2400_ck
 clk   4  [   ]   fixed_clock   |   |   |

cmd:GPIO:TI: 'gpio' command Failure Error on Beaglebone Black

[Adarsh Babu Kalepalli]

Hi,

Error output "*Command 'gpio' failed: Error -19*" is occurring with "*gpio
status -a*"
command on Beaglebone Black.

The "gpio" command is proper till "U-Boot 2021.04-rc2".
Error message is noticed from subsequent releases on-wards.

Problem is noticed on u-boot versions from *U-Boot 2021.04-rc3 to U-Boot
2021.07-rc1*
The same command is  OK on "sandbox" and "rpi 0 wireless" .

Not sure if the maintenance of code for old boards such as Beaglebone Black
is
still actively persuaded.Trying to report the observations

--
Code/Output :
---
U-Boot SPL 2021.07-rc1-00179-g8ddaf94358 (May 03 2021 - 15:36:38 +0530)
Trying to boot from MMC1


U-Boot 2021.07-rc1-00179-g8ddaf94358 (May 03 2021 - 15:36:38 +0530)

CPU  : AM335X-GP rev 2.1
Model: TI AM335x BeagleBone Black
DRAM:  512 MiB
WDT:   Started with servicing (60s timeout)
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
 not set. Validating first E-fuse MAC
Net:   eth2: ethernet@4a10, eth3: usb_ether
Hit any key to stop autoboot:  0
=> gpio status -a
Command 'gpio' failed: Error -19
=>
---
Regards,
Adarsh

[cmd] clarification on syntax of 'chpart' command

[Adarsh Babu Kalepalli]

Hi,

u-boot version: U-Boot 2021.07-rc1
Board: Beaglebone Black

I was trying to verify and use 'chpart' command on Beaglebone black with an
SDHC card ( with multiple partitions ) and am unable to get its exact
syntax.Is this command applicable to
any particular category of storage devices (viz. NOR flash,NAND flash etc)??
I tried using it as in its "help output" and also other combinations,
Am I missing anything,Please suggest its correct usage.


Output Log from U-boot shell:

=> mmc list
OMAP SD/MMC: 0 (SD)
OMAP SD/MMC: 1
=> mmc dev 0
switch to partitions #0, OK
mmc0 is current device
=> mmc part

Partition Map for MMC device 0  --   Partition Type: DOS

PartStart SectorNum Sectors UUIDType
  1 2048524288  11d09956-01 0c Boot
  2 526336  524288  11d09956-02 0c
  3 1050624 524288  11d09956-03 83
  4 1574912 524288  11d09956-04 83
=> chpart mmc0:2
Device nand0 not found!
=> chpart mmc0:3
Device nand0 not found!
=> chpart mmc2
Device nand0 not found!
=> chpart
Device nand0 not found!
=> help chpart
chpart - change active partition

Usage:
chpart part-id
- change active partition (e.g. part-id = nand0,1)
=>
=> chpart part-id=mmc0
Device nand0 not found!
=> chpart part-id=mmc1
Device nand0 not found!
=> chpart part-id = mmc1
chpart - change active partition

Usage:
chpart part-id
- change active partition (e.g. part-id = nand0,1)
=>
-
Regards,
Adarsh

[cmd] Notation for "mandatory" and "optional" parameters in "help shell_cmd" output

[Adarsh Babu Kalepalli]

Hi,

When we type "help shell_command" at u-boot console.
The syntax for the command usage is displayed.

In most of the cases I noticed parameters enclosed in '[]' or/and '<>'
or just the sub-command string is provided.

>From the help of most of the commands, and on using them I observed that
parameters enclosed in
-'[]' could be optional
-'<>' could be mandatory

In some cases, the mandatory parameters were not enclosed in "<>" .
For ex.
env ask name [message] [size] - ask for environment variable
env edit name - edit environment variable
env exists name - tests for existence of variable

in the above case "name" seems to be a mandatory parameter.

Could you please let me know the notation we follow to indicate the
mandatory and optional input parameters for shell commands in their syntax
(displayed through help) ??

Regards,
Adarsh

[cmd]:"env edit" vs "env set",do we need both options for "env" command ??

[Adarsh Babu Kalepalli]

Hi,

Are'nt "env edit" vs "env set" redundant ??.
"env edit" allows modification of the environment variable value in the
next line,whereas "env set" requires the mention of the environment
variable value in the same line.

If the values for environment variables are not provided ,in either case
they would be deleted.

Can we have only one of these commands ??.

A single line description for "set" sub-command of "env" with mention to
that additional feature will provide better clarity.

Regards,
Adarsh

[cmd] "env import" command behaviour observation

[Adarsh Babu Kalepalli]

Hi ,

Exporting environment variables to a memory location and trying to import
them back.
On certain occasions,the import command is displaying errors.

Board: rpi1ModelB/sandbox
The console log (rpi1modelb) is :
-
U-Boot> env export 0x8200
U-Boot> md.b 0x8200
8200: 61 72 63 68 3d 61 72 6d 0a 62 61 75 64 72 61 74
 arch=arm.baudrat
8210: 65 3d 31 31 35 32 30 30 0a 62 6f 61 72 64 3d 72
 e=115200.board=r
8220: 70 69 0a 62 6f 61 72 64 5f 6e 61 6d 65 3d 4d 6f
 pi.board_name=Mo
8230: 64 65 6c 20 42 20 72 65 76 32 0a 62 6f 61 72 64del B
rev2.board
U-Boot> printenv filesize
filesize=1004
U-Boot> env import 0x8200
## Warning: defaulting to text format
## Info: input data size = 4100 = 0x1004
## Error: Can't overwrite "ethaddr"
himport_r: can't insert "ethaddr=b8:27:eb:bb:2d:e6" into hash table
## Error: Can't overwrite "serial#"
himport_r: can't insert "serial#=ebbb2de6" into hash table
U-Boot>

Is this expected?? or should it be raised as a BUG.
Please advise.

Regards,
Adarsh

Re: [U-Boot] [BUG] cmd : 'env exists envvar' does not display the existence of environment variable

[Adarsh Babu Kalepalli]

  Hello Wolfgang Denk,

It's my mistake to tag this observation as a bug.
I will take care such thing does not repeat .

Could you *please clarify* couple of my queries* regarding posting
questions* to the mailing list.

+ Most of the postings in the mailing list are observed to be code patches.
Could we also post our observations/opinions on the code/commands/issues on
a particular u-boot release and
discuss with other u-boot contributors??
If yes, is there any specific string (similar to [PATCH] for a patch or a
[BUG] for a bug etc) to be mentioned in the subject line??

I posted the below two queries earlier (first one yesterday and second one
during last month)

1.[U-Boot] cmd: clarification on 'env ask' command execution
2.Unable to delete the hush shell local variables

Both of them were not forwarded by the moderator (not sure what was wrong ).
I re-sent the second query yesterday to the mailing list with subject line
"*[U-Boot] [BUG] cmd : Local Hush Variable Could not be deleted* "
and it got forwarded.

So, any specific guidelines to post queries/observations/bugs for
discussion will be definitely helpful
and keep us going.

+ For newbies, could you  suggest any pre-requisites, initial documents or
guidelines to follow while they
explore u-boot ( from user/tester/developer perspective ).

Regards,
Adarsh



<https://www.avast.com/en-in/recommend?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=default3=263e577d-8a0d-4805-aed0-c94705b9fd3a>
I’m
protected online with Avast Free Antivirus. Get it here — it’s free forever.
<https://www.avast.com/en-in/recommend?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=default3=263e577d-8a0d-4805-aed0-c94705b9fd3a>
<#m_6203331441722922600_m_-6344178679015369129_m_4688685467448139936_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, Oct 14, 2019 at 4:06 PM Wolfgang Denk  wrote:

> Dear Adarsh Babu Kalepalli,
>
> you should not flag your postings with a BUG marker if you simply
> domn't understand how to use the tools.  Please do this only when
> you are really sure there is a misbehaviour.
>
> In message  n...@mail.gmail.com> you wrote:
> >
> > 'env exists env_varName' does not display the existance
> > status of 'env_varName' environment variable.
>
> Which part of the documention states that it should _display_ such a
> status?
>
> > env exists name - tests for existence of variable
>
> This says it "tests", but it does say nothing obout outputting any
> such information.  The command to output such information is "env
> print".
>
> > => printenv ver
> > ver=U-Boot 2019.10 (Oct 14 2019 - 00:47:50 -0700)
> > => env exists ver
> > =>
> > -
> >
> > What is the expected Output and where is the result updated??
>
> Above behaviour is absolutely correct.  The command returns a
> proper status which can be used in conditionals etc., for example:
>
> U-Boot> env exists foo ; echo RC=$?
> RC=1
> U-Boot> if env exists bootdelay ; then echo BOOTDELAY exists ; else echo
> BOOTDELAY does not exist ; fi
> BOOTDELAY exists
> U-Boot> if env exists bootdelay ; then echo BOOTDELAZ exists ; else echo
> BOOTDELAZ does not exist ; fi
> BOOTDELAZ exists
> U-Boot> env exists bootdelay && printenv bootdelay
> bootdelay=3
>
>
> There is no bug.
>
> 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: w...@denx.de
> You don't need a weatherman to know which way the wind blows.
>   - Bob Dylan
>

<https://www.avast.com/en-in/recommend?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=default3=263e577d-8a0d-4805-aed0-c94705b9fd3a>
I’m
protected online with Avast Free Antivirus. Get it here — it’s free forever.
<https://www.avast.com/en-in/recommend?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=default3=263e577d-8a0d-4805-aed0-c94705b9fd3a>
<#m_6203331441722922600_m_-6344178679015369129_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] cmd: clarification on 'env ask' command execution

[Adarsh Babu Kalepalli]

Hi,

'help env' gives  usage for 'ask' option as :

"env ask name [message] [size] - ask for environment variable"

How are the optional parameters [message] and
[size] related to env variable 'name' ??

When I execute 'env' with option 'ask' and do not enter any value for the
environment variable, it is deleted.

---
=> printenv vendor
vendor=ti
=> env ask vendor
Please enter 'vendor': texasInstruments
=> printenv vendor
vendor=texasInstruments
=> env ask vendor
Please enter 'vendor':
=> printenv vendor
## Error: "vendor" not defined
=>
---
In this case,is it expected that the environment variable gets deleted??

Regards,
Adarsh
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] [BUG] cmd : Local Hush Variable Could not be deleted

[Adarsh Babu Kalepalli]

 Hello Wolfgang Denk,

> => localvar=
> => showvar
> HUSH_VERSION=0.01
> target=pxe
> devnum=1
> localvar=hello

When 'localvar' is assigned an empty value , the 'showvar' command
displays the previously assigned 'hello'.

How do we set an empty value to a hush shell local variable ??

Regards,
Adarsh

On Mon, Oct 14, 2019 at 3:58 PM Wolfgang Denk  wrote:

> Dear Adarsh Babu Kalepalli,
>
> In message <
> cajgxa7c150ova0bhprowuizg+dvlrrerbqaoj96qxkwhhhz...@mail.gmail.com> you
> wrote:
> >
> > How do I delete a hush-shell local variable??
>
> You cannot.  Local variables can be set to an empty value, but they
> cannot be deleted.
>
> Note that there is no functional difference between a non-existing
> local variable and one with an empty value anyway.  Same as in other
> shells.
>
> 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: w...@denx.de
> Carelessly planned projects take three times longer to complete  than
> expected.  Carefully  planned  projects  take  four  times  longer to
> complete than expected, mostly  because  the  planners  expect  their
> planning to reduce the time it takes.
>
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] [BUG] cmd : 'env exists envvar' does not display the existence of environment variable

[Adarsh Babu Kalepalli]

Hi,

u-boot Version: 2019.10
H/W Board : Beaglebone Black

'env exists env_varName' does not display the existance
status of 'env_varName' environment variable.

-
=> help env
env - environment handling commands

Usage:
env ask name [message] [size] - ask for environment variable
env default [-f] -a - [forcibly] reset default environment
env default [-f] var [...] - [forcibly] reset variable(s) to their default
values
env delete [-f] var [...] - [forcibly] delete variable(s)
env edit name - edit environment variable
env exists name - tests for existence of variable
env export [-t | -b | -c] [-s size] addr [var ...] - export environment
env import [-d] [-t [-r] | -b | -c] addr [size] [var ...] - import
environment
env print [-a | name ...] - print environment
env print -e [name ...] - print UEFI environment
env run var [...] - run commands in an environment variable
env save - save environment
env set -e name [arg ...] - set UEFI variable; unset if 'arg' not specified
env set [-f] name [arg ...]

=> printenv ver
ver=U-Boot 2019.10 (Oct 14 2019 - 00:47:50 -0700)
=> env exists ver
=>
-

What is the expected Output and where is the result updated??

-Adarsh


I’m
protected online with Avast Free Antivirus. Get it here — it’s free forever.

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] [BUG] cmd : Local Hush Variable Could not be deleted

[Adarsh Babu Kalepalli]

Hi,

+ u-boot version:2019.10
+ H/W Board : Beaglebone Black

With 'localvar=' at the shell prompt
, I tried to delete a existing Hush-shell local variable.


-
=> localvar=hello
=> showvar
HUSH_VERSION=0.01
target=pxe
devnum=1
localvar=hello
=> localvar=
=> showvar
HUSH_VERSION=0.01
target=pxe
devnum=1
localvar=hello
--

The 'localvar' still exists and is not deleted.
How do I delete a hush-shell local variable??

-Adarsh





I’m
protected online with Avast Free Antivirus. Get it here — it’s free forever.

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] arm am335x: SATA Drive connectivity over USB interface

[Adarsh Babu Kalepalli]

Hi,

u-boot Version: 2019.10-rc4
u-boot config : am335x-evm-defconfig
h/w Board: Beaglebone Black

Using a SATA-USB converter, 180GB SATA disk is interfaced with Beaglebone
Black.
Unable to initialze and access the device with "usb start" and other usb
command options.

Serial Console output of 'usb start' command:

---
BBB=> usb start
starting USB...
Bus usb@47401800: Port not available.
---

Beaglebone Linux environment identifies this SATA disk over USB interface.

Are additional config options required by u-boot??If yes, please let us
know.

Regards,
Adarsh


I’m
protected online with Avast Free Antivirus. Get it here — it’s free forever.

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] 'size/ext4size/fatsize' shell commands do not dispay the filesize

[Adarsh Babu Kalepalli]

Hello,

Commands "size / ext4size / fatsize" do not display the file size.



+ u-boot version:2019.10-rc4
+ H/W Board : Beaglebone Black
+ Command Causing Issue: size/ext4size/fatsize


+ Command Output: Size of the mentioned file is not displayed on serial
console.

Console Output from Beaglebone Black for usb and mmc devices :

=> fatls usb 0:1
 1024   1kB.txt
  1048576   1MB.txt

2 file(s), 0 dir(s)

=> fatsize usb 0:1  1MB.txt
=> size usb 0:1  1MB.txt
=> size
size - determine a file's size

Usage:
size   
- Find file 'filename' from 'dev' on 'interface'
  and determine its size.
=> ext4ls mmc 0:2
   4096 .
   4096 ..
   4096 bin
   4096 boot
   4096 dev
   4096 etc
   4096 home
   4096 lib
   4096 media
   4096 mnt
   4096 proc
   4096 run
   4096 sbin
   4096 sys
  8 tmp
   4096 usr
   4096 var
1024 test_data
=> ext4size mmc 0:2 /test_data
=> size mmc 0:2  /test_data
=>


- Adarsh


I’m
protected online with Avast Free Antivirus. Get it here — it’s free forever.

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

[U-Boot] Unable to delete the hush shell local variables

[Adarsh Babu Kalepalli]

Hi,

+ u-boot version:2019.10-rc4
+ H/W Board : Beaglebone Black
+ Issue : Unable to delete the hush shell local variables


with 'local_variable_name=' at the shell prompt
(similar to 'setenv env_variable_name'),I tried to
delete a Hush shell local variable after creating it.

This approach did not delete (as in the below sequence of
shell commands)  the local variable.
-
=> hushVar=3
=> showvar
HUSH_VERSION=0.01
hushVar=3
=> hushvar=
=> showvar
HUSH_VERSION=0.01
hushVar=3
=>
--

Is there a other approach to delete hush shell local variables ??
Any pointers to detailed information regarding Hush Shell Scripts will also
be helpful.

-Adarsh


I’m
protected online with Avast Free Antivirus. Get it here — it’s free forever.

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot