Hi Robert,
I've also faced the same issue and got resolved with your suggestion. Thank
you .
Regards,
Venkatesh
On Thursday, March 23, 2017 at 6:47:59 PM UTC+5:30, RobertCNelson wrote:
>
>
>
> On Mar 23, 2017 4:48 AM, "embue" >
> wrote:
>
>
> Following current instructions for U-Boot result in
Thank you so much for the patch. This did seem to fix my problem, but then
I found that it seems to work for some Beaglebone Blacks but not others.
Even boards from the same manufacturer (but potentially different lots).
What causes this issue? Is there something that would explain why the
git:/opt/scripts/:[9d965a5f40ae00774c81164f87a450a678ab79f6]
eeprom:[A335BNLTBWA51650BBWG0378]
model:[TI_AM335x_BeagleBone_Black_Wireless]
dogtag:[BeagleBoard.org Debian Image 2016-11-06]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2018.03-2-g254339602c]:[location: dd MBR]
kerne
On Wed, Mar 28, 2018 at 9:40 AM, ags wrote:
> git:/opt/scripts/:[9d965a5f40ae00774c81164f87a450a678ab79f6]
>
> eeprom:[A335BNLTBWA51650BBWG0378]
>
> model:[TI_AM335x_BeagleBone_Black_Wireless]
>
> dogtag:[BeagleBoard.org Debian Image 2016-11-06]
>
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Bo
Hello Evan
I've done it and designing a cape that manages the power by turning it off
and on under external RTC control.
I've found this works
$ sudo su
$ echo 0 > /sys/class/rtc/rtc0/wakealarm
$ echo `date '+%s' -d '+ 1 minutes'` > /sys/class/rtc/rtc0/wakealarm
$echo standby > /sys/power/state
Hi,
Thanks for the reply, I gave this a try and I can see that indeed it does
go into a low power state, however it will not wake.
These are the commands I entered for reference:
debian@beaglebone:~$ sudo su
[sudo] password for debian:
Sorry, try again.
[sudo] password for debian:
root@beaglebon
Hi,
I'm trying to use the spi device on my beaglebone black with a C program.
For setup I use something like:
uint8_t SPImode |= SPI_CPOL;
uint8_t bits = 8;
uint16_t delay = 0;
uint32_t speed = 50;
fd = open("spidev1.0", O_RDWR);
ret = ioctl(fd, SPI_IOC_WR_MODE, &SPImode);
ret = ioctl(fd, SP
Hello,
Thank you for all the help!
I have finally been able to get this array constructed by a user space C
program into the external DDR ram, and access the array directly from PRU0
using uio_pruss! I wanted to give an update on what I did for anyone else
who might try to do something simila
what version kernel are you using. 4.9 had logging turned on and it made
a lot of noise
On 3/28/2018 5:56 AM, joerg.kr...@ims.fraunhofer.de wrote:
> Hi,
> I'm trying to use the spi device on my beaglebone black with a C program.
> For setup I use something like:
>
> |
> uint8_t SPImode|=SPI_CPOL;
Uh oh...
debian@BBB:~$ sudo apt upgrade bb-wl18xx-firmware firmware-ti-connectivity
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... The following packages were automatically installed
and are no longer required:
libpci3
I realize there is not an explicit question here...
I have paused (^Z) the upgrade. Can I terminate and reclaim the disk space,
or is there another option?
Does the desired package upgrade really require 400+MB of dependencies to
also be upgraded? The output looks like all possible upgrades wer
On Wed, Mar 28, 2018 at 4:13 PM, ags wrote:
> I realize there is not an explicit question here...
>
> I have paused (^Z) the upgrade. Can I terminate and reclaim the disk space,
> or is there another option?
>
> Does the desired package upgrade really require 400+MB of dependencies to
> also be up
Sorry if this is obvious. The current situation is that I have no "disk"
space left and the upgrade is paused (^Z) after fetching 464 MB. I have
minimal user-installed "stuff" on the system so it appears to have been
filled up with this upgrade attempt.
I thought I would be installing the "firm
On Wed, Mar 28, 2018 at 4:34 PM, ags wrote:
> Sorry if this is obvious. The current situation is that I have no "disk"
> space left and the upgrade is paused (^Z) after fetching 464 MB. I have
> minimal user-installed "stuff" on the system so it appears to have been
> filled up with this upgrade a
This is turning into an "apt" tutorial - but searches haven't helped me
find what I'm looking for.
I have killed the upgrade mis-stream. I think it successfully downloaded
all the upgradable packages, and ran out of "disk" space while unpacking
it. I don't know if anything was actually installe
More specifics: I see lots of stuff (~450MiB) in /var/cache/apt/archives.
Only two are dated today. One is bb-wl18xx-firmware...
Do I "sudo apt-get clean", or delete everything manually from the
apt/archive (except bb-wl18xx-firmware...) or something else?
On Wednesday, March 28, 2018 at 3:42
Update if anyone's curious,
I actually tried temporarily pulling the cape's corresponding overlay from
/lib/firmware (I think that's where it was) and booting up that way, and
SPI came back, so I believe that may solve my problem, otherwise I just
have to modify and re-build that cape.
--
For
I've cleaned the package cache:
sudo apt-get clean
and recovered ~400MB "disk" space.
debian@BBB:/$ sudo apt install firmware-ti-connectivity
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct
looks like I have a lot of partially installed packages...
debian@BBB:/$ apt-get -f install --dry-run
NOTE: This is only a simulation!
apt-get needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real
OK, here's general info on how to interface the ESP8266 with another
device:
http://rancidbacon.com/files/kiwicon8/ESP8266_WiFi_Module_Quick_Start_Guide_v_1.0.4.pdf
-- scroll down to page 3. Caveat: he says that powering the ESP8266 from,
e.g., a Beagle, is a bad idea. What I would do is suppl
Sorry don't know how to trace it. Perhaps there is another command to
enable the RTC interrupt, but I haven't kept track of how I go there.
On Wed, Mar 28, 2018 at 10:52 AM, Evan Griffith
wrote:
> Hi,
>
> Thanks for the reply, I gave this a try and I can see that indeed it does
> go into a l
Hi All,
I am trying to connect spektrum dsm8 receiver. After binding the receiver I
connected to the board and ran "rc_test_dsm".
Here is the result:
WARNING: too many DSM channels detected, trying again
WARNING: too many DSM channels detected, trying again
WARNING: too many DSM channels detect
Hi Evan, thanks for the guide!
Am Mittwoch, 28. März 2018 20:23:08 UTC+2 schrieb evan@cyvision.com:
>
> TJF and the others were right, I could not find an easy way to do this
> using rproc, but with uio_pruss it is fairly straight forward. While the
> suggestions made to help me get this goi
23 matches
Mail list logo
