Re: [beagleboard] Re: Beagle Bone Black power LED blinks once when powered

[manelouabel94]

Hey I am currently experiencing the same problem as you had. Is there a 
solution or should I buy a new board?

Thank you

Le vendredi 19 juin 2015 22:55:43 UTC-4, Graham a écrit :
>
> I thought that it would work on USB, and not on external power supply.
> If the situation is that you get the one blink and no boot, is the same for
> both USB power and external power, then there is a hard failure of the 
> Beaglebone. Either a damaged power supply chip, or a short circuit
> downstream from there.
>
> --- Graham
>
> On Fri, Jun 19, 2015 at 11:18 AM, Vinicius Maciel  > wrote:
>
>> Hi, 
>>
>> I do not think the problem is the power sypply. I was using the same 
>> power supply before the problem occurred, power supply is functioning 
>> normally, I use it to charge my cell phone!
>>
>> In this video, https://youtu.be/qojeLqazkK8, I tested two power 
>> supplies. The same that I have used to power up through USB connector and a 
>> common DC power supply. Nothing else works :(
>>
>> 2015-06-19 11:21 GMT-03:00 Graham >:
>>
>>> If the BBB will run from USB power, then the BBB is probably OK.
>>>
>>> Put an oscilloscope on the output of the power supply that is causing 
>>> the problem, and watch what the voltage does when you turn things on.
>>>
>>> I had a bench power supply (B 1550) that when set to 5 Volts, then the 
>>> output turned on, would throw a transient up to 6 Volts then return to 5 
>>> Volts. (The bigger the capacitor across the load, the greater the 
>>> transient.) This would trip the over-voltage detect in the BBB power 
>>> supply, which would blink the power LED once, then off after that.
>>>
>>> So, make sure the power supply is working properly.  Some of the cheap 
>>> power supplies out there will NOT run a BBB.
>>>
>>> --- Graham
>>>
>>> ==
>>>
>>> On Thursday, June 18, 2015 at 7:27:54 PM UTC-5, Gerald wrote:

 Sounds like an overvoltage condition on the 5V DC input may have 
 damaged the DC input. Usually from a cheap 5V power supply. If the USB 
 power works, then the rest of the board is OK.

 Gerald


 On Thu, Jun 18, 2015 at 11:17 AM,  wrote:

> Hi, my Beaglebone Black have the same behavior, gives a short blink at 
> the power LED when powered. 
> But, I turned on via usb connector with power supply 5V@1A. What may 
> have happened?
>
>
> Em sexta-feira, 16 de agosto de 2013 13:44:09 UTC-3, magu_ escreveu:
>>
>> Hi
>>
>> I powered the BBB over the DGND - VDD_5V. But by accident I plugged 
>> it into PWR_BUT. 
>>
>> Now it only gives a short blink at the power LED when powered. I know 
>> this is a bad sign... But does anybody of you know if this does not mean 
>> the end of it and if it can be somehow reset?
>>
>> yours
>> magu_
>>
> -- 
> 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.
>



 -- 
 Gerald
  
 ger...@beagleboard.org
 http://beagleboard.org/

>>> -- 
>>> 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/ilf5jOwbgFE/unsubscribe.
>>> To unsubscribe from this group and all its topics, 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 a topic in the 
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/beagleboard/ilf5jOwbgFE/unsubscribe.
>> To unsubscribe from this group and all its topics, 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7d0e0e8e-2768-4b40-b920-cf9645481bd1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Quadrature Encoder, Device Trees and Machinekit issue

[Paulo Sherring]

Hi, everybody!
I am having trouble trying to use machinekit, config-pin and a non default 
pinmux state.
What I want to do is to configure P9_27 and P9_92 to be used by the 
quadrature encoder peripheral and leave P9_25 alone.
If I use config-pin to configure it to qep, it disables by default pull up, 
which I need, since I didn't include it in my custom PCB.
If I use a custom device tree to setup QEP, all pins are claimed and I cant 
use P9_25 throgh machinekit, as IO.
I guess I could use a memdev like program to enable it by hand. I did it in 
the past, but, I feel that it is the cheaters way to do it.
I never really understood device tree, it was always trial and error or raw 
memory RW with me :/

In help is very welcome.
Thanks in advance.
Paulo Sherring.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ebd23058-edb7-4a0e-aa82-6481e95840b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] PRU Cookbook

[Jason Kridner]

Announcing rev 0.1.0 of PRU Cookbook

PDF: https://github.com/beagleboard/PRUCookbook/releases/download/0.1.0/book.pdf

Live view: https://markayoder.github.io/PRUCookbook/
Source: https://github.com/markayoder/PRUCookbook/
Report issues: https://github.com/markayoder/PRUCookbook/issues


Outline

A cookbook for programming the PRUs in C using remoteproc and
compiling on the Beagle

Case Studies

✓ Robotics Control Library

✓ BeagleLogic

✓ LEDscape

✓ Falcon Player

❏ MachineKit

❏ ArduPilot

Getting started

✓ Selecting a Beagle

✓ Installing the Latest OS on Your Bone

✓ Flashing a Micro SD Card

✓ Cloud9 IDE

✓ Getting Example Code

✓ Blinking an LED

Running a Program; Configuring Pins

✓ Getting Code Example Files

✓ Compiling and Running

✓ Stopping and Starting the PRU

✓ The Standard Makefile

✓ Compiling with clpru and lnkpru

✓ The Linker Command File - AM335x_PRU.cmd

✓ Loading Firmware

✓ Configuring Pins for Controlling Servos

✓ Configuring Pins for Controlling Encoders

Debugging and Benchmarking [1]

✓ Debugging via an LED

✓ dmesg –Hw

✓ prudebug - A Simple Debugger for the PRU

✓ UART

Building Blocks – Applications

✓ Memory Allocation

✓ Auto Initialization of Built in LED Triggers

✓ PWM Generator

✓ Controlling the PWM Frequency

✓ Loop Unrolling for Better Performance

✓ Making All the Pulses Start at the Same Time

✓ Adding More Channels via PRU 1

✓ Sychronziing Two PRUs

✓ Reading an Input at Regular Intervals

✓ Analog Wave Generator

✓ WS2812 (NeoPixel) driver

✓ Setting NeoPixels to Different Colors

✓ Controlling Arbitrary LEDs

✓ Controlling NeoPixels Through a Kernel Driver

✓ RGB LED Matrix - No Integrated Drivers

✓ Compiling and Inserting rpmsg_pru

Accessing More I/O [2]

✓ /boot/uEnv.txt to access P8 I/O

✓ Accessing gpio

More Performance

✓ Calling Assembly from C

✓ Returning a Value from Assembly

✓ Using the Built In Counter for Timing

✓ Xout and Xin - Transfering Between PRUs

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPksgo2EmtaBnADPT6tYB2R%3DieU4y4GWoDksq2aKdY4nHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: PWM problem

[Krzysztof Śmiałek]

Ok, for me it is not important to flash emmc. I can use system from card.
And I want use this method. So, what should I do step  by step? For this
momet I have got old version on the emmc and ne we on sd card. If i remove
card, BBB boot from emmc. If I insert card, BBB boot from sd card. But when
I am using system form card there is problem with this PWM by adafruit in
python. When I use this comand: sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M
count=100 after rebooting BBB dont get up. All leds are off. With card,
without don't matter. BBB is off.

wt., 25 wrz 2018, 17:27 użytkownik Robert Nelson 
napisał:

> > *   I don't know enough about the flashing process to know if it is
> done on
> > a "by file" basis, or is done "by block". If the former, getting the used
> > space of the SD card down to around 1.5-1.8GB might be sufficient; if it
> is
> > by blocks, you'd have to somehow compress the SD card free space and
> shrink
> > the partition...
> > Perhaps Mr. Nelson could chime in on this part of the mysterious
> BBB
> > flashing process?
>
> So it's just rsync that copes files, so when it error's out, it really
> just error's out from lack of space..
>
> One option, for the 2GB eMMC that I've slightly played with but
> haven't tested in a flashing situation... Btrfs with compression..
>
> With BTFS with lzo, cut down the iot image from 3.3G to 1.6-ishG...
> Well somewhere around there, it's been a few months..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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/VVhdRE72JFE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYggtFGmyvt3euvo7QLUtfJj7PffCtf9t%3DXA5%2B7twAvqQA%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAK-qOpDGWWqHSHh11paXtPOSWC%3DSEkDDyrQSYp6EoRSQNnFUQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: PWM problem

[Robert Nelson]

> *   I don't know enough about the flashing process to know if it is done 
> on
> a "by file" basis, or is done "by block". If the former, getting the used
> space of the SD card down to around 1.5-1.8GB might be sufficient; if it is
> by blocks, you'd have to somehow compress the SD card free space and shrink
> the partition...
> Perhaps Mr. Nelson could chime in on this part of the mysterious BBB
> flashing process?

So it's just rsync that copes files, so when it error's out, it really
just error's out from lack of space..

One option, for the 2GB eMMC that I've slightly played with but
haven't tested in a flashing situation... Btrfs with compression..

With BTFS with lzo, cut down the iot image from 3.3G to 1.6-ishG...
Well somewhere around there, it's been a few months..

Regards,

-- 
Robert Nelson
https://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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYggtFGmyvt3euvo7QLUtfJj7PffCtf9t%3DXA5%2B7twAvqQA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] internet over usb isn't working

[albertz . dic]

hi all, yesterday i received my BBB rev C and i tried to follow the step in 
the getting started page (the html from the BB) but after the installation 
of the udev rules the BB i was trying to connect from the usb but with no 
success.
I have Manjaro KDE  i tried to change the script to put the rule in the 
/lib/udev/rules.d/ but nothing; i tried to change the priority of the rule 
in 99-beaglebone.rules ( in /lib/udev/rules.d), nothing.
This is my  ifconfig:
ifconfig
enp0s20u3: flags=4163  mtu 1500
inet6 fe80::2ac9:7ec0:9f88:8410  prefixlen 64  scopeid 0x20
ether 74:e1:82:78:65:dc  txqueuelen 1000  (Ethernet)
RX packets 49  bytes 11178 (10.9 KiB)
RX errors 3  dropped 0  overruns 0  frame 3
TX packets 2  bytes 469 (469.0 B)
TX errors 58  dropped 0 overruns 0  carrier 0  collisions 0

enp5s0f1: flags=4099  mtu 1500
ether 08:62:66:b5:c2:9f  txqueuelen 1000  (Ethernet)
RX packets 4654  bytes 3256416 (3.1 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 4238  bytes 430478 (420.3 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 43  base 0xd000  

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 901  bytes 75744 (73.9 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 901  bytes 75744 (73.9 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp4s0: flags=4163  mtu 1500
inet 172.20.10.2  netmask 255.255.255.240  broadcast 172.20.10.15
inet6 fe80::acdc:d52f:2565:d1  prefixlen 64  scopeid 0x20
ether 28:c2:dd:10:7d:6f  txqueuelen 1000  (Ethernet)
RX packets 1741  bytes 2008158 (1.9 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 1241  bytes 151289 (147.7 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 

enp0s20u3 is the BBB

I tried to force the ip to 192.168.7.2 netmask 255.255.255.0 gateway 
192.168.1.1 and 0.0.0.0 then in the browser (firefox and surf) i cannot 
connect with the BBB but i was able to ping the 192.168.7.2, when i tried 
to connect from ssh:
ssh: connect to host 192.168.7.2 port 22: Connection refused

I tried from ManjaroKDE, Ubuntu18.04Live, ManjaroGnomeLive always the same 
result.
I tried to change the connection of the host  (eth and wifi).

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/0bc01e63-a89f-4652-80a2-ae5a9ddb81bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] internet over usb

[Alberto di ciommo]

hi yesterday i tried to connect the BBB from usb but the connection over 
internet failed always.
I tried to change OS: ManjaroKDE(default), ManjaroGnomeLive, Ubuntu18Live.
I tried to change the host connection to internet (from eth to wifi).
I tried to put udev rules in /lib/udev/rules.d/73-beaglebone.rules and 
/lib/udev/rules.d/99-beaglebone.rules.
I tried to change manually the setting of the BB usb in ip:192.168.7.2 
netmask: 255.255.255.0 gtw: 0.0.0.0 / 192.168.1.1 and i was able to ping 
the ip but the connection in the browsers (firefox and surf) was refused 
and also the ssh connection: ssh: connect to host 192.168.7.2 port 22: 
Connection refused.

this is the ifconfig

enp0s20u3: flags=4163  mtu 1500
inet6 fe80::2ac9:7ec0:9f88:8410  prefixlen 64  scopeid 0x20
ether 74:e1:82:78:65:dc  txqueuelen 1000  (Ethernet)
RX packets 49  bytes 11178 (10.9 KiB)
RX errors 3  dropped 0  overruns 0  frame 3
TX packets 2  bytes 469 (469.0 B)
TX errors 58  dropped 0 overruns 0  carrier 0  collisions 0

enp5s0f1: flags=4099  mtu 1500
ether 08:62:66:b5:c2:9f  txqueuelen 1000  (Ethernet)
RX packets 4654  bytes 3256416 (3.1 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 4238  bytes 430478 (420.3 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 43  base 0xd000  

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 901  bytes 75744 (73.9 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 901  bytes 75744 (73.9 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp4s0: flags=4163  mtu 1500
inet 172.20.10.2  netmask 255.255.255.240  broadcast 172.20.10.15
inet6 fe80::acdc:d52f:2565:d1  prefixlen 64  scopeid 0x20
ether 28:c2:dd:10:7d:6f  txqueuelen 1000  (Ethernet)
RX packets 1741  bytes 2008158 (1.9 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 1241  bytes 151289 (147.7 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
how can i solve this problem?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/22469706-1cc7-4474-a76d-eb5f37c7614a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PWM problem

[Krzysztof Śmiałek]

Ok, for now I have flashed board with Debian 7.5 (BeagleBone Black - 2GB
eMMC) 2014-05-14

Than I remove card from BBB and install on the card: Debian 9.5 2018-08-30 4GB
SD IoT

Flashing this distro probably will not be possible because of little space
od eMMc. (I have tried it before)

Ond the SD card I need to change name of file to "uEnv.txt" to update the
bootloader and after that I can use the newest distro. But what I need to
do now to can use a PWM? If I use now: sudo dd if=/dev/zero of=/dev/mmcblk1
bs=1M count=100
The BBB will not get up. Need I make another changes in files on SD or emmc?
I am very newbie in BBB and now I am little confused :)
So tell me please step by step what should I do :)
Thanks!

wt., 25 wrz 2018 o 08:36 Krzysztof Śmiałek 
napisał(a):

> Ok,
> so first of all I need to run the BBB from emmc? So I need reflash this
> bootloader, yes?
> After that I need download new version of image from side, load on sd card
> and now using: sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=100
> shoudl help?
> Or I need making another changes in different place of code? Because now
> I am little confused.
> KS
>
> wt., 25 wrz 2018 o 00:09 Robert Nelson 
> napisał(a):
>
>> On Mon, Sep 24, 2018 at 3:55 PM Krzysztof Śmiałek
>>  wrote:
>> >
>>
>> Okay the reporting is fixed:
>>
>> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
>> 2018.09-2-g0b54a51eee]:[location: dd MBR]
>> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
>> 2014.04-00014-g47880f5]:[location: fatfs /boot/uboot/MLO]
>>
>> > Ok, so what should I do? Reflash emmc to old one once again? When I was
>> testing yesterday after reflashing the pwm was working on this old soft but
>> probably it will be better if i can use new version of soft.
>>
>> It's up to you.. but i'd just run:
>>
>> sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=100
>>
>> and utilze the new microSD image.
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAK-qOpA7BSh2Uyq%2B8i5_-Z2aMYjJZpBh5i-VZUHbXZmyNYDS%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PWM problem

[Krzysztof Śmiałek]

Ok,
so first of all I need to run the BBB from emmc? So I need reflash this
bootloader, yes?
After that I need download new version of image from side, load on sd card
and now using: sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=100 shoudl
help?
Or I need making another changes in different place of code? Because now I
am little confused.
KS

wt., 25 wrz 2018 o 00:09 Robert Nelson  napisał(a):

> On Mon, Sep 24, 2018 at 3:55 PM Krzysztof Śmiałek
>  wrote:
> >
>
> Okay the reporting is fixed:
>
> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
> 2018.09-2-g0b54a51eee]:[location: dd MBR]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
> 2014.04-00014-g47880f5]:[location: fatfs /boot/uboot/MLO]
>
> > Ok, so what should I do? Reflash emmc to old one once again? When I was
> testing yesterday after reflashing the pwm was working on this old soft but
> probably it will be better if i can use new version of soft.
>
> It's up to you.. but i'd just run:
>
> sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=100
>
> and utilze the new microSD image.
>
> Regards,
>
> --
> Robert Nelson
> https://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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAK-qOpCsku9QWn5BsdiCiH3bnjTaQtbxGGN1S%2B9z4bNMfi3qUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Disable Display Cape and use HDMI

[Marco Liess]

Hi Robert,

Thank you very much for your quick response!

So I've tried overriding the cape with SPI and at first didn't have
success. What did the job for me was looking for the "HDMI Cape" in
/lib/firmware. So I edited my /boot/uEnv.txt to this:

uboot_oberlay_addr0=/lib/firmware/BB-HDMI-TDA998x-00A0.dtbo
uboot_oberlay_addr1=/lib/firmware/BB-SPIDEV0-00A0.dtbo
uboot_oberlay_addr2=/lib/firmware/BB-SPIDEV0-00A0.dtbo
uboot_oberlay_addr3=/lib/firmware/BB-SPIDEV0-00A0.dtbo

Now the Display is attached but I can use HDMI! :-)

Thank you for your support.

Regards

Marco

Robert Nelson  schrieb am Mo., 24. Sep. 2018,
21:34:

> On Mon, Sep 24, 2018 at 2:22 PM Marco Liess  wrote:
> >
> > Hi Guys,
> >
> > my problem is that I need to "switch" between using the display cape and
> the HDMI output of my BeagleBone Black Rev C. I can't always detach the
> Display Cape when I want to use HDMI because I plan on fitting my BBB in a
> permanent case.
> > Is there a possibility to use the HDMI output when the Display Cape is
> attached to the Board? I can't seem to find an answer in any other
> questions or forums so I would really appreciate some help.
> >
> > I'm currently using debian 9.5 with following kernel: 4.14.49-ti-r54
> > I've tried editing the /boot/uEnv.txt file to disable loading the Cape,
> but I've always come up with an error.
> > When I disable uboot_overlays and power up my BBB, the user LEDs start
> blinking but after a few seconds only the heartbeat LED is on, while the
> other LEDs are off permanently. On the screen I can only see the startup
> "penguin icon" but it's like the BBB froze.
> > I've also tried uncommenting disable_uboot_overlay_addr0= and enabling
> uboot_overlays but then the same thing happens to the LEDs while my monitor
> doesn't even recognize a HDMI device.
> >
> > I am really stuck because I think it has to be possible to disable the
> Display Cape but I can't figure out how. Thank you in advance.
>
> Currently, there's no way to disable "it"...
>
> However you can "override it"  On startup, it'll pick addr0>3,
> this is eaiser to figure out if you plug in a serial adapter. One
> option is just to use:
>
> uboot_overlay_addr0=/lib/firmware/BB-SPIDEV0-00A0.dtbo
> uboot_overlay_addr1=/lib/firmware/BB-SPIDEV0-00A0.dtbo
> uboot_overlay_addr2=/lib/firmware/BB-SPIDEV0-00A0.dtbo
> uboot_overlay_addr3=/lib/firmware/BB-SPIDEV0-00A0.dtbo
>
> Then it definitely won't load the display cape.
>
> However this is definitely and odd one and one i didn't code for, so
> i'm not sure if the hdmi will actually come up either...
>
> Regards,
>
> --
> Robert Nelson
> https://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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF6QW1tS8USwcnGXAvF9RocEQqHYgS3W2NKvXxJp-7qBpZqYWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.