Re: [beagleboard] BeagleBoard XM rev c Boot Issue

[John Syn]

From:  pavan 
Reply-To:  "beagleboard@googlegroups.com" 
Date:  Saturday, September 6, 2014 at 11:39 PM
To:  "beagleboard@googlegroups.com" 
Subject:  [beagleboard] BeagleBoard XM rev c Boot Issue

> 
> Hello ,
> 
> 
> I recently tried compiling and booting a fresh kernel and U-boot on
> Beagleboard -Xm rev c , i get the following error during board bootup
> 
>  
> U-Boot SPL 2014.10-rc2 (Sep 06 2014 - 18:31:00)
> SPL: Please implement spl_start_uboot() for your board
> SPL: Direct Linux boot not active!
> reading u-boot.img
> spl_load_image_fat: error reading image u-boot.img, err - -1
> ### ERROR ### Please RESET the board ###
> 
> 
> Resetting the board dosen't help .
> 
> The default angstrom distro i got from factory works very fine and the board
> boots .So there is no issue with the board .Please help me regarding this .
> 
> I cloned the U-boot source via this git clone git://git.denx.de/u-boot.git
> u-boot/
Did you patch u-boot?

http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootlo
ader:U-Boot

But for the Beagle-xM you use 0001-omap3_beagle-uEnv.txt-bootz-n-fixes.patch

Regards,
John
> 
> 
> Thanks  and regards.
> 
> 
> 
> 
> 
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Are the 'modes' in the BBB documentation just history or what?

[cl]

John Syn  wrote:
> >
> >I'd love to find a document or tutorial that describes how this all
> >hangs together but there doesn't seem to be anything other than the
> >(huge) processor documentation which is vey much reference material
> >and (as I referred to above) various blogs etc. showing how to do one
> >particular thing but without any attempt to explain it.
> The pinmux section uses the register offset and in the attached
> spreadsheet, that offset is related to the P8/P9 connector pins.
> 
> The right column defines how the pins are setup in the V3.15-bone5 device
> tree.
> 
Thanks, but attachments don't work when using news group access to
gmane (or at least I don't think they do, I couldn't see anything).

Could you possibly point me at a URL for the spreadsheet or mail it to
me directly (E-Mail in header works).

-- 
Chris Green
·

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Are the 'modes' in the BBB documentation justhistory or what?

[cl]

Larry Howell  wrote:
> > I'd love to find a document or tutorial that describes how this all
> > hangs together but there doesn't seem to be anything other than the
> > (huge) processor documentation which is vey much reference material
> > and (as I referred to above) various blogs etc. showing how to do one
> > particular thing but without any attempt to explain it. 
> >
> Hi Chris,
> 
> The BBB SRM gives information about the BBB, but doen't go into details 
> about the AM3358 processor.  I'd suggest reading about pinmux in the 
> AM335x Sitara Processors Technical Reference Manual, which can be found 
> on the TI website.  Basically, there are far more I/O features than 
> pins on the processor.  Eight times more signals than pins to be 
> exact.  The modes allow selection of which one of the eight for a pin 
> you choose to use.  The TRM will provide the details on the mode that 
> enables a particular function for a specific pin. 
> 
> Searching for "pinmux" will find many documents and tools. 
> 
Hmm, yes, I know the AM335x Sitara Processors Technical Reference
Manual is the ultimate reference but it is (as I said) an absolutely
huge document and is hardly the place to start if trying to gain an
understanding of this stuff.

I do understand the concept of multiplexing, it's hardly a new idea (I
cut my microprocessor teeth on 8080s, Z80s, 6502s and RCA 1802s) and
the BBB SRM points one in the direction of how it's used on the BBB.

However very, very few of the documents I've found give any clue at
all on how the ready made IO libraries (such as the Adafruit ones) or
the device tree itself control (or map onto) the MUX configurations.

>From my past I'd sort of expect to be able to simply switch between
MUX modes by issuing a write to a register somewhere, so the Mux modes
shown in the BBB SRM would then be directly selectable but this
doesn't seem to be the way the BBB works.

-- 
Chris Green
·

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Are the 'modes' in the BBB documentation just history or what?

[Jesse Cobra]

In my custom audio cape device tree fragment the modes are setup like thus.

pinctrl-single,pins = <
0x1ac 0x00 /* mcasp0_ahclkx, OUTPUT | MODE0 */
0x194 0x20 /* mcasp0_fsx, INPUT | MODE0 */
0x190 0x20 /* mcasp0_aclkx, INPUT | MODE0 */
0x198 0x20 /* mcasp0_axr0, INPUT | MODE0 */
0x1a8 0x20 /* mcasp0_axr1, INPUT | MODE0 */
0x19c 0x02 /* mcasp0_axr2, OUTPUT | MODE2 */
0x1a4 0x02 /* mcasp0_axr3, OUTPUT | MODE2 */
>;
Ben Gamari  wrote:
> [-- text/plain, encoding 7bit, charset: ISO-8859-15, 23 lines --]
>
> c...@isbd.net writes:
>
> > In the BBB System Reference Manual the P8 and P9 pinouts are
> > documented with 7 modes for each pin which provide different uses for
> > the pins.
> >
> > All of the actual software and descriptions I can find about the BBB
> > hardware just talk about the Device Tree and Device Tree overlays.  I
> > have already (sort) begun to understand the Device Tree system and I
> > have actually done a (trivial) recompile of the Device Tree to change
> > one of the I2C clock frequencies.
> >
> > Do the modes in the manual have any relevance at all now?  I.e. can I
> > actually start the system in a specified mode?  Or are they just
> > history, or what?
> >
> If you are writing a device tree you will need to refer to the pin modes
> to configure the pinmux.
>
OK, but I can't really find out *how* the PinMux/Modes are referred to
in the device tree.  In fact it seems very difficult to find how the
entries in the Device Tree are mapped to the actual pins, I get the
feeling that it's actually rather simpler than it appears at first
sight but I'm still at the rather lost stage.

The other trouble is that if you look for 'how to enable the UARTs on
BBB' there are many ways of doing it:-

Edit the device tree in /boot/uboot/dtbs - this will (as I
understand it) remap things at boot time.

Create a Device Tree Template for just the things to change, this
'overlays' the Device Tree so is possible at run time (again, my
understanding)

Edit the uEnv.txt file, I assume this controls the above but it's
far from clear.

I'd love to find a document or tutorial that describes how this all
hangs together but there doesn't seem to be anything other than the
(huge) processor documentation which is vey much reference material
and (as I referred to above) various blogs etc. showing how to do one
particular thing but without any attempt to explain it.

--
Chris Green
·

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] kernel 2.6.37 doesn't boot on xM C

['Kai' via BeagleBoard]

Hi,

I built linux-omap-psp-2.6.37 kernel for BB xM with version 
uImage--2.6.37-r125b.2. But I stops at
Uncompressing Linux... done, booting the kernel.

I have console=ttyO2,115200n8, I tried to change kernel configuration, but 
I can not figure out.

Thanks!

Kai

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Start QT Application on bootup on Beaglebone Black

[Mahendra Gunawardena]

Below is picture of the display on bootup. Expected display output is 
overwritten by Angstrom screen 


Expected Display output


The expected display output briefly appears but is overwritten by the 
Angstrom text based image. But occasionally the expected display appears. Then 
the dynamic widgets update the screen but the static information is not 
visible. The issues appears to be timing, and if the BBB can be forced to 
start the QT application after complete bootup of BBB that would suffices 
the current needs.
 
Application is been started as a service. Below is the content of the 
service file

[Unit]
Description=QTAccelerometer GUI
After=systemd-user-sessions.service

[Service]
WorkingDirectory=/home/root/projects/qt-projects
ExecStart=/home/root/projects/qt-projects/QTAccelerometer -qws
SyslogIdentifier=QTAccelerometer
Restart=on-failure
RestartSec=5

[Install]
Alias=display-manager.service


Below are the other options tried without success

[Install]
WantedBy=multi-user.target
WantedBy=graphical.target


*References*

   - Creating Ångström System Services on BeagleBone Black 
   

I have also posted this question on Stackoverflow 

.

Thank you in advance

Mahen

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BeagleBoard XM rev c Boot Issue

[pavan B.G]

Hello John ,

I applied the patch,cross  compiled U-boot and tried but its still the same
..:(


Regards
Pavan



On 7 September 2014 13:12, John Syn  wrote:

>
> From: pavan 
> Reply-To: "beagleboard@googlegroups.com" 
> Date: Saturday, September 6, 2014 at 11:39 PM
> To: "beagleboard@googlegroups.com" 
> Subject: [beagleboard] BeagleBoard XM rev c Boot Issue
>
>
> Hello ,
>
>
> I recently tried compiling and booting a fresh kernel and U-boot on
> Beagleboard -Xm rev c , i get the following error during board bootup
>
>
> U-Boot SPL 2014.10-rc2 (Sep 06 2014 - 18:31:00)
> SPL: Please implement spl_start_uboot() for your board
> SPL: Direct Linux boot not active!
> reading u-boot.img
> spl_load_image_fat: error reading image u-boot.img, err - -1
> ### ERROR ### Please RESET the board ###
>
>
> Resetting the board dosen't help .
>
> The default angstrom distro i got from factory works very fine and the
> board boots .So there is no issue with the board .Please help me regarding
> this .
>
> I cloned the U-boot source via this *git clone
> git://git.denx.de/u-boot.git  u-boot/*
>
> Did you patch u-boot?
>
>
> http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot
>
> But for the Beagle-xM you
> use 0001-omap3_beagle-uEnv.txt-bootz-n-fixes.patch
>
> Regards,
> John
>
>
>
>
>
> *Thanks  and regards.*
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BeagleBoard XM rev c Boot Issue

[Maxim Podbereznyy]

Of course! Because changing u-boot environment variables means nothing for
SPL bootloader :)
07 Сен 2014 г. 16:11 пользователь "pavan B.G"  написал:

> Hello John ,
>
> I applied the patch,cross  compiled U-boot and tried but its still the
> same ..:(
>
>
> Regards
> Pavan
>
>
>
> On 7 September 2014 13:12, John Syn  wrote:
>
>>
>> From: pavan 
>> Reply-To: "beagleboard@googlegroups.com" 
>> Date: Saturday, September 6, 2014 at 11:39 PM
>> To: "beagleboard@googlegroups.com" 
>> Subject: [beagleboard] BeagleBoard XM rev c Boot Issue
>>
>>
>> Hello ,
>>
>>
>> I recently tried compiling and booting a fresh kernel and U-boot on
>> Beagleboard -Xm rev c , i get the following error during board bootup
>>
>>
>> U-Boot SPL 2014.10-rc2 (Sep 06 2014 - 18:31:00)
>> SPL: Please implement spl_start_uboot() for your board
>> SPL: Direct Linux boot not active!
>> reading u-boot.img
>> spl_load_image_fat: error reading image u-boot.img, err - -1
>> ### ERROR ### Please RESET the board ###
>>
>>
>> Resetting the board dosen't help .
>>
>> The default angstrom distro i got from factory works very fine and the
>> board boots .So there is no issue with the board .Please help me regarding
>> this .
>>
>> I cloned the U-boot source via this *git clone
>> git://git.denx.de/u-boot.git  u-boot/*
>>
>> Did you patch u-boot?
>>
>>
>> http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot
>>
>> But for the Beagle-xM you
>> use 0001-omap3_beagle-uEnv.txt-bootz-n-fixes.patch
>>
>> Regards,
>> John
>>
>>
>>
>>
>>
>> *Thanks  and regards.*
>>
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BeagleBoard XM rev c Boot Issue

[pavan B.G]

Hi Maxim ,

Please let me know how to proceed further ???

On 7 September 2014 18:56, Maxim Podbereznyy  wrote:

> Of course! Because changing u-boot environment variables means nothing for
> SPL bootloader :)
> 07 Сен 2014 г. 16:11 пользователь "pavan B.G"  написал:
>
> Hello John ,
>>
>> I applied the patch,cross  compiled U-boot and tried but its still the
>> same ..:(
>>
>>
>> Regards
>> Pavan
>>
>>
>>
>> On 7 September 2014 13:12, John Syn  wrote:
>>
>>>
>>> From: pavan 
>>> Reply-To: "beagleboard@googlegroups.com" 
>>> Date: Saturday, September 6, 2014 at 11:39 PM
>>> To: "beagleboard@googlegroups.com" 
>>> Subject: [beagleboard] BeagleBoard XM rev c Boot Issue
>>>
>>>
>>> Hello ,
>>>
>>>
>>> I recently tried compiling and booting a fresh kernel and U-boot on
>>> Beagleboard -Xm rev c , i get the following error during board bootup
>>>
>>>
>>> U-Boot SPL 2014.10-rc2 (Sep 06 2014 - 18:31:00)
>>> SPL: Please implement spl_start_uboot() for your board
>>> SPL: Direct Linux boot not active!
>>> reading u-boot.img
>>> spl_load_image_fat: error reading image u-boot.img, err - -1
>>> ### ERROR ### Please RESET the board ###
>>>
>>>
>>> Resetting the board dosen't help .
>>>
>>> The default angstrom distro i got from factory works very fine and the
>>> board boots .So there is no issue with the board .Please help me regarding
>>> this .
>>>
>>> I cloned the U-boot source via this *git clone
>>> git://git.denx.de/u-boot.git  u-boot/*
>>>
>>> Did you patch u-boot?
>>>
>>>
>>> http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot
>>>
>>> But for the Beagle-xM you
>>> use 0001-omap3_beagle-uEnv.txt-bootz-n-fixes.patch
>>>
>>> Regards,
>>> John
>>>
>>>
>>>
>>>
>>>
>>> *Thanks  and regards.*
>>>
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>  --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: LVDS for the BB Black .. what is available

[Kumar Abhishek]

This is a standard 4-wire resistive touchscreen there. You would probably 
just need to identify the X-axis and the Y-axis pins and hook them up to 
the ADC inputs of the BBB which can also control a touchscreen IIRC.

On Sunday, September 7, 2014 5:20:06 AM UTC+5:30, Pete Lancashire wrote:
>
> I've just acquired a few NEC 1024x768 LCD panels with a LVDS interface
>
> http://www.beyondinfinite.com/lcd/Library/Nec/NL10276BC12-02.pdf
>
> They also have a yet to be identified touch panel
>
>
> https://plus.google.com/u/0/photos/111617808980322733757/albums/6056105788778128721
>
> Is there a LVDS cape for the Black  that I could use the panel on ?
>
> Thanks
>
> -pete
>
>
>
>
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Issue getting DS18B20 temperature sensor working

[Michaël Vaes]

Hi JrBenito -

Looks like something went wrong with my schematic, I'm actually using a 
4.7k resistor as described in the Maxim datasheet.  However I tried with a 
1k one but with the same result.  Is there any way to see the RAW 
inputs/outputs on a pin?

Thanks!
*Michael*


On Saturday, September 6, 2014 5:25:03 PM UTC+2, JrBenito wrote:
>
>
> Hi Michaël,
>
> Are you using 18ohm pull up resistor as your wiring diagram states? If so 
> this resistor is too low for pull up; both bone and sensor will have to 
> sink a lot of current to drive the line down.
>
> See this discussion here:
>
> https://groups.google.com/forum/#!topic/beaglebone/dosKmEE7xso
>
> Gerald told a beaglebone pin can sink around 6mA, but using Ohm's Law to 
> find current over a 18ohms resistor while driven by 3.3V voltage source we 
> find 0.183A or 183mA. The discussion pointed above talk  about 1K resistor, 
> this would result in 3.3/1000 = 0.0033 or 3.3mA.
>
> Your beaglebone and sensor might have not enough strength to hold the Data 
> line down (GND) and because of this there is no communication. This also 
> can damage the bone pin, so for test try another pin with 1k resistor pull 
> up.
>
> Regards,
> Benito
>
> On Sat, Sep 6, 2014 at 10:10 AM, Michaël Vaes  > wrote:
>
>> Changing the OS to Ubuntu did not change the behaviour.
>> Any help is appreciated on debugging this.
>>
>> Thanks!
>> *Michael*
>>
>>
>> On Saturday, August 30, 2014 1:01:18 PM UTC+2, Michaël Vaes wrote:
>>>
>>> Hi -
>>>
>>> I'm stuck getting my DS18B20 temperature sensor working on my Beaglebone 
>>> Black.  I installed and loaded the DTC overlay but Im not getting the '28-*'
>>> files in my '/sys/devices/w1_bus_master1/' directory.
>>>
>>> *Wiring*
>>> https://dl.dropboxusercontent.com/u/97513059/ds18b20-
>>> temperature-sensor.pdf
>>>
>>
>
>
>
> --
> *Josenivaldo Benito Jr.*
> *PU2LBD*
>
> *Por Aurélio Buarque de Hollanda,  elite, do francês élite, significa “o 
> que há de melhor em uma sociedade, minoria prestigiada, constituída pelos 
> indivíduos mais aptos”.
>  

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Issue getting DS18B20 temperature sensor working

[Michaël Vaes]

Output when overlay enabled but no devices found.

   /sys/devices/w1_bus_master1/w1_master_add: write device 
id xx- to add slave
  /sys/devices/w1_bus_master1/w1_master_attempts: 61
   /sys/devices/w1_bus_master1/w1_master_max_slave_count: 10
  /sys/devices/w1_bus_master1/w1_master_name: w1_bus_master1
   /sys/devices/w1_bus_master1/w1_master_pointer: 0xdf1eda70
/sys/devices/w1_bus_master1/w1_master_pullup: 1
/sys/devices/w1_bus_master1/w1_master_remove: write device 
id xx- to remove slave
/sys/devices/w1_bus_master1/w1_master_search: -1
   /sys/devices/w1_bus_master1/w1_master_slave_count: 0
/sys/devices/w1_bus_master1/w1_master_slaves: not found.
   /sys/devices/w1_bus_master1/w1_master_timeout: 10


On Saturday, August 30, 2014 1:01:18 PM UTC+2, Michaël Vaes wrote:
>
> Hi -
>
> I'm stuck getting my DS18B20 temperature sensor working on my Beaglebone 
> Black.  I installed and loaded the DTC overlay but Im not getting the '28-*'
> files in my '/sys/devices/w1_bus_master1/' directory.
>
> *Wiring*
> https://dl.dropboxusercontent.com/u/97513059/ds18b20-temperature-sensor.pdf
>
> *Software*
> Debian 7.6
> Kernel: 3.8.13-bone50
>
> *My sensor:* http://www.mouser.com/ds/2/256/DS18B20-28978.pdf
> *My DTS file:* http://pastebin.com/ma7qd6HK
>
> *Latest version of dtc: *https://raw.githubusercontent.com/RobertCNelson/
> tools/master/pkgs/dtc .sh 
>
> *Install*
> root@bbb:~# cat one-wire-temp-sensor_p8-11.sh
> #!/bin/bash
> #
> # BBB One Wire Temperature sensor (DS18B20)
> #
>
> sName='w1';
> sInput=$sName'.dts';
> sOutput=${sName:0:16}'-00A0.dtbo';
>
>
> # Build
> /usr/local/bin/dtc -O dtb -o "$sOutput" -b 0 -@ "$sInput";
> cp $sOutput /lib/firmware/;
> echo "$sName" > /sys/devices/bone_capemgr.9/slots;
>
> *GPIO's*
> Pin P8.11 gets high, when I test the voltage it's 3.3VDC.
> root@bbb:~# cat /sys/kernel/debug/gpio
> GPIOs 0-31, gpio:
>  gpio-6   (mmc_cd  ) in  lo
>
> GPIOs 32-63, gpio:
>  gpio-45  (w1  ) in  hi
>  gpio-52  (eMMC_RSTn   ) out lo
>  gpio-53  (beaglebone:green:usr) out lo
>  gpio-54  (beaglebone:green:usr) out lo
>  gpio-55  (beaglebone:green:usr) out hi
>  gpio-56  (beaglebone:green:usr) out lo
>
> GPIOs 64-95, gpio:
>
> GPIOs 96-127, gpio:
>
> *Overlays*
> HDMI disabled, w1 overlay loaded
> root@bbb:~# cat /sys/devices/bone_capemgr.9/slots
>  0: 54:PF---
>  1: 55:PF---
>  2: 56:PF---
>  3: 57:PF---
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART1
>  8: ff:P-O-L Override Board Name,00A0,Override Manuf,w1
>
> *dmesg*
> root@bbb:~# dmesg | tail -n11
> [  167.078501] bone-capemgr bone_capemgr.9: part_number 'w1', version 
> 'N/A'
> [  167.078681] bone-capemgr bone_capemgr.9: slot #8: generic override
> [  167.078726] bone-capemgr bone_capemgr.9: bone: Using override eeprom 
> data at slot 8
> [  167.078775] bone-capemgr bone_capemgr.9: slot #8: 'Override Board 
> Name,00A0,Override Manuf,w1'
> [  167.079020] bone-capemgr bone_capemgr.9: slot #8: Requesting part 
> number/version based 'w1-00A0.dtbo
> [  167.079067] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware 
> 'w1-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
> [  167.082029] bone-capemgr bone_capemgr.9: slot #8: dtbo 'w1-00A0.dtbo' 
> loaded; converting to live tree
> [  167.082504] bone-capemgr bone_capemgr.9: slot #8: #2 overlays
> [  167.089775] of_get_named_gpio_flags exited with status 45
> [  167.089820] of_get_named_gpio_flags: can't parse gpios property
> [  167.097793] bone-capemgr bone_capemgr.9: slot #8: Applied #2 overlays.
>
> *Tryouts without success*
>
>- Reboots :o)
>- Using another temperature sensor
>- Updating the OS
>- Changing the DTS file to use another pin like 'P9.22'
>   - 
>   
> http://hipstercircuits.com/dallas-one-wire-temperature-reading-on-beaglebone-black-with-dto/
>   - Changing 'gpios = <&gpio2 13 0>;' to 'gpios = <&gpio1 13 0>;'
>
> *What concerns me and where I cannot seem to get rid of in dmesg ...

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBB Rev C: Debian: PureJavaComm/JNA test fails

[maxmike]

Can't figure out why people trash Java (my language is better than yours 
thing;) the key driver of Java is its library - it has no peer!

On Thursday, July 31, 2014 9:15:04 AM UTC-7, William Hermans wrote:
>
> Datenheld, My point was why use a language, when if key feature is taken 
> away . . . also it is not very proficient especially considering you've 
> spent how many days here trying to troubleshoot an issue that should never 
> have existed ? People who write libraries that brake key features in 
> languages such as this should be shot.
>
> I could go on all day, but THIS is one reason why Java is a horrible 
> language.  People are taught to write sloppy / crappy code like this, and 
> told  that it's fine / good. It's not fine, when you break a key feature in 
> a language.
>
> Anyway, do not take the above personally. but please do try to expand your 
> horizons some.  
>
>
> On Thu, Jul 31, 2014 at 8:39 AM, Datenheld  > wrote:
>
>> Maybe you are very proficient in java and many of its libraries. It has 
>> got some really nice features. I never cared about the platform indepence 
>> that much. Many, many people worldwise use it and are proficient in it and 
>> there are lots of libraries available.
>>
>> Am Donnerstag, 31. Juli 2014 17:28:00 UTC+2 schrieb William Hermans:
>>>
>>> So what is the point of using Java if binaries like this do not work 
>>> cross platform ?
>>>
>>>
>>> On Thu, Jul 31, 2014 at 7:12 AM, Datenheld  wrote:
>>>
 Uhm, to correct myself: It's probably not even necessary to implement 
 the Java part of JTermios, the wrapper. Just make sure you build the 
 native 
 binary for arm with softfp. I suspect that the one you use has been built 
 for i386.

 You can use the linaro toolchain to crosscompile it on windows or 
 compile it directly on the bone.

 -- 
 For more options, visit http://beagleboard.org/discuss
 --- 
 You received this message because you are subscribed to the Google 
 Groups "BeagleBoard" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to beagleboard...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>  -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BeagleBone Black switching to 3.14 kernel

[Brent]

Thanks for the update Jason... I didn't realize the kernel repo had moved - 
I was wondering why there wasn't much activity recently!  I was looking at 
the 3.8 branch and noticed that Robert had added SGX... it would appear 
that 3.8 will also now have SGX working, not only 3.14, right?  I didn't 
see any commits regarding DMA for USB though...

On Sunday, August 17, 2014 9:26:34 PM UTC-4, Jason Kridner wrote:
>
> It is time to make another big software push for BeagleBone Black. We 
> have several recent updates from Robert, including managing the kernel 
> as Debian packages. 
>
> To try out the new code, use one of the recent images from: 
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-08-05 
>
> Then, you'll need to switch to the 3.14 kernel: 
> sudo apt-get update ; sudo apt-get install linux-image-3.14.17-ti-r10 
>
> Report issues to one of these trackers: 
> https://github.com/beagleboard/linux 
> http://bugs.elinux.org/projects/debian-image-releases 
>
> The device tree overlay support is still under development as is 
> built-in 'config-pin/cape-universal' support, so static configuration 
> of the .dtb is currently required. Your help is requested to make sure 
> the default .dtb file includes as many configurations as possible that 
> can be enabled from userspace. 
>
> Update summary: 
> * Repo moved to https://github.com/beagleboard/linux 
> * Layout of Debian images now enable 'apt-get' updates to the kernel, 
> but you need to grab a newer starting distro image 
> * The false-start on the cape-firmware repo has been abandoned and 
> device tree overlays are now part of the kernel tree 
> * The kernel currently uses DMA for the USB and includes SGX support 
>
> I've setup a buildbot hosted at http://builds.beagleboard.org, but I'm 
> still working on getting it to handle pull requests, multiple 
> branches, etc. like the MachineKit folks are doing, as well as pushing 
> out the builds. 
>
> After a bit more feedback, I'll push out some blog posts, etc. to get 
> more people involved. Thanks for your help! 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBB Rev C: Debian: PureJavaComm/JNA test fails

[William Hermans]

>
> *Can't figure out why people trash Java (my language is better than yours
> thing;) the key driver of Java is its library - it has no peer!*


And yet, here you are continuing the argument. Ignoring the fact that
countless other languages have equal ( maybe even bigger / better )
Libraries. I would like you to think about a few things.

1) How much storage space does Java cost you to run your application(s)?
2) How much processor time does the JVM eat up in addition to your own
application(s)?
3) How much memory does the JVM use in addition to your application(s), and
how much memory does it take to run your application(s)?
4) How performant is your application using Java as compared to the same
application using another language ?

All of the above tie to efficiency, and can have multiple effects on
various different aspects while running an embedded system over time. Most
certainly there is more to consider as well.

On Sun, Sep 7, 2014 at 1:25 PM, maxmike  wrote:

> Can't figure out why people trash Java (my language is better than yours
> thing;) the key driver of Java is its library - it has no peer!
>
> On Thursday, July 31, 2014 9:15:04 AM UTC-7, William Hermans wrote:
>>
>> Datenheld, My point was why use a language, when if key feature is taken
>> away . . . also it is not very proficient especially considering you've
>> spent how many days here trying to troubleshoot an issue that should never
>> have existed ? People who write libraries that brake key features in
>> languages such as this should be shot.
>>
>> I could go on all day, but THIS is one reason why Java is a horrible
>> language.  People are taught to write sloppy / crappy code like this, and
>> told  that it's fine / good. It's not fine, when you break a key feature in
>> a language.
>>
>> Anyway, do not take the above personally. but please do try to expand
>> your horizons some.
>>
>>
>> On Thu, Jul 31, 2014 at 8:39 AM, Datenheld  wrote:
>>
>>> Maybe you are very proficient in java and many of its libraries. It has
>>> got some really nice features. I never cared about the platform indepence
>>> that much. Many, many people worldwise use it and are proficient in it and
>>> there are lots of libraries available.
>>>
>>> Am Donnerstag, 31. Juli 2014 17:28:00 UTC+2 schrieb William Hermans:

 So what is the point of using Java if binaries like this do not work
 cross platform ?


 On Thu, Jul 31, 2014 at 7:12 AM, Datenheld  wrote:

> Uhm, to correct myself: It's probably not even necessary to implement
> the Java part of JTermios, the wrapper. Just make sure you build the 
> native
> binary for arm with softfp. I suspect that the one you use has been built
> for i386.
>
> You can use the linaro toolchain to crosscompile it on windows or
> compile it directly on the bone.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google
> Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to beagleboard...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

  --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Are the 'modes' in the BBB documentation just history or what?

[John Syn]

On 9/7/14, 2:07 AM, "c...@isbd.net"  wrote:

>John Syn  wrote:
>> >
>> >I'd love to find a document or tutorial that describes how this all
>> >hangs together but there doesn't seem to be anything other than the
>> >(huge) processor documentation which is vey much reference material
>> >and (as I referred to above) various blogs etc. showing how to do one
>> >particular thing but without any attempt to explain it.
>> The pinmux section uses the register offset and in the attached
>> spreadsheet, that offset is related to the P8/P9 connector pins.
>> 
>> The right column defines how the pins are setup in the V3.15-bone5
>>device
>> tree.
>> 
>Thanks, but attachments don't work when using news group access to
>gmane (or at least I don't think they do, I couldn't see anything).
>
>Could you possibly point me at a URL for the spreadsheet or mail it to
>me directly (E-Mail in header works).
To explain how the spreadsheet works:

If you look at the AM335x TRM, start with the CONTROL_MODULE Registers in
Section 9.3.1. The first I/O pin is conf_gpmc_ad0 which is at offset 800h,
but the pinmux in the device tree defines this as address 0h so you always
have to subtract 800h from the offset from this table. On the right
column, you will see a reference to 9.3.1.50 which defines the mode, pull
up, pull down, etc. Now you have to use either the schematic or the BBB
SRM to map the processor pin (conf_gpmc_ad0) to a board connector pin
(P8_25).

Regards
John
>
>-- 
>Chris Green
>·
>
>-- 
>For more options, visit http://beagleboard.org/discuss
>--- 
>You received this message because you are subscribed to the Google Groups
>"BeagleBoard" group.
>To unsubscribe from this group and stop receiving emails from it, send an
>email to beagleboard+unsubscr...@googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] optargs in kernel 3.15.10-bone8

[Moscowbob]

BBB boot from tftp and nfs -
kernel:  3.15.10-bone8 
rootfs:  debian-jessie-console-armhf-2014-08-13

Hardware:
BBB A5C
Circuitco LCD4 cape
Circuitco RS232 cape

/home/rob/rootfs/boot/uEnv.txt

uname_r=3.15.10-bone8
cmdline=quiet init=/lib/systemd/systemd
*optargs="consoleblank=0"*.

I used this reference http://elinux.org/Beagleboard:BeagleBone_Black_FAQ 

 but 
the display is still blanking after 10  minutes.

Would appreciate some guidance.

Thanks
Rob
 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Are the 'modes' in the BBB documentation just history or what?

[John Stampfl]

Here is a nice spreadsheet

http://www.embedded-things.com/bbb/beaglebone-black-pin-mux-spreadsheet/


On Mon, Sep 8, 2014 at 6:15 AM, John Syn  wrote:

>
> On 9/7/14, 2:07 AM, "c...@isbd.net"  wrote:
>
> >John Syn  wrote:
> >> >
> >> >I'd love to find a document or tutorial that describes how this all
> >> >hangs together but there doesn't seem to be anything other than the
> >> >(huge) processor documentation which is vey much reference material
> >> >and (as I referred to above) various blogs etc. showing how to do one
> >> >particular thing but without any attempt to explain it.
> >> The pinmux section uses the register offset and in the attached
> >> spreadsheet, that offset is related to the P8/P9 connector pins.
> >>
> >> The right column defines how the pins are setup in the V3.15-bone5
> >>device
> >> tree.
> >>
> >Thanks, but attachments don't work when using news group access to
> >gmane (or at least I don't think they do, I couldn't see anything).
> >
> >Could you possibly point me at a URL for the spreadsheet or mail it to
> >me directly (E-Mail in header works).
> To explain how the spreadsheet works:
>
> If you look at the AM335x TRM, start with the CONTROL_MODULE Registers in
> Section 9.3.1. The first I/O pin is conf_gpmc_ad0 which is at offset 800h,
> but the pinmux in the device tree defines this as address 0h so you always
> have to subtract 800h from the offset from this table. On the right
> column, you will see a reference to 9.3.1.50 which defines the mode, pull
> up, pull down, etc. Now you have to use either the schematic or the BBB
> SRM to map the processor pin (conf_gpmc_ad0) to a board connector pin
> (P8_25).
>
> Regards
> John
> >
> >--
> >Chris Green
> >·
> >
> >--
> >For more options, visit http://beagleboard.org/discuss
> >---
> >You received this message because you are subscribed to the Google Groups
> >"BeagleBoard" group.
> >To unsubscribe from this group and stop receiving emails from it, send an
> >email to beagleboard+unsubscr...@googlegroups.com.
> >For more options, visit https://groups.google.com/d/optout.
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
John Stampfl

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Are the 'modes' in the BBB documentation just history or what?

[John Stampfl]

I hadn't googled for "pinmux" for a while:

http://roshan.info/blog/2014/03/03/beaglebone-black-pinmux-and-dts-helper/

On Mon, Sep 8, 2014 at 8:21 AM, John Stampfl  wrote:

> Here is a nice spreadsheet
>
> http://www.embedded-things.com/bbb/beaglebone-black-pin-mux-spreadsheet/
>
>
> On Mon, Sep 8, 2014 at 6:15 AM, John Syn  wrote:
>
>>
>> On 9/7/14, 2:07 AM, "c...@isbd.net"  wrote:
>>
>> >John Syn  wrote:
>> >> >
>> >> >I'd love to find a document or tutorial that describes how this all
>> >> >hangs together but there doesn't seem to be anything other than the
>> >> >(huge) processor documentation which is vey much reference material
>> >> >and (as I referred to above) various blogs etc. showing how to do one
>> >> >particular thing but without any attempt to explain it.
>> >> The pinmux section uses the register offset and in the attached
>> >> spreadsheet, that offset is related to the P8/P9 connector pins.
>> >>
>> >> The right column defines how the pins are setup in the V3.15-bone5
>> >>device
>> >> tree.
>> >>
>> >Thanks, but attachments don't work when using news group access to
>> >gmane (or at least I don't think they do, I couldn't see anything).
>> >
>> >Could you possibly point me at a URL for the spreadsheet or mail it to
>> >me directly (E-Mail in header works).
>> To explain how the spreadsheet works:
>>
>> If you look at the AM335x TRM, start with the CONTROL_MODULE Registers in
>> Section 9.3.1. The first I/O pin is conf_gpmc_ad0 which is at offset 800h,
>> but the pinmux in the device tree defines this as address 0h so you always
>> have to subtract 800h from the offset from this table. On the right
>> column, you will see a reference to 9.3.1.50 which defines the mode, pull
>> up, pull down, etc. Now you have to use either the schematic or the BBB
>> SRM to map the processor pin (conf_gpmc_ad0) to a board connector pin
>> (P8_25).
>>
>> Regards
>> John
>> >
>> >--
>> >Chris Green
>> >·
>> >
>> >--
>> >For more options, visit http://beagleboard.org/discuss
>> >---
>> >You received this message because you are subscribed to the Google Groups
>> >"BeagleBoard" group.
>> >To unsubscribe from this group and stop receiving emails from it, send an
>> >email to beagleboard+unsubscr...@googlegroups.com.
>> >For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> John Stampfl
>



-- 
John Stampfl

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Are the 'modes' in the BBB documentation just history or what?

[John Stampfl]

and of course:

https://github.com/cdsteinkuehler/beaglebone-universal-io



On Mon, Sep 8, 2014 at 8:27 AM, John Stampfl  wrote:

> I hadn't googled for "pinmux" for a while:
>
> http://roshan.info/blog/2014/03/03/beaglebone-black-pinmux-and-dts-helper/
>
> On Mon, Sep 8, 2014 at 8:21 AM, John Stampfl  wrote:
>
>> Here is a nice spreadsheet
>>
>> http://www.embedded-things.com/bbb/beaglebone-black-pin-mux-spreadsheet/
>>
>>
>> On Mon, Sep 8, 2014 at 6:15 AM, John Syn  wrote:
>>
>>>
>>> On 9/7/14, 2:07 AM, "c...@isbd.net"  wrote:
>>>
>>> >John Syn  wrote:
>>> >> >
>>> >> >I'd love to find a document or tutorial that describes how this all
>>> >> >hangs together but there doesn't seem to be anything other than the
>>> >> >(huge) processor documentation which is vey much reference material
>>> >> >and (as I referred to above) various blogs etc. showing how to do one
>>> >> >particular thing but without any attempt to explain it.
>>> >> The pinmux section uses the register offset and in the attached
>>> >> spreadsheet, that offset is related to the P8/P9 connector pins.
>>> >>
>>> >> The right column defines how the pins are setup in the V3.15-bone5
>>> >>device
>>> >> tree.
>>> >>
>>> >Thanks, but attachments don't work when using news group access to
>>> >gmane (or at least I don't think they do, I couldn't see anything).
>>> >
>>> >Could you possibly point me at a URL for the spreadsheet or mail it to
>>> >me directly (E-Mail in header works).
>>> To explain how the spreadsheet works:
>>>
>>> If you look at the AM335x TRM, start with the CONTROL_MODULE Registers in
>>> Section 9.3.1. The first I/O pin is conf_gpmc_ad0 which is at offset
>>> 800h,
>>> but the pinmux in the device tree defines this as address 0h so you
>>> always
>>> have to subtract 800h from the offset from this table. On the right
>>> column, you will see a reference to 9.3.1.50 which defines the mode, pull
>>> up, pull down, etc. Now you have to use either the schematic or the BBB
>>> SRM to map the processor pin (conf_gpmc_ad0) to a board connector pin
>>> (P8_25).
>>>
>>> Regards
>>> John
>>> >
>>> >--
>>> >Chris Green
>>> >·
>>> >
>>> >--
>>> >For more options, visit http://beagleboard.org/discuss
>>> >---
>>> >You received this message because you are subscribed to the Google
>>> Groups
>>> >"BeagleBoard" group.
>>> >To unsubscribe from this group and stop receiving emails from it, send
>>> an
>>> >email to beagleboard+unsubscr...@googlegroups.com.
>>> >For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> John Stampfl
>>
>
>
>
> --
> John Stampfl
>



-- 
John Stampfl

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Using cape .dts with latest kernel 3.15.10.

[Randy Graham]

Robert,

Thanks again for your help, everything seems to be working now.

-Randy

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[William Hermans]

$ setterm -powersave off -blank 0

On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob  wrote:

>
> BBB boot from tftp and nfs -
> kernel:  3.15.10-bone8
> rootfs:  debian-jessie-console-armhf-2014-08-13
>
> Hardware:
> BBB A5C
> Circuitco LCD4 cape
> Circuitco RS232 cape
>
> /home/rob/rootfs/boot/uEnv.txt
>
> uname_r=3.15.10-bone8
> cmdline=quiet init=/lib/systemd/systemd
> *optargs="consoleblank=0"*.
>
> I used this reference http://elinux.org/Beagleboard:BeagleBone_Black_FAQ
> 
>  but
> the display is still blanking after 10  minutes.
>
> Would appreciate some guidance.
>
> Thanks
> Rob
>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[William Hermans]

>
> errr sorry, that should only be *setterm -blank 0*
>

On Sun, Sep 7, 2014 at 6:03 PM, William Hermans  wrote:

> $ setterm -powersave off -blank 0
>
> On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob  wrote:
>
>>
>> BBB boot from tftp and nfs -
>> kernel:  3.15.10-bone8
>> rootfs:  debian-jessie-console-armhf-2014-08-13
>>
>> Hardware:
>> BBB A5C
>> Circuitco LCD4 cape
>> Circuitco RS232 cape
>>
>> /home/rob/rootfs/boot/uEnv.txt
>>
>> uname_r=3.15.10-bone8
>> cmdline=quiet init=/lib/systemd/systemd
>> *optargs="consoleblank=0"*.
>>
>> I used this reference http://elinux.org/Beagleboard:BeagleBone_Black_FAQ
>> 
>>  but
>> the display is still blanking after 10  minutes.
>>
>> Would appreciate some guidance.
>>
>> Thanks
>> Rob
>>
>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] How to properly update my application

[Frank Hunleth]

On Sat, Sep 6, 2014 at 6:57 PM, Brent Sink  wrote:

> I can't quite define it, but something seems to get corrupted.  When the
> new "corrupted" application runs, it only shows a white rectangle, rather
> than the application.  I guess I was wondering how others update their own
> software applications - if they do something similar to what I'm doing or
> if they are using opkg/apt-get/etc.  The MD5 sum may be something I could
> look into... I'm not familiar on how to implement that, but I'll do some
> research.  Thanks,
>

I've gotten frustrated with corrupt root filesystems enough that I keep
mine read-only and ping-pong the firmware updates between two partitions.
I.e., the BBB starts out booting off the rootfs in the 2nd partition
(uboot, etc are in the 1st). The updater writes the new rootfs to the 3rd
partition and then when it's done, the 3rd partition becomes the new active
one. I keep all of my application data on a writable 4th partition so that
it doesn't get overwritten by the firmware updates. This setup is a bit old
school, but it has worked well for me. I also don't usually have access to
devices to investigate corruption issues, so it can be hard to figure out
the root cause.

I use Buildroot to create my root filesystems. For an open-source project
that I'm working on, I had to put together a firmware update utility to
manage updates. It seems to work for me and for what I need on the other
project, but it's not battle tested (the battle tested one is tied to a
product). If you're interested, you can look at it here:
https://github.com/fhunleth/fwup. I just updated an example project to show
how it can be used on the BBB:
https://github.com/fhunleth/bbb-buildroot-fwup.

Frank



>
> On Sat, Sep 6, 2014 at 6:33 PM, William Hermans  wrote:
>
>> Define "something gets messed up". You're going to have to know what this
>> something *is* before solving the issue. But perhaps you could use an MD5
>> sum to verify the file ? Then when there is a mismatch you delete the
>> target file and try again ?
>>
>>
>> On Sat, Sep 6, 2014 at 3:02 PM, Brent  wrote:
>>
>>> I have a Qt application that runs at start up.  Currently, I update my
>>> application by allowing the user to press a button inside of my application
>>> which copies the updated application files from the USB drive to the eMMC.
>>>  It then sets a flag inside of a text file to "1", and reboots.  When my
>>> start up script is ran, it firsts checks the text file to see if there is a
>>> "1", and if so it overwrites the old files with the new ones and then
>>> launches the application.  This works most of the time, but there are
>>> occasions where something gets messed up and the new application does not
>>> start.
>>>
>>> I was wondering if there is a better way of updating my application.
>>>  Could I use opkg to do this, and if so, how?  Will it allow my application
>>> to be running while it is updating it?  What is the proper way to do this?
>>>  Thanks in advance for your help!
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/4FY8Owh_i_I/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> -brent
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[William Hermans]

hmm so actual that did not work for me either, which I do not know is a bug
or what so here is what I had to do.

First check output of:

*$ cat /sys/module/kernel/parameters/consoleblank*
*600*

It'll probably be 600 as above, which is ten minutes( 600 seconds ).

So . . .

*nano /boot/uEnv.txt*
and uncomment this line:
*#cmdline=quiet init=/lib/systemd/systemd*
then add at the end  *consoleblank=0*
Which gives you


*cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
reboot the beaglebone and when it comes back up.

*root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
> *0*
>


On Sun, Sep 7, 2014 at 6:07 PM, William Hermans  wrote:

> errr sorry, that should only be *setterm -blank 0*
>>
>
> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans  wrote:
>
>> $ setterm -powersave off -blank 0
>>
>> On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob  wrote:
>>
>>>
>>> BBB boot from tftp and nfs -
>>> kernel:  3.15.10-bone8
>>> rootfs:  debian-jessie-console-armhf-2014-08-13
>>>
>>> Hardware:
>>> BBB A5C
>>> Circuitco LCD4 cape
>>> Circuitco RS232 cape
>>>
>>> /home/rob/rootfs/boot/uEnv.txt
>>>
>>> uname_r=3.15.10-bone8
>>> cmdline=quiet init=/lib/systemd/systemd
>>> *optargs="consoleblank=0"*.
>>>
>>> I used this reference http://elinux.org/Beagleboard:BeagleBone_Black_FAQ
>>> 
>>>  but
>>> the display is still blanking after 10  minutes.
>>>
>>> Would appreciate some guidance.
>>>
>>> Thanks
>>> Rob
>>>
>>>
>>>  --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[William Hermans]

@Robert

I'll have you know that you've broken $optargs in the initial stage
uEnv.txt.

In case you did not know already . . .

On Sun, Sep 7, 2014 at 6:32 PM, William Hermans  wrote:

> hmm so actual that did not work for me either, which I do not know is a
> bug or what so here is what I had to do.
>
> First check output of:
>
> *$ cat /sys/module/kernel/parameters/consoleblank*
> *600*
>
> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>
> So . . .
>
> *nano /boot/uEnv.txt*
> and uncomment this line:
> *#cmdline=quiet init=/lib/systemd/systemd*
> then add at the end  *consoleblank=0*
> Which gives you
>
>
> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
> reboot the beaglebone and when it comes back up.
>
> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>> *0*
>>
>
>
> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans  wrote:
>
>> errr sorry, that should only be *setterm -blank 0*
>>>
>>
>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
>> wrote:
>>
>>> $ setterm -powersave off -blank 0
>>>
>>> On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob  wrote:
>>>

 BBB boot from tftp and nfs -
 kernel:  3.15.10-bone8
 rootfs:  debian-jessie-console-armhf-2014-08-13

 Hardware:
 BBB A5C
 Circuitco LCD4 cape
 Circuitco RS232 cape

 /home/rob/rootfs/boot/uEnv.txt

 uname_r=3.15.10-bone8
 cmdline=quiet init=/lib/systemd/systemd
 *optargs="consoleblank=0"*.

 I used this reference
 http://elinux.org/Beagleboard:BeagleBone_Black_FAQ
 
  but
 the display is still blanking after 10  minutes.

 Would appreciate some guidance.

 Thanks
 Rob


  --
 For more options, visit http://beagleboard.org/discuss
 ---
 You received this message because you are subscribed to the Google
 Groups "BeagleBoard" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to beagleboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[Jason Lange]

Hello,

I'm wondering if it would help if you changed from:

optargs="consoleblank=0"

to:

optargs=consoleblank=0

I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone Debian
Image 2014-09-04 running 3.14.17-ti-r17



On Sun, Sep 7, 2014 at 6:37 PM, William Hermans  wrote:

> @Robert
>
> I'll have you know that you've broken $optargs in the initial stage
> uEnv.txt.
>
> In case you did not know already . . .
>
> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans  wrote:
>
>> hmm so actual that did not work for me either, which I do not know is a
>> bug or what so here is what I had to do.
>>
>> First check output of:
>>
>> *$ cat /sys/module/kernel/parameters/consoleblank*
>> *600*
>>
>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>>
>> So . . .
>>
>> *nano /boot/uEnv.txt*
>> and uncomment this line:
>> *#cmdline=quiet init=/lib/systemd/systemd*
>> then add at the end  *consoleblank=0*
>> Which gives you
>>
>>
>> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
>> reboot the beaglebone and when it comes back up.
>>
>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>> *0*
>>>
>>
>>
>> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
>> wrote:
>>
>>> errr sorry, that should only be *setterm -blank 0*

>>>
>>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
>>> wrote:
>>>
 $ setterm -powersave off -blank 0

 On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob  wrote:

>
> BBB boot from tftp and nfs -
> kernel:  3.15.10-bone8
> rootfs:  debian-jessie-console-armhf-2014-08-13
>
> Hardware:
> BBB A5C
> Circuitco LCD4 cape
> Circuitco RS232 cape
>
> /home/rob/rootfs/boot/uEnv.txt
>
> uname_r=3.15.10-bone8
> cmdline=quiet init=/lib/systemd/systemd
> *optargs="consoleblank=0"*.
>
> I used this reference
> http://elinux.org/Beagleboard:BeagleBone_Black_FAQ
> 
>  but
> the display is still blanking after 10  minutes.
>
> Would appreciate some guidance.
>
> Thanks
> Rob
>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google
> Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>


>>>
>>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[William Hermans]

optargs does not work in the latest uboot file setup. I've noticed this
myself in othe situations. you have to use Robert new cmdline env variable

On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange  wrote:

> Hello,
>
> I'm wondering if it would help if you changed from:
>
> optargs="consoleblank=0"
>
> to:
>
> optargs=consoleblank=0
>
> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone Debian
> Image 2014-09-04 running 3.14.17-ti-r17
>
>
>
> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans  wrote:
>
>> @Robert
>>
>> I'll have you know that you've broken $optargs in the initial stage
>> uEnv.txt.
>>
>> In case you did not know already . . .
>>
>> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans 
>> wrote:
>>
>>> hmm so actual that did not work for me either, which I do not know is a
>>> bug or what so here is what I had to do.
>>>
>>> First check output of:
>>>
>>> *$ cat /sys/module/kernel/parameters/consoleblank*
>>> *600*
>>>
>>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>>>
>>> So . . .
>>>
>>> *nano /boot/uEnv.txt*
>>> and uncomment this line:
>>> *#cmdline=quiet init=/lib/systemd/systemd*
>>> then add at the end  *consoleblank=0*
>>> Which gives you
>>>
>>>
>>> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
>>> reboot the beaglebone and when it comes back up.
>>>
>>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
 *0*

>>>
>>>
>>> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
>>> wrote:
>>>
 errr sorry, that should only be *setterm -blank 0*
>

 On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
 wrote:

> $ setterm -powersave off -blank 0
>
> On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob  wrote:
>
>>
>> BBB boot from tftp and nfs -
>> kernel:  3.15.10-bone8
>> rootfs:  debian-jessie-console-armhf-2014-08-13
>>
>> Hardware:
>> BBB A5C
>> Circuitco LCD4 cape
>> Circuitco RS232 cape
>>
>> /home/rob/rootfs/boot/uEnv.txt
>>
>> uname_r=3.15.10-bone8
>> cmdline=quiet init=/lib/systemd/systemd
>> *optargs="consoleblank=0"*.
>>
>> I used this reference
>> http://elinux.org/Beagleboard:BeagleBone_Black_FAQ
>> 
>>  but
>> the display is still blanking after 10  minutes.
>>
>> Would appreciate some guidance.
>>
>> Thanks
>> Rob
>>
>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google
>> Groups "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

>>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[John Syn]

From:  William Hermans 
Reply-To:  "beagleboard@googlegroups.com" 
Date:  Sunday, September 7, 2014 at 7:26 PM
To:  "beagleboard@googlegroups.com" 
Subject:  Re: [beagleboard] optargs in kernel 3.15.10-bone8

> optargs does not work in the latest uboot file setup. I've noticed this myself
> in othe situations. you have to use Robert new cmdline env variable
https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_ev
m-uEnv.txt-bootz-n-fixes.patch

Looking at the u-boot patch it looks like optargs is used with both mmcargs
and nfsargs.

Regards,
John
> 
> 
> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange  wrote:
>> Hello,
>> 
>> I'm wondering if it would help if you changed from:
>> 
>> optargs="consoleblank=0"
>> 
>> to:
>> 
>> optargs=consoleblank=0
>> 
>> I use optargs=spidev.bufsiz=16382 without a hitch on BeagleBone Debian Image
>> 2014-09-04 running 3.14.17-ti-r17
>> 
>> 
>> 
>> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans  wrote:
>>> @Robert
>>> 
>>> I'll have you know that you've broken $optargs in the initial stage
>>> uEnv.txt.
>>> 
>>> In case you did not know already . . .
>>> 
>>> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans  wrote:
 hmm so actual that did not work for me either, which I do not know is a bug
 or what so here is what I had to do.
 
 First check output of:
> $ cat /sys/module/kernel/parameters/consoleblank
> 600
 It'll probably be 600 as above, which is ten minutes( 600 seconds ).
 
 So . . .
 nano /boot/uEnv.txt
 and uncomment this line:
 #cmdline=quiet init=/lib/systemd/systemd
 then add at the end  consoleblank=0
 Which gives you
 cmdline=quiet init=/lib/systemd/systemd consoleblank=0
 
 reboot the beaglebone and when it comes back up.
 
> root@arm:~# cat /sys/module/kernel/parameters/consoleblank
> 0
 
 
 On Sun, Sep 7, 2014 at 6:07 PM, William Hermans  wrote:
>> errr sorry, that should only be setterm -blank 0
> 
> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans  wrote:
>> $ setterm -powersave off -blank 0
>> 
>> On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob  wrote:
>>> 
>>> BBB boot from tftp and nfs -
>>> kernel:  3.15.10-bone8
>>> rootfs:  debian-jessie-console-armhf-2014-08-13
>>> 
>>> Hardware:
>>> BBB A5C
>>> Circuitco LCD4 cape
>>> Circuitco RS232 cape
>>> 
>>> /home/rob/rootfs/boot/uEnv.txt
>>> 
>>> uname_r=3.15.10-bone8
>>> cmdline=quiet init=/lib/systemd/systemd
>>> optargs="consoleblank=0".
>>> 
>>> I used this reference http://elinux.org/Beagleboard:BeagleBone_Black_FAQ
>>> >> event_my_HDMI_monitor_from_sleeping_while_using_my_BBB.3F>  but the
>>> display is still blanking after 10  minutes.
>>> 
>>> Would appreciate some guidance.
>>> 
>>> Thanks
>>> Rob
>>>  
>>> 
>>> 
>>> -- 
>>> For more options, visit http://beagleboard.org/discuss
>>> --- 
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
> 
 
>>> 
>>> 
>>> -- 
>>> For more options, visit http://beagleboard.org/discuss
>>> --- 
>>> You received this message because you are subscribed to the Google Groups
>>> "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> 
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> 
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[William Hermans]

Ok, so rather coming in and sniping a comment Jjohn, why dont you try and
set an optargs env variable in the initial uEnv.txt file and see what
happens.

If you're using the same uboot we're using, it wont work. Now, feel free to
find yourself trolling a different post.

On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:

>
> From: William Hermans 
> Reply-To: "beagleboard@googlegroups.com" 
> Date: Sunday, September 7, 2014 at 7:26 PM
> To: "beagleboard@googlegroups.com" 
> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>
> optargs does not work in the latest uboot file setup. I've noticed this
> myself in othe situations. you have to use Robert new cmdline env variable
>
>
> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>
> Looking at the u-boot patch it looks like optargs is used with both
> mmcargs and nfsargs.
>
> Regards,
> John
>
>
>
> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange  wrote:
>
>> Hello,
>>
>> I'm wondering if it would help if you changed from:
>>
>> optargs="consoleblank=0"
>>
>> to:
>>
>> optargs=consoleblank=0
>>
>> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone Debian
>> Image 2014-09-04 running 3.14.17-ti-r17
>>
>>
>>
>> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans 
>> wrote:
>>
>>> @Robert
>>>
>>> I'll have you know that you've broken $optargs in the initial stage
>>> uEnv.txt.
>>>
>>> In case you did not know already . . .
>>>
>>> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans 
>>> wrote:
>>>
 hmm so actual that did not work for me either, which I do not know is a
 bug or what so here is what I had to do.

 First check output of:

 *$ cat /sys/module/kernel/parameters/consoleblank*
 *600*

 It'll probably be 600 as above, which is ten minutes( 600 seconds ).

 So . . .

 *nano /boot/uEnv.txt*
 and uncomment this line:
 *#cmdline=quiet init=/lib/systemd/systemd*
 then add at the end  *consoleblank=0*
 Which gives you


 *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
 reboot the beaglebone and when it comes back up.

 *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
> *0*
>


 On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
 wrote:

> errr sorry, that should only be *setterm -blank 0*
>>
>
> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
> wrote:
>
>> $ setterm -powersave off -blank 0
>>
>> On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob 
>> wrote:
>>
>>>
>>> BBB boot from tftp and nfs -
>>> kernel:  3.15.10-bone8
>>> rootfs:  debian-jessie-console-armhf-2014-08-13
>>>
>>> Hardware:
>>> BBB A5C
>>> Circuitco LCD4 cape
>>> Circuitco RS232 cape
>>>
>>> /home/rob/rootfs/boot/uEnv.txt
>>>
>>> uname_r=3.15.10-bone8
>>> cmdline=quiet init=/lib/systemd/systemd
>>> *optargs="consoleblank=0"*.
>>>
>>> I used this reference
>>> http://elinux.org/Beagleboard:BeagleBone_Black_FAQ
>>> 
>>>  but
>>> the display is still blanking after 10  minutes.
>>>
>>> Would appreciate some guidance.
>>>
>>> Thanks
>>> Rob
>>>
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it,
>>> send an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>

>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>  --
> For more options, visit http://beagleboard.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[Jason Lange]

Hi again,

I just tried wrapping my optarg in quotes and it didn't make a lick of
difference, so that's not it.

It's seems that I should have the latest uboot since I'm running an image
from 3 days ago.
My optargs aren't broken.

On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:

>
> From: William Hermans 
> Reply-To: "beagleboard@googlegroups.com" 
> Date: Sunday, September 7, 2014 at 7:26 PM
> To: "beagleboard@googlegroups.com" 
> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>
> optargs does not work in the latest uboot file setup. I've noticed this
> myself in othe situations. you have to use Robert new cmdline env variable
>
>
> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>
> Looking at the u-boot patch it looks like optargs is used with both
> mmcargs and nfsargs.
>
> Regards,
> John
>
>
>
> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange  wrote:
>
>> Hello,
>>
>> I'm wondering if it would help if you changed from:
>>
>> optargs="consoleblank=0"
>>
>> to:
>>
>> optargs=consoleblank=0
>>
>> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone Debian
>> Image 2014-09-04 running 3.14.17-ti-r17
>>
>>
>>
>> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans 
>> wrote:
>>
>>> @Robert
>>>
>>> I'll have you know that you've broken $optargs in the initial stage
>>> uEnv.txt.
>>>
>>> In case you did not know already . . .
>>>
>>> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans 
>>> wrote:
>>>
 hmm so actual that did not work for me either, which I do not know is a
 bug or what so here is what I had to do.

 First check output of:

 *$ cat /sys/module/kernel/parameters/consoleblank*
 *600*

 It'll probably be 600 as above, which is ten minutes( 600 seconds ).

 So . . .

 *nano /boot/uEnv.txt*
 and uncomment this line:
 *#cmdline=quiet init=/lib/systemd/systemd*
 then add at the end  *consoleblank=0*
 Which gives you


 *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
 reboot the beaglebone and when it comes back up.

 *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
> *0*
>


 On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
 wrote:

> errr sorry, that should only be *setterm -blank 0*
>>
>
> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
> wrote:
>
>> $ setterm -powersave off -blank 0
>>
>> On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob 
>> wrote:
>>
>>>
>>> BBB boot from tftp and nfs -
>>> kernel:  3.15.10-bone8
>>> rootfs:  debian-jessie-console-armhf-2014-08-13
>>>
>>> Hardware:
>>> BBB A5C
>>> Circuitco LCD4 cape
>>> Circuitco RS232 cape
>>>
>>> /home/rob/rootfs/boot/uEnv.txt
>>>
>>> uname_r=3.15.10-bone8
>>> cmdline=quiet init=/lib/systemd/systemd
>>> *optargs="consoleblank=0"*.
>>>
>>> I used this reference
>>> http://elinux.org/Beagleboard:BeagleBone_Black_FAQ
>>> 
>>>  but
>>> the display is still blanking after 10  minutes.
>>>
>>> Would appreciate some guidance.
>>>
>>> Thanks
>>> Rob
>>>
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it,
>>> send an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>

>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this mes

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[John Syn]

From:  William Hermans 
Reply-To:  "beagleboard@googlegroups.com" 
Date:  Sunday, September 7, 2014 at 7:43 PM
To:  "beagleboard@googlegroups.com" 
Subject:  Re: [beagleboard] optargs in kernel 3.15.10-bone8

> Ok, so rather coming in and sniping a comment Jjohn, why dont you try and set
> an optargs env variable in the initial uEnv.txt file and see what happens.
> 
> If you're using the same uboot we're using, it wont work. Now, feel free to
> find yourself trolling a different post.
Wow, that was so unnecessary. I was just trying to be helpful.

Regards,
John
> 
> 
> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>> 
>> From:  William Hermans 
>> Reply-To:  "beagleboard@googlegroups.com" 
>> Date:  Sunday, September 7, 2014 at 7:26 PM
>> To:  "beagleboard@googlegroups.com" 
>> Subject:  Re: [beagleboard] optargs in kernel 3.15.10-bone8
>> 
>>> optargs does not work in the latest uboot file setup. I've noticed this
>>> myself in othe situations. you have to use Robert new cmdline env variable
>> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm
>> -uEnv.txt-bootz-n-fixes.patch
>> 
>> Looking at the u-boot patch it looks like optargs is used with both mmcargs
>> and nfsargs.
>> 
>> Regards,
>> John
>>> 
>>> 
>>> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange  wrote:
 Hello,
 
 I'm wondering if it would help if you changed from:
 
 optargs="consoleblank=0"
 
 to:
 
 optargs=consoleblank=0
 
 I use optargs=spidev.bufsiz=16382 without a hitch on BeagleBone Debian
 Image 2014-09-04 running 3.14.17-ti-r17
 
 
 
 On Sun, Sep 7, 2014 at 6:37 PM, William Hermans  wrote:
> @Robert
> 
> I'll have you know that you've broken $optargs in the initial stage
> uEnv.txt.
> 
> In case you did not know already . . .
> 
> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans  wrote:
>> hmm so actual that did not work for me either, which I do not know is a
>> bug or what so here is what I had to do.
>> 
>> First check output of:
>>> $ cat /sys/module/kernel/parameters/consoleblank
>>> 600
>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>> 
>> So . . .
>> nano /boot/uEnv.txt
>> and uncomment this line:
>> #cmdline=quiet init=/lib/systemd/systemd
>> then add at the end  consoleblank=0
>> Which gives you
>> cmdline=quiet init=/lib/systemd/systemd consoleblank=0
>> 
>> reboot the beaglebone and when it comes back up.
>> 
>>> root@arm:~# cat /sys/module/kernel/parameters/consoleblank
>>> 0
>> 
>> 
>> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
>> wrote:
>>> errr sorry, that should only be setterm -blank 0
>>> 
>>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
>>> wrote:
>>> $ setterm -powersave off -blank 0
>>> 
>>> On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob  wrote:
>>> 
>>> BBB boot from tftp and nfs -
>>> kernel:  3.15.10-bone8
>>> rootfs:  debian-jessie-console-armhf-2014-08-13
>>> 
>>> Hardware:
>>> BBB A5C
>>> Circuitco LCD4 cape
>>> Circuitco RS232 cape
>>> 
>>> /home/rob/rootfs/boot/uEnv.txt
>>> 
>>> uname_r=3.15.10-bone8
>>> cmdline=quiet init=/lib/systemd/systemd
>>> optargs="consoleblank=0".
>>> 
>>> I used this reference http://elinux.org/Beagleboard:BeagleBone_Black_FAQ
>>> >> event_my_HDMI_monitor_from_sleeping_while_using_my_BBB.3F>  but the
>>> display is still blanking after 10  minutes.
>>> 
>>> Would appreciate some guidance.
>>> 
>>> Thanks
>>> Rob
>>>  
>>> 
>>> 
>>> -- 
>>> For more options, visit http://beagleboard.org/discuss
>>> --- 
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> 
>> 
> 
> 
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
 
 
 -- 
 For more options, visit http://beagleboard.org/discuss
 --- 
 You received this message because you are subscribed to the Google Groups
 "BeagleBoard" group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to beagleboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.googl

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[Jason Lange]

try:
cat /proc/cmdline

to see if optargs show there




On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:

>
> From: William Hermans 
> Reply-To: "beagleboard@googlegroups.com" 
> Date: Sunday, September 7, 2014 at 7:43 PM
> To: "beagleboard@googlegroups.com" 
> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>
> Ok, so rather coming in and sniping a comment Jjohn, why dont you try and
> set an optargs env variable in the initial uEnv.txt file and see what
> happens.
>
> If you're using the same uboot we're using, it wont work. Now, feel free
> to find yourself trolling a different post.
>
> Wow, that was so unnecessary. I was just trying to be helpful.
>
> Regards,
> John
>
>
>
> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>
>>
>> From: William Hermans 
>> Reply-To: "beagleboard@googlegroups.com" 
>> Date: Sunday, September 7, 2014 at 7:26 PM
>> To: "beagleboard@googlegroups.com" 
>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>
>> optargs does not work in the latest uboot file setup. I've noticed this
>> myself in othe situations. you have to use Robert new cmdline env variable
>>
>>
>> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>>
>> Looking at the u-boot patch it looks like optargs is used with both
>> mmcargs and nfsargs.
>>
>> Regards,
>> John
>>
>>
>>
>> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange  wrote:
>>
>>> Hello,
>>>
>>> I'm wondering if it would help if you changed from:
>>>
>>> optargs="consoleblank=0"
>>>
>>> to:
>>>
>>> optargs=consoleblank=0
>>>
>>> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone
>>> Debian Image 2014-09-04 running 3.14.17-ti-r17
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans 
>>> wrote:
>>>
 @Robert

 I'll have you know that you've broken $optargs in the initial stage
 uEnv.txt.

 In case you did not know already . . .

 On Sun, Sep 7, 2014 at 6:32 PM, William Hermans 
 wrote:

> hmm so actual that did not work for me either, which I do not know is
> a bug or what so here is what I had to do.
>
> First check output of:
>
> *$ cat /sys/module/kernel/parameters/consoleblank*
> *600*
>
> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>
> So . . .
>
> *nano /boot/uEnv.txt*
> and uncomment this line:
> *#cmdline=quiet init=/lib/systemd/systemd*
> then add at the end  *consoleblank=0*
> Which gives you
>
>
> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
> reboot the beaglebone and when it comes back up.
>
> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>> *0*
>>
>
>
> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
> wrote:
>
>> errr sorry, that should only be *setterm -blank 0*
>>>
>>
>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
>> wrote:
>>
>>> $ setterm -powersave off -blank 0
>>>
>>> On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob 
>>> wrote:
>>>

 BBB boot from tftp and nfs -
 kernel:  3.15.10-bone8
 rootfs:  debian-jessie-console-armhf-2014-08-13

 Hardware:
 BBB A5C
 Circuitco LCD4 cape
 Circuitco RS232 cape

 /home/rob/rootfs/boot/uEnv.txt

 uname_r=3.15.10-bone8
 cmdline=quiet init=/lib/systemd/systemd
 *optargs="consoleblank=0"*.

 I used this reference
 http://elinux.org/Beagleboard:BeagleBone_Black_FAQ
 
  but
 the display is still blanking after 10  minutes.

 Would appreciate some guidance.

 Thanks
 Rob


 --
 For more options, visit http://beagleboard.org/discuss
 ---
 You received this message because you are subscribed to the Google
 Groups "BeagleBoard" group.
 To unsubscribe from this group and stop receiving emails from it,
 send an email to beagleboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>
>
 --
 For more options, visit http://beagleboard.org/discuss
 ---
 You received this message because you are subscribed to the Google
 Groups "BeagleBoard" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to beagleboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this gro

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[William Hermans]

Since both of you seem convinced that optargs is not broken, why dont you
actually go make changes to your own uEnv.txt and test if what you think
will work, actually works. What I did works, as I tested it myself.

On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange  wrote:

> try:
> cat /proc/cmdline
>
> to see if optargs show there
>
>
>
>
> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>
>>
>> From: William Hermans 
>> Reply-To: "beagleboard@googlegroups.com" 
>> Date: Sunday, September 7, 2014 at 7:43 PM
>> To: "beagleboard@googlegroups.com" 
>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>
>> Ok, so rather coming in and sniping a comment Jjohn, why dont you try and
>> set an optargs env variable in the initial uEnv.txt file and see what
>> happens.
>>
>> If you're using the same uboot we're using, it wont work. Now, feel free
>> to find yourself trolling a different post.
>>
>> Wow, that was so unnecessary. I was just trying to be helpful.
>>
>> Regards,
>> John
>>
>>
>>
>> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>>
>>>
>>> From: William Hermans 
>>> Reply-To: "beagleboard@googlegroups.com" 
>>> Date: Sunday, September 7, 2014 at 7:26 PM
>>> To: "beagleboard@googlegroups.com" 
>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>
>>> optargs does not work in the latest uboot file setup. I've noticed this
>>> myself in othe situations. you have to use Robert new cmdline env variable
>>>
>>>
>>> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>>>
>>> Looking at the u-boot patch it looks like optargs is used with both
>>> mmcargs and nfsargs.
>>>
>>> Regards,
>>> John
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange  wrote:
>>>
 Hello,

 I'm wondering if it would help if you changed from:

 optargs="consoleblank=0"

 to:

 optargs=consoleblank=0

 I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone
 Debian Image 2014-09-04 running 3.14.17-ti-r17



 On Sun, Sep 7, 2014 at 6:37 PM, William Hermans 
 wrote:

> @Robert
>
> I'll have you know that you've broken $optargs in the initial stage
> uEnv.txt.
>
> In case you did not know already . . .
>
> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans 
> wrote:
>
>> hmm so actual that did not work for me either, which I do not know is
>> a bug or what so here is what I had to do.
>>
>> First check output of:
>>
>> *$ cat /sys/module/kernel/parameters/consoleblank*
>> *600*
>>
>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>>
>> So . . .
>>
>> *nano /boot/uEnv.txt*
>> and uncomment this line:
>> *#cmdline=quiet init=/lib/systemd/systemd*
>> then add at the end  *consoleblank=0*
>> Which gives you
>>
>>
>> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
>> reboot the beaglebone and when it comes back up.
>>
>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>> *0*
>>>
>>
>>
>> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
>> wrote:
>>
>>> errr sorry, that should only be *setterm -blank 0*

>>>
>>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
>>> wrote:
>>>
 $ setterm -powersave off -blank 0

 On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob 
 wrote:

>
> BBB boot from tftp and nfs -
> kernel:  3.15.10-bone8
> rootfs:  debian-jessie-console-armhf-2014-08-13
>
> Hardware:
> BBB A5C
> Circuitco LCD4 cape
> Circuitco RS232 cape
>
> /home/rob/rootfs/boot/uEnv.txt
>
> uname_r=3.15.10-bone8
> cmdline=quiet init=/lib/systemd/systemd
> *optargs="consoleblank=0"*.
>
> I used this reference
> http://elinux.org/Beagleboard:BeagleBone_Black_FAQ
> 
>  but
> the display is still blanking after 10  minutes.
>
> Would appreciate some guidance.
>
> Thanks
> Rob
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google
> Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>


>>>
>>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google
> Gr

[beagleboard] Re: Welcome the Fall 2014 Beagle Class to the group

[Tim Cole]

This course *does* look interesting. Is there any way to audit the course 
-- uStream archives or something like that?
Cheers, Tim



On Friday, September 5, 2014 11:13:58 AM UTC-4, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching 
> an Embedded Linux class based on the BeagleBone Black [1].  I'm 
> teaching as open-source as I can and have have posted many of course 
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and 
> suggestions for interesting course projects.  For example we are starting
> BoneScript today and hope to be writing simple kernel module 5 weeks from 
> now.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark 
>
> --Prof. Mark A. Yoder 
>   Rose-Hulman Institute of Technology [4] 
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
> [2] http://elinux.org/index.php?title=Category:ECE597 
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
> [4]  http://www.rose-hulman.edu 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[Jason Lange]

 just added fauxarg to my optargs like this:

optargs="spidev.bufsiz=16384" fauxarg

and rebooted.  Now cat /proc/cmdline shows this:

console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
init=/lib/systemd/systemd

On Sun, Sep 7, 2014 at 7:51 PM, William Hermans  wrote:

> Since both of you seem convinced that optargs is not broken, why dont you
> actually go make changes to your own uEnv.txt and test if what you think
> will work, actually works. What I did works, as I tested it myself.
>
> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange  wrote:
>
>> try:
>> cat /proc/cmdline
>>
>> to see if optargs show there
>>
>>
>>
>>
>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>>
>>>
>>> From: William Hermans 
>>> Reply-To: "beagleboard@googlegroups.com" 
>>> Date: Sunday, September 7, 2014 at 7:43 PM
>>> To: "beagleboard@googlegroups.com" 
>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>
>>> Ok, so rather coming in and sniping a comment Jjohn, why dont you try
>>> and set an optargs env variable in the initial uEnv.txt file and see what
>>> happens.
>>>
>>> If you're using the same uboot we're using, it wont work. Now, feel free
>>> to find yourself trolling a different post.
>>>
>>> Wow, that was so unnecessary. I was just trying to be helpful.
>>>
>>> Regards,
>>> John
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>>>

 From: William Hermans 
 Reply-To: "beagleboard@googlegroups.com" 
 Date: Sunday, September 7, 2014 at 7:26 PM
 To: "beagleboard@googlegroups.com" 
 Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8

 optargs does not work in the latest uboot file setup. I've noticed this
 myself in othe situations. you have to use Robert new cmdline env variable


 https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch

 Looking at the u-boot patch it looks like optargs is used with both
 mmcargs and nfsargs.

 Regards,
 John



 On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange 
 wrote:

> Hello,
>
> I'm wondering if it would help if you changed from:
>
> optargs="consoleblank=0"
>
> to:
>
> optargs=consoleblank=0
>
> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone
> Debian Image 2014-09-04 running 3.14.17-ti-r17
>
>
>
> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans 
> wrote:
>
>> @Robert
>>
>> I'll have you know that you've broken $optargs in the initial stage
>> uEnv.txt.
>>
>> In case you did not know already . . .
>>
>> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans 
>> wrote:
>>
>>> hmm so actual that did not work for me either, which I do not know
>>> is a bug or what so here is what I had to do.
>>>
>>> First check output of:
>>>
>>> *$ cat /sys/module/kernel/parameters/consoleblank*
>>> *600*
>>>
>>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>>>
>>> So . . .
>>>
>>> *nano /boot/uEnv.txt*
>>> and uncomment this line:
>>> *#cmdline=quiet init=/lib/systemd/systemd*
>>> then add at the end  *consoleblank=0*
>>> Which gives you
>>>
>>>
>>> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
>>> reboot the beaglebone and when it comes back up.
>>>
>>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
 *0*

>>>
>>>
>>> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
>>> wrote:
>>>
 errr sorry, that should only be *setterm -blank 0*
>

 On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
 wrote:

> $ setterm -powersave off -blank 0
>
> On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob 
> wrote:
>
>>
>> BBB boot from tftp and nfs -
>> kernel:  3.15.10-bone8
>> rootfs:  debian-jessie-console-armhf-2014-08-13
>>
>> Hardware:
>> BBB A5C
>> Circuitco LCD4 cape
>> Circuitco RS232 cape
>>
>> /home/rob/rootfs/boot/uEnv.txt
>>
>> uname_r=3.15.10-bone8
>> cmdline=quiet init=/lib/systemd/systemd
>> *optargs="consoleblank=0"*.
>>
>> I used this reference
>> http://elinux.org/Beagleboard:BeagleBone_Black_FAQ
>> 
>>  but
>> the display is still blanking after 10  minutes.
>>
>> Would appreciate some guidance.
>>
>> Thanks
>> Rob
>>
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You recei

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[William Hermans]

Jason, odd, it seems to be working for me now too. Previously the cmdline
env variable was overriding my optargs statements.

*root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
> *0*
> *root@arm:~# cat /proc/cmdline*
> *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
> nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
> rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
> quiet init=/lib/systemd/systemd*
>


On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange  wrote:

> just added fauxarg to my optargs like this:
>
> optargs="spidev.bufsiz=16384" fauxarg
>
> and rebooted.  Now cat /proc/cmdline shows this:
>
> console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
> init=/lib/systemd/systemd
>
> On Sun, Sep 7, 2014 at 7:51 PM, William Hermans  wrote:
>
>> Since both of you seem convinced that optargs is not broken, why dont you
>> actually go make changes to your own uEnv.txt and test if what you think
>> will work, actually works. What I did works, as I tested it myself.
>>
>> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange  wrote:
>>
>>> try:
>>> cat /proc/cmdline
>>>
>>> to see if optargs show there
>>>
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>>>

 From: William Hermans 
 Reply-To: "beagleboard@googlegroups.com" 
 Date: Sunday, September 7, 2014 at 7:43 PM
 To: "beagleboard@googlegroups.com" 
 Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8

 Ok, so rather coming in and sniping a comment Jjohn, why dont you try
 and set an optargs env variable in the initial uEnv.txt file and see what
 happens.

 If you're using the same uboot we're using, it wont work. Now, feel
 free to find yourself trolling a different post.

 Wow, that was so unnecessary. I was just trying to be helpful.

 Regards,
 John



 On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:

>
> From: William Hermans 
> Reply-To: "beagleboard@googlegroups.com"  >
> Date: Sunday, September 7, 2014 at 7:26 PM
> To: "beagleboard@googlegroups.com" 
> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>
> optargs does not work in the latest uboot file setup. I've noticed
> this myself in othe situations. you have to use Robert new cmdline env
> variable
>
>
> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>
> Looking at the u-boot patch it looks like optargs is used with both
> mmcargs and nfsargs.
>
> Regards,
> John
>
>
>
> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange 
> wrote:
>
>> Hello,
>>
>> I'm wondering if it would help if you changed from:
>>
>> optargs="consoleblank=0"
>>
>> to:
>>
>> optargs=consoleblank=0
>>
>> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone
>> Debian Image 2014-09-04 running 3.14.17-ti-r17
>>
>>
>>
>> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans 
>> wrote:
>>
>>> @Robert
>>>
>>> I'll have you know that you've broken $optargs in the initial stage
>>> uEnv.txt.
>>>
>>> In case you did not know already . . .
>>>
>>> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans 
>>> wrote:
>>>
 hmm so actual that did not work for me either, which I do not know
 is a bug or what so here is what I had to do.

 First check output of:

 *$ cat /sys/module/kernel/parameters/consoleblank*
 *600*

 It'll probably be 600 as above, which is ten minutes( 600 seconds ).

 So . . .

 *nano /boot/uEnv.txt*
 and uncomment this line:
 *#cmdline=quiet init=/lib/systemd/systemd*
 then add at the end  *consoleblank=0*
 Which gives you


 *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
 reboot the beaglebone and when it comes back up.

 *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
> *0*
>


 On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
 wrote:

> errr sorry, that should only be *setterm -blank 0*
>>
>
> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans  > wrote:
>
>> $ setterm -powersave off -blank 0
>>
>> On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob 
>> wrote:
>>
>>>
>>> BBB boot from tftp and nfs -
>>> kernel:  3.15.10-bone8
>>> rootfs:  debian-jessie-console-armhf-2014-08-13
>>>
>>> Hardware:
>>> BBB A5C
>>> Circuitco LCD4 cape
>>> Circuitco RS232 cape
>>>
>>> /home/rob/rootfs

Re: [beagleboard] Re: Yet another newbie "how to get started"

[Tim Cole]

Once again --- thanks, folks. It's always useful to have some "trail 
markers" from explorers who've gone before. It certainly seems odd to have 
open resources that aren't just thinly veiled ads, but it seems that's not 
unusual in the Land of Linux. Who'd have guessed? :-)

(If you'll pardon the digression, I'm reminded of a joke that makes more 
sense to me now. A Windows user says, "Oh, crap! Windows is downloading 
another update!" A Linux user says, "Oh, just the usual updates." A Mac 
user says, "Oh, wow! An update! And it's only a hundred dollars!")

Cheers, Tim


On Friday, September 5, 2014 12:56:21 PM UTC-4, William Hermans wrote:
>
> You can find free legitimate reading material easily on the web. LDD ( 
> Linux Device Drivers is one example ). 
>
> Not to mention sites like 
>
> http://www.debianhelp.co.uk/ddcommand.htm and 
> https://wiki.debian.org/NetworkConfiguration
>
> Note that both those came up off of a google search, so yeah google is 
> probably the most important resource.
>
>
>
>
> On Fri, Sep 5, 2014 at 7:11 AM, Joshua Datko  > wrote:
>
>>
>>
>> Tim Cole > 
>> writes:
>>
>> > Agreed -- you can't learn a damned thing without putting in your own
>> > skull time. Perhaps I'm too distrustful of internet search engines --
>> > I like a good reference handbook. If there isn't one available, I'll
>> > just have to make do.
>>
>> By far, the number one reference on the BeagleBone Black is the System
>> Reference Manual:
>>
>> https://github.com/CircuitCo/BeagleBone-Black/blob/master/BBB_SRM.pdf?raw=true
>>
>> It's impressively complete.
>>
>> However, that mainly covers the hardware. Since hardware doesn't change
>> as often as software (although it's becoming more that way) any other
>> reference is a snapshot in time, especially for Linux resources.
>>
>> In increasing specificity, one would need (supplied with links to books
>> I like):
>>
>> - A good Linux reference
>> http://www.nostarch.com/howlinuxworks.htm
>>
>> - A good Debian reference
>> http://www.nostarch.com/debian.htm
>>
>> - A good embedded Linux reference
>> http://www.amazon.com/Linux-Embedded-Systems-Experts-Voice/dp/1430272279
>>
>> - A good Linux programming reference
>> http://www.nostarch.com/tlpi
>>
>> The difficulty in writing books on the BeagleBone is that the community
>> moves incredibly fast. This is the sign of a healthy and vibrant
>> community.
>>
>> Josh
>>
>> p.s. There are, of course, great *free* resources too. One would have to
>> use a distrustful search engine to find them :p
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[William Hermans]

For the record. in that cmdline *consoleblank=0* is declared in $optargs
and *init=/lib/systemd/systemd *is declared in* $cmdline. *

Previously I had tried disabling hdmi via optargs, so maybe that is now
different. Either way
*optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*

was not working for me



On Sun, Sep 7, 2014 at 8:08 PM, William Hermans  wrote:

> Jason, odd, it seems to be working for me now too. Previously the cmdline
> env variable was overriding my optargs statements.
>
> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>> *0*
>> *root@arm:~# cat /proc/cmdline*
>> *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
>> nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
>> rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
>> quiet init=/lib/systemd/systemd*
>>
>
>
> On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange  wrote:
>
>> just added fauxarg to my optargs like this:
>>
>> optargs="spidev.bufsiz=16384" fauxarg
>>
>> and rebooted.  Now cat /proc/cmdline shows this:
>>
>> console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
>> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
>> init=/lib/systemd/systemd
>>
>> On Sun, Sep 7, 2014 at 7:51 PM, William Hermans 
>> wrote:
>>
>>> Since both of you seem convinced that optargs is not broken, why dont
>>> you actually go make changes to your own uEnv.txt and test if what you
>>> think will work, actually works. What I did works, as I tested it myself.
>>>
>>> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange  wrote:
>>>
 try:
 cat /proc/cmdline

 to see if optargs show there




 On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:

>
> From: William Hermans 
> Reply-To: "beagleboard@googlegroups.com"  >
> Date: Sunday, September 7, 2014 at 7:43 PM
> To: "beagleboard@googlegroups.com" 
> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>
> Ok, so rather coming in and sniping a comment Jjohn, why dont you try
> and set an optargs env variable in the initial uEnv.txt file and see what
> happens.
>
> If you're using the same uboot we're using, it wont work. Now, feel
> free to find yourself trolling a different post.
>
> Wow, that was so unnecessary. I was just trying to be helpful.
>
> Regards,
> John
>
>
>
> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>
>>
>> From: William Hermans 
>> Reply-To: "beagleboard@googlegroups.com" <
>> beagleboard@googlegroups.com>
>> Date: Sunday, September 7, 2014 at 7:26 PM
>> To: "beagleboard@googlegroups.com" 
>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>
>> optargs does not work in the latest uboot file setup. I've noticed
>> this myself in othe situations. you have to use Robert new cmdline env
>> variable
>>
>>
>> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>>
>> Looking at the u-boot patch it looks like optargs is used with both
>> mmcargs and nfsargs.
>>
>> Regards,
>> John
>>
>>
>>
>> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange 
>> wrote:
>>
>>> Hello,
>>>
>>> I'm wondering if it would help if you changed from:
>>>
>>> optargs="consoleblank=0"
>>>
>>> to:
>>>
>>> optargs=consoleblank=0
>>>
>>> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone
>>> Debian Image 2014-09-04 running 3.14.17-ti-r17
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans 
>>> wrote:
>>>
 @Robert

 I'll have you know that you've broken $optargs in the initial stage
 uEnv.txt.

 In case you did not know already . . .

 On Sun, Sep 7, 2014 at 6:32 PM, William Hermans 
 wrote:

> hmm so actual that did not work for me either, which I do not know
> is a bug or what so here is what I had to do.
>
> First check output of:
>
> *$ cat /sys/module/kernel/parameters/consoleblank*
> *600*
>
> It'll probably be 600 as above, which is ten minutes( 600 seconds
> ).
>
> So . . .
>
> *nano /boot/uEnv.txt*
> and uncomment this line:
> *#cmdline=quiet init=/lib/systemd/systemd*
> then add at the end  *consoleblank=0*
> Which gives you
>
>
> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
> reboot the beaglebone and when it comes back up.
>
> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>> *0*
>>
>
>
> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans  > wrote:
>
>> errr sorry, that should

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[Jason Lange]

I don't know if capemanager is functional for these new fangled kernels.
optargs will happily pass non functional arguments (like my fauxarg
above).  Maybe optargs was passing your capemgr.disable argument and it was
something else that was broken?

But if you can make it work why isn't it working for MoscowBob ??

On Sun, Sep 7, 2014 at 8:20 PM, William Hermans  wrote:

> For the record. in that cmdline *consoleblank=0* is declared in $optargs
> and *init=/lib/systemd/systemd *is declared in* $cmdline. *
>
> Previously I had tried disabling hdmi via optargs, so maybe that is now
> different. Either way
> *optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*
>
> was not working for me
>
>
>
> On Sun, Sep 7, 2014 at 8:08 PM, William Hermans  wrote:
>
>> Jason, odd, it seems to be working for me now too. Previously the cmdline
>> env variable was overriding my optargs statements.
>>
>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>> *0*
>>> *root@arm:~# cat /proc/cmdline*
>>> *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
>>> nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
>>> rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
>>> quiet init=/lib/systemd/systemd*
>>>
>>
>>
>> On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange  wrote:
>>
>>> just added fauxarg to my optargs like this:
>>>
>>> optargs="spidev.bufsiz=16384" fauxarg
>>>
>>> and rebooted.  Now cat /proc/cmdline shows this:
>>>
>>> console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
>>> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
>>> init=/lib/systemd/systemd
>>>
>>> On Sun, Sep 7, 2014 at 7:51 PM, William Hermans 
>>> wrote:
>>>
 Since both of you seem convinced that optargs is not broken, why dont
 you actually go make changes to your own uEnv.txt and test if what you
 think will work, actually works. What I did works, as I tested it myself.

 On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange 
 wrote:

> try:
> cat /proc/cmdline
>
> to see if optargs show there
>
>
>
>
> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>
>>
>> From: William Hermans 
>> Reply-To: "beagleboard@googlegroups.com" <
>> beagleboard@googlegroups.com>
>> Date: Sunday, September 7, 2014 at 7:43 PM
>> To: "beagleboard@googlegroups.com" 
>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>
>> Ok, so rather coming in and sniping a comment Jjohn, why dont you try
>> and set an optargs env variable in the initial uEnv.txt file and see what
>> happens.
>>
>> If you're using the same uboot we're using, it wont work. Now, feel
>> free to find yourself trolling a different post.
>>
>> Wow, that was so unnecessary. I was just trying to be helpful.
>>
>> Regards,
>> John
>>
>>
>>
>> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>>
>>>
>>> From: William Hermans 
>>> Reply-To: "beagleboard@googlegroups.com" <
>>> beagleboard@googlegroups.com>
>>> Date: Sunday, September 7, 2014 at 7:26 PM
>>> To: "beagleboard@googlegroups.com" 
>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>
>>> optargs does not work in the latest uboot file setup. I've noticed
>>> this myself in othe situations. you have to use Robert new cmdline env
>>> variable
>>>
>>>
>>> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>>>
>>> Looking at the u-boot patch it looks like optargs is used with both
>>> mmcargs and nfsargs.
>>>
>>> Regards,
>>> John
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange 
>>> wrote:
>>>
 Hello,

 I'm wondering if it would help if you changed from:

 optargs="consoleblank=0"

 to:

 optargs=consoleblank=0

 I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone
 Debian Image 2014-09-04 running 3.14.17-ti-r17



 On Sun, Sep 7, 2014 at 6:37 PM, William Hermans 
 wrote:

> @Robert
>
> I'll have you know that you've broken $optargs in the initial
> stage uEnv.txt.
>
> In case you did not know already . . .
>
> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans  > wrote:
>
>> hmm so actual that did not work for me either, which I do not
>> know is a bug or what so here is what I had to do.
>>
>> First check output of:
>>
>> *$ cat /sys/module/kernel/parameters/consoleblank*
>> *600*
>>
>> It'll probably be 600 as above, which is ten minutes( 600 seconds
>> ).
>>
>> So . . .
>>
>> *nano /boot

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[William Hermans]

Jason, hah ! I see why now. Can you see the problem ?

*uname_r=3.15.10-bone8*
> *cmdline=quiet init=/lib/systemd/systemd*
> *optargs="consoleblank=0"*.
>

This is actually in the wrong file. For this to work in the file he's using
there it needs to be as i said above. Which is:

*cmdline=quiet init=/lib/systemd/systemd*

*consoleblank=0*
This is because the file he's using is the second stage uEnv.txt file and
not the one loaded at boot. Which now that I think about it could have very
well been my problem too.


On Sun, Sep 7, 2014 at 8:30 PM, Jason Lange  wrote:

> I don't know if capemanager is functional for these new fangled kernels.
> optargs will happily pass non functional arguments (like my fauxarg
> above).  Maybe optargs was passing your capemgr.disable argument and it was
> something else that was broken?
>
> But if you can make it work why isn't it working for MoscowBob ??
>
> On Sun, Sep 7, 2014 at 8:20 PM, William Hermans  wrote:
>
>> For the record. in that cmdline *consoleblank=0* is declared in
>> $optargs  and *init=/lib/systemd/systemd *is declared in* $cmdline. *
>>
>> Previously I had tried disabling hdmi via optargs, so maybe that is now
>> different. Either way
>> *optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*
>>
>> was not working for me
>>
>>
>>
>> On Sun, Sep 7, 2014 at 8:08 PM, William Hermans 
>> wrote:
>>
>>> Jason, odd, it seems to be working for me now too. Previously the
>>> cmdline env variable was overriding my optargs statements.
>>>
>>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
 *0*
 *root@arm:~# cat /proc/cmdline*
 *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
 nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
 rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
 quiet init=/lib/systemd/systemd*

>>>
>>>
>>> On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange  wrote:
>>>
 just added fauxarg to my optargs like this:

 optargs="spidev.bufsiz=16384" fauxarg

 and rebooted.  Now cat /proc/cmdline shows this:

 console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
 init=/lib/systemd/systemd

 On Sun, Sep 7, 2014 at 7:51 PM, William Hermans 
 wrote:

> Since both of you seem convinced that optargs is not broken, why dont
> you actually go make changes to your own uEnv.txt and test if what you
> think will work, actually works. What I did works, as I tested it myself.
>
> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange 
> wrote:
>
>> try:
>> cat /proc/cmdline
>>
>> to see if optargs show there
>>
>>
>>
>>
>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>>
>>>
>>> From: William Hermans 
>>> Reply-To: "beagleboard@googlegroups.com" <
>>> beagleboard@googlegroups.com>
>>> Date: Sunday, September 7, 2014 at 7:43 PM
>>> To: "beagleboard@googlegroups.com" 
>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>
>>> Ok, so rather coming in and sniping a comment Jjohn, why dont you
>>> try and set an optargs env variable in the initial uEnv.txt file and see
>>> what happens.
>>>
>>> If you're using the same uboot we're using, it wont work. Now, feel
>>> free to find yourself trolling a different post.
>>>
>>> Wow, that was so unnecessary. I was just trying to be helpful.
>>>
>>> Regards,
>>> John
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>>>

 From: William Hermans 
 Reply-To: "beagleboard@googlegroups.com" <
 beagleboard@googlegroups.com>
 Date: Sunday, September 7, 2014 at 7:26 PM
 To: "beagleboard@googlegroups.com" 
 Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8

 optargs does not work in the latest uboot file setup. I've noticed
 this myself in othe situations. you have to use Robert new cmdline env
 variable


 https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch

 Looking at the u-boot patch it looks like optargs is used with both
 mmcargs and nfsargs.

 Regards,
 John



 On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange 
 wrote:

> Hello,
>
> I'm wondering if it would help if you changed from:
>
> optargs="consoleblank=0"
>
> to:
>
> optargs=consoleblank=0
>
> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone
> Debian Image 2014-09-04 running 3.14.17-ti-r17
>
>
>
> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans  > wrote:
>

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[William Hermans]

This should be that $optargs works in the initial uEnv.txt file loaded at
boot, but not the second stage uEnv.txt file which is pulled in by the
stage 1 file.

False alarm ( again ).

On Sun, Sep 7, 2014 at 6:37 PM, William Hermans  wrote:

> @Robert
>
> I'll have you know that you've broken $optargs in the initial stage
> uEnv.txt.
>
> In case you did not know already . . .
>
> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans  wrote:
>
>> hmm so actual that did not work for me either, which I do not know is a
>> bug or what so here is what I had to do.
>>
>> First check output of:
>>
>> *$ cat /sys/module/kernel/parameters/consoleblank*
>> *600*
>>
>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>>
>> So . . .
>>
>> *nano /boot/uEnv.txt*
>> and uncomment this line:
>> *#cmdline=quiet init=/lib/systemd/systemd*
>> then add at the end  *consoleblank=0*
>> Which gives you
>>
>>
>> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
>> reboot the beaglebone and when it comes back up.
>>
>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>> *0*
>>>
>>
>>
>> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
>> wrote:
>>
>>> errr sorry, that should only be *setterm -blank 0*

>>>
>>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
>>> wrote:
>>>
 $ setterm -powersave off -blank 0

 On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob  wrote:

>
> BBB boot from tftp and nfs -
> kernel:  3.15.10-bone8
> rootfs:  debian-jessie-console-armhf-2014-08-13
>
> Hardware:
> BBB A5C
> Circuitco LCD4 cape
> Circuitco RS232 cape
>
> /home/rob/rootfs/boot/uEnv.txt
>
> uname_r=3.15.10-bone8
> cmdline=quiet init=/lib/systemd/systemd
> *optargs="consoleblank=0"*.
>
> I used this reference
> http://elinux.org/Beagleboard:BeagleBone_Black_FAQ
> 
>  but
> the display is still blanking after 10  minutes.
>
> Would appreciate some guidance.
>
> Thanks
> Rob
>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google
> Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>


>>>
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[William Hermans]

On Sun, Sep 7, 2014 at 8:30 PM, Jason Lange  wrote:

> I don't know if capemanager is functional for these new fangled kernels.
> optargs will happily pass non functional arguments (like my fauxarg
> above).  Maybe optargs was passing your capemgr.disable argument and it was
> something else that was broken?
>

Yes, capemgr always works with 3.8.x, however it is different. optargs does
not seem to work as it did previously.

root@arm:~# cat /sys/devices/bone_capemgr.9/slots
 0: 54:PF---
 1: 55:PF---
 2: 56:PF---
 3: 57:PF---
 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN

root@arm:~# mount /dev/mmcblk0p1 /media/boot/
root@arm:~# cat /media/boot/uEnv.txt |grep optargs=
optargs=consoleblank=0 capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN



> But if you can make it work why isn't it working for MoscowBob ??
>
> On Sun, Sep 7, 2014 at 8:20 PM, William Hermans  wrote:
>
>> For the record. in that cmdline *consoleblank=0* is declared in
>> $optargs  and *init=/lib/systemd/systemd *is declared in* $cmdline. *
>>
>> Previously I had tried disabling hdmi via optargs, so maybe that is now
>> different. Either way
>> *optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*
>>
>> was not working for me
>>
>>
>>
>> On Sun, Sep 7, 2014 at 8:08 PM, William Hermans 
>> wrote:
>>
>>> Jason, odd, it seems to be working for me now too. Previously the
>>> cmdline env variable was overriding my optargs statements.
>>>
>>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
 *0*
 *root@arm:~# cat /proc/cmdline*
 *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
 nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
 rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
 quiet init=/lib/systemd/systemd*

>>>
>>>
>>> On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange  wrote:
>>>
 just added fauxarg to my optargs like this:

 optargs="spidev.bufsiz=16384" fauxarg

 and rebooted.  Now cat /proc/cmdline shows this:

 console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
 init=/lib/systemd/systemd

 On Sun, Sep 7, 2014 at 7:51 PM, William Hermans 
 wrote:

> Since both of you seem convinced that optargs is not broken, why dont
> you actually go make changes to your own uEnv.txt and test if what you
> think will work, actually works. What I did works, as I tested it myself.
>
> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange 
> wrote:
>
>> try:
>> cat /proc/cmdline
>>
>> to see if optargs show there
>>
>>
>>
>>
>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>>
>>>
>>> From: William Hermans 
>>> Reply-To: "beagleboard@googlegroups.com" <
>>> beagleboard@googlegroups.com>
>>> Date: Sunday, September 7, 2014 at 7:43 PM
>>> To: "beagleboard@googlegroups.com" 
>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>
>>> Ok, so rather coming in and sniping a comment Jjohn, why dont you
>>> try and set an optargs env variable in the initial uEnv.txt file and see
>>> what happens.
>>>
>>> If you're using the same uboot we're using, it wont work. Now, feel
>>> free to find yourself trolling a different post.
>>>
>>> Wow, that was so unnecessary. I was just trying to be helpful.
>>>
>>> Regards,
>>> John
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>>>

 From: William Hermans 
 Reply-To: "beagleboard@googlegroups.com" <
 beagleboard@googlegroups.com>
 Date: Sunday, September 7, 2014 at 7:26 PM
 To: "beagleboard@googlegroups.com" 
 Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8

 optargs does not work in the latest uboot file setup. I've noticed
 this myself in othe situations. you have to use Robert new cmdline env
 variable


 https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch

 Looking at the u-boot patch it looks like optargs is used with both
 mmcargs and nfsargs.

 Regards,
 John



 On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange 
 wrote:

> Hello,
>
> I'm wondering if it would help if you changed from:
>
> optargs="consoleblank=0"
>
> to:
>
> optargs=consoleblank=0
>
> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone
> Debian Image 2014-09-04 running 3.14.17-ti-r17
>
>
>
>>

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[William Hermans]

Err actually, they are not loaded, been a while since ive played with
*slots* heh.

On Sun, Sep 7, 2014 at 8:53 PM, William Hermans  wrote:

> On Sun, Sep 7, 2014 at 8:30 PM, Jason Lange  wrote:
>
>> I don't know if capemanager is functional for these new fangled kernels.
>> optargs will happily pass non functional arguments (like my fauxarg
>> above).  Maybe optargs was passing your capemgr.disable argument and it was
>> something else that was broken?
>>
>
> Yes, capemgr always works with 3.8.x, however it is different. optargs
> does not seem to work as it did previously.
>
> root@arm:~# cat /sys/devices/bone_capemgr.9/slots
>  0: 54:PF---
>  1: 55:PF---
>  2: 56:PF---
>  3: 57:PF---
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>
> root@arm:~# mount /dev/mmcblk0p1 /media/boot/
> root@arm:~# cat /media/boot/uEnv.txt |grep optargs=
> optargs=consoleblank=0
> capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
>
>
>
>> But if you can make it work why isn't it working for MoscowBob ??
>>
>> On Sun, Sep 7, 2014 at 8:20 PM, William Hermans 
>> wrote:
>>
>>> For the record. in that cmdline *consoleblank=0* is declared in
>>> $optargs  and *init=/lib/systemd/systemd *is declared in* $cmdline. *
>>>
>>> Previously I had tried disabling hdmi via optargs, so maybe that is now
>>> different. Either way
>>> *optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*
>>>
>>> was not working for me
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 8:08 PM, William Hermans 
>>> wrote:
>>>
 Jason, odd, it seems to be working for me now too. Previously the
 cmdline env variable was overriding my optargs statements.

 *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
> *0*
> *root@arm:~# cat /proc/cmdline*
> *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
> nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
> rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
> quiet init=/lib/systemd/systemd*
>


 On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange 
 wrote:

> just added fauxarg to my optargs like this:
>
> optargs="spidev.bufsiz=16384" fauxarg
>
> and rebooted.  Now cat /proc/cmdline shows this:
>
> console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
> init=/lib/systemd/systemd
>
> On Sun, Sep 7, 2014 at 7:51 PM, William Hermans 
> wrote:
>
>> Since both of you seem convinced that optargs is not broken, why dont
>> you actually go make changes to your own uEnv.txt and test if what you
>> think will work, actually works. What I did works, as I tested it myself.
>>
>> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange 
>> wrote:
>>
>>> try:
>>> cat /proc/cmdline
>>>
>>> to see if optargs show there
>>>
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>>>

 From: William Hermans 
 Reply-To: "beagleboard@googlegroups.com" <
 beagleboard@googlegroups.com>
 Date: Sunday, September 7, 2014 at 7:43 PM
 To: "beagleboard@googlegroups.com" 
 Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8

 Ok, so rather coming in and sniping a comment Jjohn, why dont you
 try and set an optargs env variable in the initial uEnv.txt file and 
 see
 what happens.

 If you're using the same uboot we're using, it wont work. Now, feel
 free to find yourself trolling a different post.

 Wow, that was so unnecessary. I was just trying to be helpful.

 Regards,
 John



 On Sun, Sep 7, 2014 at 7:36 PM, John Syn 
 wrote:

>
> From: William Hermans 
> Reply-To: "beagleboard@googlegroups.com" <
> beagleboard@googlegroups.com>
> Date: Sunday, September 7, 2014 at 7:26 PM
> To: "beagleboard@googlegroups.com" 
> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>
> optargs does not work in the latest uboot file setup. I've noticed
> this myself in othe situations. you have to use Robert new cmdline env
> variable
>
>
> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>
> Looking at the u-boot patch it looks like optargs is used with
> both mmcargs and nfsargs.
>
> Regards,
> John
>
>
>
> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange 
> wrote:
>
>> Hello,
>>
>> I'm wondering if 

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[Jason Lange]

Does the "L" that is there in the listing for slot 4, but not 5 and 6,
indicate that it is loaded.  If you echo in the HDMI capes again do they
then show a "L" as well?

By "new fangled" I mean 3.14 and above -- when I ls /sys/devices there is
no bone_capemgr


On Sun, Sep 7, 2014 at 8:53 PM, William Hermans  wrote:

> On Sun, Sep 7, 2014 at 8:30 PM, Jason Lange  wrote:
>
>> I don't know if capemanager is functional for these new fangled kernels.
>> optargs will happily pass non functional arguments (like my fauxarg
>> above).  Maybe optargs was passing your capemgr.disable argument and it was
>> something else that was broken?
>>
>
> Yes, capemgr always works with 3.8.x, however it is different. optargs
> does not seem to work as it did previously.
>
> root@arm:~# cat /sys/devices/bone_capemgr.9/slots
>  0: 54:PF---
>  1: 55:PF---
>  2: 56:PF---
>  3: 57:PF---
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>
> root@arm:~# mount /dev/mmcblk0p1 /media/boot/
> root@arm:~# cat /media/boot/uEnv.txt |grep optargs=
> optargs=consoleblank=0
> capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
>
>
>
>> But if you can make it work why isn't it working for MoscowBob ??
>>
>> On Sun, Sep 7, 2014 at 8:20 PM, William Hermans 
>> wrote:
>>
>>> For the record. in that cmdline *consoleblank=0* is declared in
>>> $optargs  and *init=/lib/systemd/systemd *is declared in* $cmdline. *
>>>
>>> Previously I had tried disabling hdmi via optargs, so maybe that is now
>>> different. Either way
>>> *optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*
>>>
>>> was not working for me
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 8:08 PM, William Hermans 
>>> wrote:
>>>
 Jason, odd, it seems to be working for me now too. Previously the
 cmdline env variable was overriding my optargs statements.

 *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
> *0*
> *root@arm:~# cat /proc/cmdline*
> *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
> nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
> rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
> quiet init=/lib/systemd/systemd*
>


 On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange 
 wrote:

> just added fauxarg to my optargs like this:
>
> optargs="spidev.bufsiz=16384" fauxarg
>
> and rebooted.  Now cat /proc/cmdline shows this:
>
> console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
> init=/lib/systemd/systemd
>
> On Sun, Sep 7, 2014 at 7:51 PM, William Hermans 
> wrote:
>
>> Since both of you seem convinced that optargs is not broken, why dont
>> you actually go make changes to your own uEnv.txt and test if what you
>> think will work, actually works. What I did works, as I tested it myself.
>>
>> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange 
>> wrote:
>>
>>> try:
>>> cat /proc/cmdline
>>>
>>> to see if optargs show there
>>>
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>>>

 From: William Hermans 
 Reply-To: "beagleboard@googlegroups.com" <
 beagleboard@googlegroups.com>
 Date: Sunday, September 7, 2014 at 7:43 PM
 To: "beagleboard@googlegroups.com" 
 Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8

 Ok, so rather coming in and sniping a comment Jjohn, why dont you
 try and set an optargs env variable in the initial uEnv.txt file and 
 see
 what happens.

 If you're using the same uboot we're using, it wont work. Now, feel
 free to find yourself trolling a different post.

 Wow, that was so unnecessary. I was just trying to be helpful.

 Regards,
 John



 On Sun, Sep 7, 2014 at 7:36 PM, John Syn 
 wrote:

>
> From: William Hermans 
> Reply-To: "beagleboard@googlegroups.com" <
> beagleboard@googlegroups.com>
> Date: Sunday, September 7, 2014 at 7:26 PM
> To: "beagleboard@googlegroups.com" 
> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>
> optargs does not work in the latest uboot file setup. I've noticed
> this myself in othe situations. you have to use Robert new cmdline env
> variable
>
>
> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>
> Looking at the u-boot patch it looks like optargs is used with
> both mmcargs and nfsargs.
>
> Regards,
>>

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[Jason Lange]

I think if they are built in and not loaded as an overlay they never
disappear from the listing I think that L comes and goes to show there
status.

On Sun, Sep 7, 2014 at 9:02 PM, William Hermans  wrote:

> Err actually, they are not loaded, been a while since ive played with
> *slots* heh.
>
> On Sun, Sep 7, 2014 at 8:53 PM, William Hermans  wrote:
>
>> On Sun, Sep 7, 2014 at 8:30 PM, Jason Lange  wrote:
>>
>>> I don't know if capemanager is functional for these new fangled
>>> kernels.  optargs will happily pass non functional arguments (like my
>>> fauxarg above).  Maybe optargs was passing your capemgr.disable argument
>>> and it was something else that was broken?
>>>
>>
>> Yes, capemgr always works with 3.8.x, however it is different. optargs
>> does not seem to work as it did previously.
>>
>> root@arm:~# cat /sys/devices/bone_capemgr.9/slots
>>  0: 54:PF---
>>  1: 55:PF---
>>  2: 56:PF---
>>  3: 57:PF---
>>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>>
>> root@arm:~# mount /dev/mmcblk0p1 /media/boot/
>> root@arm:~# cat /media/boot/uEnv.txt |grep optargs=
>> optargs=consoleblank=0
>> capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
>>
>>
>>
>>> But if you can make it work why isn't it working for MoscowBob ??
>>>
>>> On Sun, Sep 7, 2014 at 8:20 PM, William Hermans 
>>> wrote:
>>>
 For the record. in that cmdline *consoleblank=0* is declared in
 $optargs  and *init=/lib/systemd/systemd *is declared in* $cmdline. *

 Previously I had tried disabling hdmi via optargs, so maybe that is now
 different. Either way
 *optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*

 was not working for me



 On Sun, Sep 7, 2014 at 8:08 PM, William Hermans 
 wrote:

> Jason, odd, it seems to be working for me now too. Previously the
> cmdline env variable was overriding my optargs statements.
>
> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>> *0*
>> *root@arm:~# cat /proc/cmdline*
>> *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
>> nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
>> rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
>> quiet init=/lib/systemd/systemd*
>>
>
>
> On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange 
> wrote:
>
>> just added fauxarg to my optargs like this:
>>
>> optargs="spidev.bufsiz=16384" fauxarg
>>
>> and rebooted.  Now cat /proc/cmdline shows this:
>>
>> console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
>> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
>> init=/lib/systemd/systemd
>>
>> On Sun, Sep 7, 2014 at 7:51 PM, William Hermans 
>> wrote:
>>
>>> Since both of you seem convinced that optargs is not broken, why
>>> dont you actually go make changes to your own uEnv.txt and test if what 
>>> you
>>> think will work, actually works. What I did works, as I tested it 
>>> myself.
>>>
>>> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange 
>>> wrote:
>>>
 try:
 cat /proc/cmdline

 to see if optargs show there




 On Sun, Sep 7, 2014 at 7:46 PM, John Syn 
 wrote:

>
> From: William Hermans 
> Reply-To: "beagleboard@googlegroups.com" <
> beagleboard@googlegroups.com>
> Date: Sunday, September 7, 2014 at 7:43 PM
> To: "beagleboard@googlegroups.com" 
> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>
> Ok, so rather coming in and sniping a comment Jjohn, why dont you
> try and set an optargs env variable in the initial uEnv.txt file and 
> see
> what happens.
>
> If you're using the same uboot we're using, it wont work. Now,
> feel free to find yourself trolling a different post.
>
> Wow, that was so unnecessary. I was just trying to be helpful.
>
> Regards,
> John
>
>
>
> On Sun, Sep 7, 2014 at 7:36 PM, John Syn 
> wrote:
>
>>
>> From: William Hermans 
>> Reply-To: "beagleboard@googlegroups.com" <
>> beagleboard@googlegroups.com>
>> Date: Sunday, September 7, 2014 at 7:26 PM
>> To: "beagleboard@googlegroups.com" 
>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>
>> optargs does not work in the latest uboot file setup. I've
>> noticed this myself in othe situations. you have to use Robert new 
>> cmdline
>> env variable
>>
>>
>> https://github.com/eewiki/u-boot-patches/blob/master/

Re: [beagleboard] debian testing: 2014-09-03 (goodbye vfat release)

[William Hermans]

##enable BBB: eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v2.sh

I suppose this will need to be changed. The tools needed ( now just "tool"
as in singular ), and the actual script file.

I wonder how many people out there realize how powerful this is in
combination with  TFTP / NFS . . .

On Fri, Sep 5, 2014 at 12:21 PM, John Syn  wrote:

>
> From: William Hermans 
> Reply-To: "beagleboard@googlegroups.com" 
> Date: Friday, September 5, 2014 at 12:19 PM
> To: "beagleboard@googlegroups.com" 
> Subject: Re: [beagleboard] debian testing: 2014-09-03 (goodbye vfat
> release)
>
> *So, we are offering more protection, as windows user's can't randomly
>> delete it.*
>>
>
> That should read "clueless users", since I'm a windows user myself and
> have never had that problem :P
>
> All windows users are clueless ;-)
>
>
>
>
> On Fri, Sep 5, 2014 at 12:16 PM, Robert Nelson 
> wrote:
>
>> On Fri, Sep 5, 2014 at 7:14 AM, Vesa Jääskeläinen 
>> wrote:
>> >
>> > On 04/09/14 21:24, Robert Nelson wrote:
>> >>
>> >> Howdy!
>> >>
>> >> I just pushed out another round of images for testing.
>> >>
>> >> There's really only "one" big change with this image, the sorta change
>> >> that will re-write every wiki document.
>> >>
>> >> NO VFAT PARTITION REQUIRED!!!
>> >>
>> >> Let me repeat that... THE VFAT "boot" PARTITION IS NOT REQUIRED! ;)
>> >>
>> >> So far i've only got it to reliabley work on omap4+ bootroms (which
>> >> include the am335x).. so beagle/beagle-xm, not yet...
>> >>
>> > MBR/GPT's MBR emu is at the first sectors of the card. So are you using
>> > relocateable MBR/GPT? Or how are you handling that issue?
>>
>> Traditionally it's been a msdos partition setup... Either way, the
>> first file MLO gets stored at 128k
>>
>> > Would it be wise to also support backup boot loader in case first one
>> gets
>> > corrupt? -- if I recon correctly the bootrom should also support that.
>>
>> We never had a backup boot loader previously.. It was just stored in
>> the "fat" partition as a file and was also shared over usb as a
>> "gadget usb flash drive".
>>
>> So, we are offering more protection, as windows user's can't randomly
>> delete it.
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> http://www.rcn-ee.com/
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Questions about latest images.

[kyle]

I have two older A5A boards that I'm trying to use the August/Sept 
standalone SD images with.   Both behave much different than the older 
image (not sure which one maybe june/july) I'm using from my recently fried 
Rev C board.   I was able to take the backup image from that board and 
write it to an SD that I inserted in an A5A board and it's mostly working. 
 USB gadget shows up on my Macs and power button works as it should.   I've 
been able to at least keep working on my project for now.


However, the new images I downloaded bott up and run on the A5A's but they 
do not appear as a network connection when on USB and the power button does 
nothing when pressed.   I have to access them by USB serial.  Both show the 
usb0 device config in /etc/network/interfaces but neither show that present 
when I run ifconfig.


Is A5A supported on these images?   I'll be ordering a couple new Rev C 
boards later on but for now I have to continue on the A5A's and I don't see 
why that old image behaves perfectly while these do not.   Without access 
to the USB ethernet if I lose my wireless while the board is in my robot it 
means dissasembly to get to it because the custom cape blocks the serial 
console pins.




-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] debian testing: 2014-09-03 (goodbye vfat release)

[John Syn]

From:  William Hermans 
Reply-To:  "beagleboard@googlegroups.com" 
Date:  Sunday, September 7, 2014 at 10:00 PM
To:  "beagleboard@googlegroups.com" 
Subject:  Re: [beagleboard] debian testing: 2014-09-03 (goodbye vfat
release)

> ##enable BBB: eMMC Flasher:
> ##make sure, these tools are installed: dosfstools rsync
> #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v2.sh
> 
> I suppose this will need to be changed. The tools needed ( now just "tool" as
> in singular ), and the actual script file.
> 
> I wonder how many people out there realize how powerful this is in combination
> with  TFTP / NFS . . .
> 
> On Fri, Sep 5, 2014 at 12:21 PM, John Syn  wrote:
>> 
>> From:  William Hermans 
>> Reply-To:  "beagleboard@googlegroups.com" 
>> Date:  Friday, September 5, 2014 at 12:19 PM
>> To:  "beagleboard@googlegroups.com" 
>> Subject:  Re: [beagleboard] debian testing: 2014-09-03 (goodbye vfat release)
>> 
 So, we are offering more protection, as windows user's can't randomly
 delete it.
>>> 
>>> That should read "clueless users", since I'm a windows user myself and have
>>> never had that problem :P
>> All windows users are clueless ;-)
Oh, so this is why you were to pissed at me. It was a joke. You set it up
and I couldn¹t resist ;-)

I¹m not purposefully mean or demeaning so please don¹t take this the wrong
way. It was just meant as a little light hearted humor.

Regards,
John
>>> 
>>> 
>>> 
>>> On Fri, Sep 5, 2014 at 12:16 PM, Robert Nelson 
>>> wrote:
 On Fri, Sep 5, 2014 at 7:14 AM, Vesa Jääskeläinen 
 wrote:
> >
> > On 04/09/14 21:24, Robert Nelson wrote:
>> >>
>> >> Howdy!
>> >>
>> >> I just pushed out another round of images for testing.
>> >>
>> >> There's really only "one" big change with this image, the sorta change
>> >> that will re-write every wiki document.
>> >>
>> >> NO VFAT PARTITION REQUIRED!!!
>> >>
>> >> Let me repeat that... THE VFAT "boot" PARTITION IS NOT REQUIRED! ;)
>> >>
>> >> So far i've only got it to reliabley work on omap4+ bootroms (which
>> >> include the am335x).. so beagle/beagle-xm, not yet...
>> >>
> > MBR/GPT's MBR emu is at the first sectors of the card. So are you using
> > relocateable MBR/GPT? Or how are you handling that issue?
 
 Traditionally it's been a msdos partition setup... Either way, the
 first file MLO gets stored at 128k
 
> > Would it be wise to also support backup boot loader in case first one
> gets
> > corrupt? -- if I recon correctly the bootrom should also support that.
 
 We never had a backup boot loader previously.. It was just stored in
 the "fat" partition as a file and was also shared over usb as a
 "gadget usb flash drive".
 
 So, we are offering more protection, as windows user's can't randomly
 delete it.
 
 Regards,
 
 --
 Robert Nelson
 http://www.rcn-ee.com/
 
 --
 For more options, visit http://beagleboard.org/discuss
 ---
 You received this message because you are subscribed to the Google Groups
 "BeagleBoard" group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to beagleboard+unsubscr...@googlegroups.com
  .
 For more options, visit https://groups.google.com/d/optout.
>>> 
>>> 
>>> -- 
>>> For more options, visit http://beagleboard.org/discuss
>>> --- 
>>> You received this message because you are subscribed to the Google Groups
>>> "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> 
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Are there no capes which provide just I/O buffering and level conversion?

[briselec via BeagleBoard]

For bidirectional push pull
>
> http://www.ti.com/product/txb0108?keyMatch=txb0108&tisearch=Search-EN
>
>
Note the txb0108 has a low dc drive strength. They can't pull a bus low if 
it has strong pullups.   

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.