Hi Mr. Nelson,
I made some progress,
mdev was auto-mounting /dev/mmcblk0* partitions, i changed following line
in the mdev.conf file.
*#mmcblk[0-9]p+[0-9]* root:root 660 */etc/mdev/mount.sh $MDEV*
*mmcblk[0-9]p+[0-9]* root:root 660 *
But i don't understand why auto-mounting was creating
Hi Matthijs,
On Wed, Apr 29, 2015, at 03:10 AM, Matthijs van Duin wrote:
The PMIC is not the problem here, it properly shuts down all DCDC and LDO
supplies, and requires no configuration other than voltage adjustments
when
desired, and setting the OFF bit before using the RTC to request
On Wednesday, 29 April 2015 17:30:14 UTC+2, Matthijs van Duin wrote:
Your original question is actually very easy to answer
I posted a bit too hastily since I missed the second half of your original
post.
If external hardware unconditionally drives or pulls up to 3V3EXP (in case
of BBW) or
Greetings Dimitar,
I can't thank you enough for the direction (I was afraid no one would want
to slog through all that). I'm also interested in the hardware part of it.
Are there any schematics for interfacing the camera to the board (will I
need caps, resistors, voltage translations)? The few
On Wednesday, 29 April 2015 20:18:51 UTC+2, Andrew Bradford wrote:
If you take a BBW and cut the trace coming from U8 pin 5 (the LDO enable
line) and then wire U8 pin 5 to the PWR_LED net on page 2 of the
schematic, then the U8 LDO will shutdown correctly when on battery.
It will shut
On Tue, Apr 28, 2015 at 9:20 PM, Robert Nelson robertcnel...@gmail.com
wrote:
Oh, it doesn't bother me; I reviewed the 8250_omap driver for
inclusion in mainline.
With all the generic improvements done to the base 8250 since the
omap_serial driver came out, it is a big improvement. But
On Wed, Apr 29, 2015, at 01:07 PM, Matthijs van Duin wrote:
On Wednesday, 29 April 2015 17:30:14 UTC+2, Matthijs van Duin wrote:
Your original question is actually very easy to answer
I posted a bit too hastily since I missed the second half of your
original
post.
If external
I've held down the button you're suggesting for nearly 2mins and no change
from booting from uSD. Once I eject the uSD and reboot the BBB i'm able to
boot into to the eMMC, which is running the flashed version of ubuntu. I'm
simply attempting to run the ubuntu desktop now(from uSD),
On Wed, Apr 29, 2015 at 3:50 PM, Tim M timlorimurta...@hotmail.com wrote:
I've held down the button you're suggesting for nearly 2mins and no
change from booting from uSD. Once I eject the uSD and reboot the BBB i'm
able to boot into to the eMMC, which is running the flashed version of
ubuntu.
Robert,
Unfortunately I don't have a ftdi usb-serial cable. But if I get one, can
you refer me to instructions on how to use it?
Thanks,
Tim
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard
Got a kernel panic on Jessie running kernel 3.14.39-ti-r61:
BBB rev C.
TP-Link TL WN722N.
Wall wart power.
No capes.
Is there anywhere else I should post this?
[ 439.103374] Unable to handle kernel paging request at virtual address
01010241
[ 439.111041] pgd = c0004000
[ 439.113910]
What is it you do not know about using a serial debug cable Tim ?
On Wed, Apr 29, 2015 at 2:05 PM, Tim M timlorimurta...@hotmail.com wrote:
Robert,
Unfortunately I don't have a ftdi usb-serial cable. But if I get one, can
you refer me to instructions on how to use it?
Thanks,
Tim
--
On Wed, Apr 29, 2015 at 4:53 PM, Dan Lipsitt d...@typeamachines.com wrote:
Got a kernel panic on Jessie running kernel 3.14.39-ti-r61:
BBB rev C.
TP-Link TL WN722N.
I have this one too, so i can test it at home.. DOes the opps go away
when it's not plugged in?
Wall wart power.
No capes.
Thank you for the response (and sorry for my lack of update!been
traveling).
I'll update and let you know if there's an improvement.
Thanks!
On Tuesday, April 7, 2015 at 6:51:38 AM UTC-7, RobertCNelson wrote:
On Mon, Apr 6, 2015 at 11:25 PM, Andris Bjornson and...@everylayer.com
Here's another, from different BBB with the same setup:
[Apr29 23:08] hrtimer: interrupt took 387492 ns
[Apr29 23:15] INFO: task kworker/0:1:15 blocked for more than 120 seconds.
[ +0.006971] Tainted: G O 3.14.39-ti-r61 #1
[ +0.017714] echo 0
[ +8.711840] [ cut here ]
[ +0.004777] kernel BUG at mm/slab.c:2919!
[ +0.004088] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
[ +0.005940] Modules linked in: ctr ccm usb_f_acm u_serial usb_f_ecm
g_multi usb_f_mass_storage usb_f_rndis u_ether libcomposite arc4
Robert, is there a 3.14 kernel you consider stable? Have you tested the
previous one (3.14.38-ti-r60) much?
We also want compatibility with the Logicsupply UWN-200 (MediaTek MT7601)
adaptor, but it looks like we may be better off with kernel 3.8 for that.
Thanks,
Dan
--
For more options,
Another:
[ 65.549033] Unable to handle kernel paging request at virtual address
0101020d
[ 65.556700] pgd = c0004000
[ 65.562498] [0101020d] *pgd=
[ 65.567712] Internal error: Oops: 805 [#1] PREEMPT SMP ARM
[ 65.573493] Modules linked in: ctr ccm usb_f_acm u_serial usb_f_ecm
On Wednesday, April 29, 2015 at 3:08:05 PM UTC-7, RobertCNelson wrote:
DOes the opps go away
when it's not plugged in?
Hard to tell because it's intermittent. I'm currently trying to trigger it
with the wifi adaptor still plugged in. I got two panics in a row and now I
can't reproduce
Hi,
Same problem here. Have you checked md5sum of latest Debian image ? I have
downloaded the same latest image 3 times, but every time my md5sum was
giving checksum = 725d3fa63c0b1b0cc47b44f5c3f56238 which is different as
per the website. So its not booting from sd card.
--
For more
I've got a problem with configuration of SPI1 of BeagleBone White using
PRU. The SPI works with external ADC in receive only mode
during boot (ubuntu minimal) I do pin mux:
//SPI CLK (output, mode3)
echo 13 /sys/kernel/debug/omap_mux/mcasp0_aclkx
//D1 (input, pull-up, mode3)
echo 33
Using RevC produce similar problems.
New power adaptors, same problems.
On Sunday, February 2, 2014 at 11:18:36 AM UTC+1, MV wrote:
With a new power adaptor (BBB side) no more noise, but same problems.
When reboot BBB does not more recognize USB port, and the connected
arduino USB-serial.
I am trying to setup Matplotlib for my Angstrom Beaglebone. I followed
instructions here:
http://matplotlib.org/faq/installing_faq.html#install-from-git and
downloaded matplotlib succesfully.
python setup.py install
it results with following error. I installed numpy. Why do I get this
On Sunday, January 18, 2015 at 4:08:15 PM UTC-8, Robert Fisher wrote:
OK, I found your apt repository. I got that set up and the installation
seemed successful, but upon reboot I'm still running my original 3.18
according to uname -a.
I am trying to install that kernel and have not found
On Wed, Apr 29, 2015 at 7:43 AM, nilesh.tek...@volansystech.com wrote:
Hi,
Same problem here. Have you checked md5sum of latest Debian image ? I have
downloaded the same latest image 3 times, but every time my md5sum was
giving checksum = 725d3fa63c0b1b0cc47b44f5c3f56238 which is different
hi,
I got problem with SPI configuration (receive only mode for ADC) using PRU,
first the system setup:
during boot (ubuntu minimal) does:
#SPI CLK - output, mode 3
echo 13 /sys/kernel/debug/omap_mux/mcasp0_aclkx
#D1 - input, mode 3, pulled-up
echo 33 /sys/kernel/debug/omap_mux/mcasp0_axr0
Hi, I am planning of using BeagleBone in my Project..I plan to install
Android OS and develop and Android Application to run on the BeagleBone
with a TouchScreen in place for the GUI
There will be an xBEE module connected to the Board...What if i want to use
the Rx-Tx peripherals present
Hi all.
Once I upgraded BBB to 4.0 I have noticed section below, which configures
P9_41.
am33xx_pinmux {
pinctrl-names = default;
pinctrl-0 = clkout2_pin;
};
I need this pin to work as gpio output.
Is it safe to disable this and release the P9_41 pin?
What does clkout2 do?
Why
Hi all.
After BBB boots up there is no /dev/i2c-0 nor /dev/i2c-1.
Even if I use modprobe and the do appear, I can't see eeprom in appropriate
folder.
Is it my fault or it will be fixed in bone1 version of 4.0 kernel?
root@beaglebone:~# ls /dev/i
iio:device0 initctl input/
Hi all.
When I connect BBB with 4.0 kernel to Windows 7 it detects only Gadget USB
network card. It doesn't detect USB mass storage.
Everything works as it should when connected to laptop running Debian.
Same BBB loaded with 3.8.13 doesn't have that problem. Works fine on both
Windows and
I am testing the Beaglebone black C and LCD 4DCAPE-70T that provides
touch panel. I am eager to use ADconveters on the BBB. But the touch panel
can not work well when AD convters work. Sometimes CPU halts at all.
For example
*root@beaglebone*
On Mon, Apr 27, 2015 at 8:34 PM, mjmccl...@gmail.com wrote:
On Sunday, January 18, 2015 at 4:08:15 PM UTC-8, Robert Fisher wrote:
OK, I found your apt repository. I got that set up and the installation
seemed successful, but upon reboot I'm still running my original 3.18
according to uname
I meant that I've never used the debug port and an FTDI cable on the BBB. I
assume I would connect to the BBB using a serial terminal program (in my
case I would be connecting from Windows). When Robert said I could prove
it easily by plugging in a ftdi usb-serial cable into the debug port, I
Yes
It should boot from the onboard emmc.
Type “debian” as the username and “temppwd” as the password.
Then try “dmesg” to see all of the boot messages.
No one could make a greater mistake than he who did nothing because he could
do only a little.
All that is necessary for the
I am testing the Beaglebone black C and LCD displayer 4DCAPE-70T that is
pruced by 4D-systems now. If ADconveter that is installed in the beaglebone
black C works, the touch panel that is provided in 4DCAPE-70T works very
slowly and sometimes CPU halts at all.
For example
*root@beaglebone*
On Wednesday, 29 April 2015 14:00:17 UTC+2, Andrew Bradford wrote:
You seem to be talking about the BBB, correct?
Correct, though it seems nearly all posts in this thread are referring to
the BBB issue?
My initial work was on BBW back in 2012 (prior to BBB release).
It sounds like BBB has
36 matches
Mail list logo
