Granted, I do agree. That discussing low level micro-controller C code,
when describing Javascript is a bit odd. But in reality, the heavy lifting
is done in C, while Javascript just wraps the executable, and making it
perhaps easier to use ?
Quite honestly, a couple of years ago I could not see m
pwm:
https://github.com/wphermans/Bonejs/blob/master/documentation/pwm-readme.md
and
devmem:
https://github.com/wphermans/Bonejs/blob/master/documentation/devmem-readme.md
Added. Both are very similar to using each from the cmdline. Personally, I
think the devmem wrapper is very cool, but I'm not
Same issue here.
Any help?
On Monday, July 18, 2016 at 6:25:21 AM UTC-7, Geek Till It Hertz wrote:
>
>
> Hi,
> New to Beaglebone here, i cannot get the hdmi cape for beagle bone green
> wireless working, any ideas?
>
--
For more options, visit http://beagleboard.org/discuss
---
You received t
Note: Don't do an apt-get upgrade it'll royally screw things up. For me it
rendered tzdata half installed, and cause everything else related to apt to
break. With no way to back out, or easily fix the problem.
On Thu, Jul 28, 2016 at 5:08 PM, William Hermans wrote:
> Anyway, uenv_root= got it wo
Anyway, uenv_root= got it working, thanks Robert !
On Thu, Jul 28, 2016 at 3:41 PM, William Hermans wrote:
> Somehow this worked for me: I guess mmcargs was not the right place to put
> uenv_root= . . .
>
> debian@arm:~$ cat /uEnv.txt
> ##This will work with: Angstrom's 2013.06.20 u-boot.
>
> lo
Somehow this worked for me: I guess mmcargs was not the right place to put
uenv_root= . . .
debian@arm:~$ cat /uEnv.txt
##This will work with: Angstrom's 2013.06.20 u-boot.
loadaddr=0x8200
fdtaddr=0x8800
rdaddr=0x8808
initrd_high=0x
fdt_high=0x
#for single partitions
Also
debug: [console=ttyO0,115200n8 root=/dev/mmcblk1p1 ro rootfstype=ext4
rootwait ipv6.disable=1
is not what I have.
william@beaglebone:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0boot0 179:802M 1 disk
mmcblk0boot1 179:16 02M 1 disk
mmcblk0 179:00 3.
Still not working. The dahmed thing insists on booting from mmcblk1 when
there is not mmcblk1 inserted. But as soon as I do insert an sdcard, it
boots from it.
Checking for: /boot/uEnv.txt ...
gpio: pin 55 (gpio 55) value is 1
1181 bytes read in 19 ms (60.5 KiB/s)
Loaded environment from /boot/uEn
Robert,
Ok, here is exactly what I did, incase you might spot something else I did
wrong . . .
I downloaded your barefs, chroot'd into it, and used APT to install a
4.4*bone* kernel, and a few tools. tar'd that up, and tar'd it back to a
working single partition (eMMC)
The kernel loads, but get
So . . .
[5.174190] of_cfs_init
[5.176726] of_cfs_init: OK
[5.183633] Waiting for root device /dev/mmcblk1p1...
The problem *is* . . .
william@ds:~/armhf-rootfs$ cat uEnv.txt | grep mmcroot
mmcroot=/dev/mmcblk0p1
mmcargs=setenv bootargs console=tty0 console=${console} ${optargs}
${ca
So . . . yeah. For 4.x kernels it's broken.
william@beaglebone:~$ ls /sys/class/pwm/
william@beaglebone:~$ nano bspwm_P9_22_13-00A0.dts
william@beaglebone:~$ dtc -O dtb -o bspwm_P9_22_13-00A0.dtbo -b 0 -@
bspwm_P9_22_13-00A0.dts
Error: bspwm_P9_22_13-00A0.dts:53.2-54.1 syntax error
FATAL ERROR: Un
Hi Mike,
Yeah, that's pretty cool, except it does need an update at minimum when
showing sysfs paths for *ocp* targets
. Also I'm not entirerly sure it generates correct overlay files for( at
minimum ) ehrpwm* and kernels 4.1.x+
On Thu, Jul 28, 2016 at 1:16 PM, Mike wrote:
> On 07/28/2016 03:
On 07/28/2016 03:20 PM, William Hermans wrote:
I think what would be super useful, if a web interface, or maybe even
native app that did pinmux for people. Select a few options from
dropdowns, click a few checkboxes, and viola ! Have it generate a *dts
file for you.
http://kilobaser.com/blog/2
Charles,
The idea I had in my mind is that someone could potentially, more easily.
Figure out how to use device tree files. By examining something that is
closer to self explanatory, and not a wall of code to hurdle. I think your
overlays illustrate very well how device tree files work, but that w
I think what would be super useful, if a web interface, or maybe even
native app that did pinmux for people. Select a few options from dropdowns,
click a few checkboxes, and viola ! Have it generate a *dts file for you.
I will say, and agree that this platform is not like something like the
rPI( Ar
I want to know how to pin multiplex pins in initial phase of boot i.e is in
spl(MLO). What I am trying to do is change the default pin configuration to
gpio one, so that I can see high or low on the pin.
On P8 header I tried to change the mode 0 from default 'TIMER4' to gpio2[2]
i.e mode 7. S
I am trying to send and receive data from my PC to BeagleBone Black via
RS485. I used a 'ISO3082' transceiver in between to make the signals
compatible. I used UART2 of BBB. The RE/DE pin is not getting toggled for
Tx and Rx. My dts code is as below:
&am33xx_pinmux {
uart2_pins: pinmux_uart2
On Wed, Jul 27, 2016 at 11:38 AM Juliusz Chroboczek <
j...@pps.univ-paris-diderot.fr> wrote:
> >>> There is a race condition between booting and loading the Bluetooth
> >>> firmware. Reloading the firmware manually works around the issue.
>
> >> This has been haunting us for a while.
>
> Okay, I
Hi!
I want to use Mentorel Beaglebone uSomIQ with Tiwi-BLE chip but don't know
which kernel version supports it. I used v3.2 some time ago but need to
migrate to one of latest kernels. Please suggest the kernel with support
for TI wl127x chips
--
For more options, visit http://beagleboard.org/di
LR,
I did a quick g-search.
Found:
http://www.iebmedia.com/index.php?id=5543&parentid=63&themeid=255&showdetail=true
There are apparently several ways to implement the 1588 protocol. From all
software to a combo of
hardware and software. Most however don't seem to need a specific phy
solution.
LR,
I don't believe that the Phy is what determines the 1588 compliance. My
understanding is that it is the MAC.
On the BBB the MAC is what is 1588 compliant. The 8710 phy says nothing
about this. As a matter of fact,
none of the datasheets I have on phys say anything about 1588. The phy is
jus
On 7/28/2016 2:52 AM, William Hermans wrote:
> Charles,
>
> Also, I've been meaning to ask you what you'd think of individual pin overlay
> files based on universal-IO. I have all of P8 done, or most of( I don't wont
> touch the eMMC pins - but HDMI + audio is fair game).
> Was considering how
Hello,
The specs for the new X15 are quite impressive. However I think it is
missing one thing: PHY chips that support IEEE 1588, i.e. Precision Time
Protocol (PTP). For example: http://www.ti.com/product/DP83640 which is
TIs DP83640 chip. I think this would open up the board to even more
deve
We have no plans to do so at this time. The space on the board is very
tight and this device is larger that what is there now. It would take a lot
of work and the changing of the board dimensions to get it in.
Gerald
On Thu, Jul 28, 2016 at 1:25 AM, wrote:
> Hello,
>
> The specs for the new X15
We have no plans to do so at this time. The space on the board is very
tight and this device is larger that what is there now.
Gerald
On Thu, Jul 28, 2016 at 2:09 AM, wrote:
> The BeagleBoard-X15 has quite an impressive set of features. However I
> think that it is missing one thing: IEEE 1588
>> After some reading of the kernel sources (always a pleasure), I've found
>> how to enable 2x2 MIMO on the BBGW. I'm getting 77Mbit/s downstream (TCP
>> iperf), which is pretty cool, but only 22Mbit/s upstream.
> Is this AP/sta or adhoc mode?
Client mode to a WNDR 3700 situated in the next roo
Hi ,
I have made the SD card bootable and made partions as boot, rootfs. Under
boot i have copied MLO,u-boot.img.uEnv.txt and zImage. Under rootfs i have
copied the root file system. After that i inserted SD card into BBB and
hold the S2 button during power up , after this i can observe all
The BeagleBoard-X15 has quite an impressive set of features. However I
think that it is missing one thing: IEEE 1588 Precision Time Protocol (PTP)
PHY chips. For example, http://www.ti.com/product/DP83640 which is
TI's DP83640 PHY chip.
I believe the board as is will be great for doing real-ti
Hello,
I am trying to interface a USB web cam on beaglebone black android. I can
see the device is created as /dev/video0 but when I call
getNumberOfCameras() from my application code it always return 0. Is there
a limitation in Android on connecting USB camera?
Any Idea how to fix it and how
Hello William,
the output is:
root@beaglebone:/lib/firmware# ls /sys/devices/platform/ocp/
4030.ocmcram 4740.usb 48046000.timer 4819c000.i2c
48302000.epwmss 4a10.ethernet modalias
ocp:P9_22_pinmux
40302000.ocmcram_nocache 48022000.se
I use sublime text 3. And no device tree syntax is nothing like python.
On Thu, Jul 28, 2016 at 3:30 AM, Jane wrote:
> Can you name the editor?Is the dt is also like python where the Tabs and
> special character may ruin its compiling?
> Also does dtc compiler checks for the sanity of the file
Can you name the editor?Is the dt is also like python where the Tabs and
special character may ruin its compiling?
Also does dtc compiler checks for the sanity of the file besides checking
these tabs,syntax,etc.I mean what if it compiles fine but there is an issue
in the dt?
Also can you pleas
>
> However I could not produce any outputs. I measure all channels with an
> oscilloscope, but unfortunately no success. Do you know what I did wrong?
>
No. Did you test the correct pins ? Also what is the output of:
$ ls /sys/devices/platform/ocp/
?
On Thu, Jul 28, 2016 at 3:00 AM, wrote:
>
Hello William,
so I tried your approach however without success. Here is how I did it:
- I exported the capes to sys/devices/platform/bone_capemgr/slots.
This reads now as follows:
0: PF -1
1: PF -1
2: PF -1
3: PF -1
4: P-O-L- 0 Overr
Hello everybody,
how to set inputs/outputs or ADC in kernel (4.x) without installing cape
manager.
I'm assuming that the right way is editing *-overlay.dts in
(bb-kernel/KERNEL/arch/arm/boot/dts).
I see that u-boot also contains (/u-boot/arch/arm/dts) *-boneblack.dts
files for what is those fi
Charles,
Also, I've been meaning to ask you what you'd think of individual pin
overlay files based on universal-IO. I have all of P8 done, or most of( I
don't wont touch the eMMC pins - but HDMI + audio is fair game).
I got bored, when our internet bouncing equipment got struck by lightning
again
Thanks Charles. Read this last night, and been meaning to thank you for the
information. But kept getting sidetracked . .. gpio-of-helper, I have not
been able to find decent documentation on that, but I have not looked
recently. Probably somewhere in linux/documentation/ . . .
On Wed, Jul 27, 201
37 matches
Mail list logo
