[beagleboard] Future of BeagleBone (Black)?
Hi, I'm aware of the fact that there can't be a obligatory answer to my question, so I'm happy with any kind of rumours and rough ideas: As far as I know TI does not further develop the AM335X series, more than this I remember an article where they stated they drop the whole mobile devices marked where this CPU was intended for originally. So I don't think there will be a multi core variant of this Sitara SoC or even a version with higher clock. So: what future could be there for the BeagleBone (Black)? Will there be a somehow compatible successor? Or what else is planned? Thanks! Karl -- 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] Future of BeagleBone (Black)?
On 19/05/15 16:45, Karl Karpfen wrote: So: what future could be there for the BeagleBone (Black)? Will there be a somehow compatible successor? Or what else is planned? Well, there's the upcoming X15. http://elinux.org/Beagleboard:BeagleBoard-X15 And if I were a betting man, I'd put a few dollars on there eventually being a small version of that, as much as the BBB is a small version of the larger Board/Board xM thing. 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: [beagleboard] will a buildroot build for BBB work out of the box?
Thanks. With luck this is just for the record … bootpart=0:1 bootdir= bootfile=zImage uenvcmd=run loadimage;run loadramdisk;run findfdt;run loadfdt;run ramboot Lets see what your uEnv.txt looks like. -- 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: Problem with capacitive touchscreen driver ft5x06 no input event
Hello Jim, I'm currently using the kernel 3.14. I modified the bbb-exp-c dtb to have the good resolution and it worked. Good luck -- 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: Disabling HDMI makes mounted drives not authorized
That all makes perfect sense William. I have the debug cable already, I have learned the benefit of lowest level communication possible a long time ago. You don't always need it, but... Dig your e-mail address by the way, I was/am a huge Elric fan, indeed all the Eternal Champion stuff. Thanks again for your super help. Respectfully, Jack On Monday, May 18, 2015, William Hermans yyrk...@gmail.com wrote: As an aside / semi correction to what I wrote. I believe that u-boot has the USB serial gadget built in. Not sure how to go about using it, but I also believe it has to be loaded by u-boot first so will not give you as much output as a serial debug cable. If you're wondering if an FTDI cable is worth the $20 . . . it is. However I actually got a $2 prolific cable off ebay from China. That works fine. It's exactly the same as the new one ADA Fruit sells. You just need to make sure it's 3v3 TTL. If this is confusing to you, just stick with the recommended cables / adapters from the beagleboard.org ewiki pages. On Mon, May 18, 2015 at 4:50 PM, William Hermans yyrk...@gmail.com javascript:_e(%7B%7D,'cvml','yyrk...@gmail.com'); wrote: *just a newb trying to follow along and learn, byt he serial debug cable you mean the FTDI 3.3V serial-USB cable with the six pin header? It seems this one gives insight at a lower level than the straight mini-USB port...* Yes. The USB serial gadget driver is not funcitonal until the OS has control, and loads the driver. Where as the serial debug is functional far earlier. From memory, the serial debug serial interface is loaded late x-loader / MLO, but either way. For all intents and purposes. When u-boot is loaded into memory( and operational ), this is where you have communication potential with the system. This means you're able to view all uboot output, as well as when the kernel takes control of the board. You get all boot up kernel output as well. With the USB gadget, you will not get any ouput until late Linux boot, if any at all. The main purpose of the serial debug cable is exactly as the name implies. Debugging in the sense of something akin to code debugging using printf() in C. But it can also come in handy in a pinch for other uses as well. Such as gaining access to the board when there are no other means. On Mon, May 18, 2015 at 4:27 PM, Jack Fisher lotusf...@gmail.com javascript:_e(%7B%7D,'cvml','lotusf...@gmail.com'); wrote: William and Sam, Just a newb trying to follow along and learn, byt he serial debug cable you mean the FTDI 3.3V serial-USB cable with the six pin header? It seems this one gives insight at a lower level than the straight mini-USB port... Sorry for my gross ignorance, but I am working on that... Regards, Jack On Thursday, May 7, 2015 at 6:14:47 PM UTC-7, Sam wrote: Don't be sorry! I appreciate the help. It's a bit weird. Especially since no one else seems to be having the issue. I'll order myself a cable and continue the investigation. On Fri, 8 May 2015 9:59 am William Hermans yyr...@gmail.com wrote: Sorry I couldn't help more Sam . . . This problem seems kind of obscure to me. I do not remember reading about, or hearing of a similar issue. If you did happen to buy, or borrow a serial debug cable. You could run both configurations, logging the boot log output to file. Then run a diff on them to see if anything stands out. You can also try this with dmesg . . . and . . . just poking around myself . . . debian@beaglebone:~$* dmesg ~/file* debian@beaglebone:~$ *nano ./file* *[3.590829] bone-pinmux-helper P8_27_pinmux.18: Set initial pinmux mode to hdmi* *[3.598760] bone-pinmux-helper P8_28_pinmux.19: Set initial pinmux mode to hdmi* *[3.606640] bone-pinmux-helper P8_29_pinmux.20: Set initial pinmux mode to hdmi* *[3.614507] bone-pinmux-helper P8_30_pinmux.21: Set initial pinmux mode to hdmi* *[3.622286] bone-pinmux-helper P8_31_pinmux.22: Set initial pinmux mode to hdmi* *[3.630087] bone-pinmux-helper P8_32_pinmux.23: Set initial pinmux mode to hdmi* *[3.637903] bone-pinmux-helper P8_33_pinmux.24: Set initial pinmux mode to hdmi* *[3.645782] bone-pinmux-helper P8_34_pinmux.25: Set initial pinmux mode to hdmi* *[3.653558] bone-pinmux-helper P8_35_pinmux.26: Set initial pinmux mode to hdmi* *[3.661459] bone-pinmux-helper P8_36_pinmux.27: Set initial pinmux mode to hdmi* *[3.669453] bone-pinmux-helper P8_37_pinmux.28: Set initial pinmux mode to hdmi* *[3.677472] bone-pinmux-helper P8_38_pinmux.29: Set initial pinmux mode to hdmi* *[3.685519] bone-pinmux-helper P8_39_pinmux.30: Set initial pinmux mode to hdmi* *[3.693538] bone-pinmux-helper P8_40_pinmux.31: Set initial pinmux mode to hdmi* *[3.701634] bone-pinmux-helper P8_41_pinmux.32: Set initial pinmux mode to hdmi* *[3.709755] bone-pinmux-helper P8_42_pinmux.33: Set initial pinmux mode to hdmi* *[3.717978]
Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.
On Tue, May 19, 2015 at 3:56 PM, Robert Nelson robert...@gmail.com javascript: wrote: We assume phy_mask to be 100% correct. Maybe we should just force the dt value of phy_id always into phy_mask? I really need to find a board that 'never' boots with 0xfffe.. Back when I had this problem people who received a phymask of fffe (like when my board worked) booted successfully, those with fffb (like when my board failed) - failed. The reply to my forum post back then said: --- They phymask comes from a hardware register read by the davinci_mdio driver, which gets passed to the linux phy libraries. The problem is that the cpsw driver gets the value from device tree, which is hardcoded to address 0. Usually the values are the same (address 0), but sometimes the phy gets registered to a different address, usually in my case address 2. You calculate the address using the phymask. If you changed the phymask than, you pointing back to address 0, so that wouldn't help you. --- Can the phy move to address 2? Lots of failing boards look for it there, but do any find it there? Humm, that is odd, it corrected for [phy mask fffb] with [4a101000.mdio:02] Indeed, when my board found fffb, it looked for address 2, just like the recent post. But back then it would never find a working phy there... -- Except for one time, when I was testing an RCN modified mmcboot in uenv.txt (the image that booted was on the uSD, so this must show a power-up with the button held): --- U-Boot 2013.10-00249-g15c5cdf (Nov 17 2013 - 16:35:11) ... [0.00] Linux version 3.8.13-bone30 (root@imx6q-sabrelite-1gb-1) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #1 SMP Thu Nov 14 11:19:20 UTC 2013 ... [2.467130] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [2.473591] davinci_mdio 4a101000.mdio: detected phy mask fffb [2.481082] libphy: 4a101000.mdio: probed [2.485347] davinci_mdio 4a101000.mdio: phy[2]: device 4a101000.mdio:02, driver SMSC LAN8710/LAN8720 [2.495182] Detected MACID = 90:59:af:4d:71:eb ... [6.246797] libphy: PHY 4a101000.mdio:00 not found [6.251852] net eth0: phy 4a101000.mdio:00 not found on slave 0 [6.258081] libphy: PHY 4a101000.mdio:01 not found [6.263119] net eth0: phy 4a101000.mdio:01 not found on slave 1 ... Welcome to Ubuntu 12.04.4 LTS (GNU/Linux 3.8.13-bone30 armv7l) --- All the other logs I archived of that same board with the same boot files show fffe or failure, but that one disproves my original theory. Since I installed bone-ubuntu-14.04-console-2014-06-05-2gb.img I've never seen a problem. The same board just works. BTW: Messages that follow the initial detect/probe later in the boot, like [6.258081] libphy: PHY 4a101000.mdio:01 not found [6.263119] net eth0: phy 4a101000.mdio:01 not found on slave 1 are not really errors - the phy at 00 could have a second slave at the next address, but never does. These messages just repeat over and over to clutter the logs. -- 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] Future of BeagleBone (Black)?
May 19th 2015 16.39.22 UTC+2 Karl/Gerald/Mickae1 wrote:
As far as I know TI does not further develop the AM335X series, more
than this I remember an article where they stated they drop the whole
mobile devices marked where this CPU was intended for originally.
BeagleBone Black at this point has no processor future due to TI's dead
end road map.
Hi, where did you get those information? Where did Texas say that it is
over for the am335x?
Second that, sources and/or further insights would be nice if this is
general knowledge affecting development prioritizations. Might lead to
better understanding out here for the lack of attention to the current
BeagleBone {W,B,G} products.
Finding no publicly communicated indications of TI reconsidering mobile,
Sitara or AM335x. Officially AM3358 is marked as active on
http://www.ti.com/product/AM3358, and
http://e2e.ti.com/support/arm/sitara_arm/f/791/p/152524/560202 describes 10
years availability of AM335x (released 2011-10-31). I guess then that
manufacturing of BBB based designs is possible until 2021 (at least
processor wise).
But I hear your saying that we shouldn't expect further developments and a
bright shiny future for the current incarnation of the BeagleBone boards?
Mikkel
--
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] Future of BeagleBone (Black)?
On Tue, May 19, 2015 at 7:20 PM, m...@mikini.dk wrote:
May 19th 2015 16.39.22 UTC+2 Karl/Gerald/Mickae1 wrote:
As far as I know TI does not further develop the AM335X series, more
than this I remember an article where they stated they drop the whole mobile
devices marked where this CPU was intended for originally.
BeagleBone Black at this point has no processor future due to TI's dead
end road map.
Hi, where did you get those information? Where did Texas say that it is
over for the am335x?
Second that, sources and/or further insights would be nice if this is
general knowledge affecting development prioritizations. Might lead to
better understanding out here for the lack of attention to the current
BeagleBone {W,B,G} products.
TI's roadmap's are kinda funny..
While there is no pin for pin am335x++, the am43xx is the sudo
sucessor to the am335x...
Finding no publicly communicated indications of TI reconsidering mobile,
Sitara or AM335x. Officially AM3358 is marked as active on
http://www.ti.com/product/AM3358, and
http://e2e.ti.com/support/arm/sitara_arm/f/791/p/152524/560202 describes 10
years availability of AM335x (released 2011-10-31). I guess then that
manufacturing of BBB based designs is possible until 2021 (at least
processor wise).
Correct, 10 year plan unless something major happens.. The am335x has
been a pretty good success..
But I hear your saying that we shouldn't expect further developments and a
bright shiny future for the current incarnation of the BeagleBone boards?
There's other 3rd party boards, such as seeed studio's BeagleBone Green. ;)
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.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] BeagleBone Black PWM on QNX OS
http://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/TiAm335Beaglebone 2015-05-18 10:31 GMT+08:00 Charles Steinkuehler char...@steinkuehler.net: On 5/17/2015 8:03 AM, amir@gmail.com wrote: I would like to have a PWM output signal from BeagleBone Black. I have to use QNX operating System (due to Real-Time Constraints) on my BeagleBone. Do you have any suggestions how to do that? There is no out of the box QNX bsp to do that. If you want to use QNX, you'll have to perform all the hardware setup and configuration yourself. It's reasonably straight-forward to interface to the PWM registers (see the TRM for details), but you'll also need to setup the clock multiplexing and resets before anything will work at all. The Linux kernel code is a great reference for getting the clocks/resets configured properly, or you can refer to the TI bare-metal example applications. ...or see if the QNX folks will make a proper AM335x BSP for you. :) -- Charles Steinkuehler char...@steinkuehler.net -- 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] BeagleBone Black PWM on QNX OS
Sorry , missing the key driver of pwm . As I remember , QNX dont have the pwm as a architecture driver . maybe from other bsp source as a reference ? 2015-05-20 10:48 GMT+08:00 liyaoshi liyao...@gmail.com: http://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/TiAm335Beaglebone 2015-05-18 10:31 GMT+08:00 Charles Steinkuehler char...@steinkuehler.net : On 5/17/2015 8:03 AM, amir@gmail.com wrote: I would like to have a PWM output signal from BeagleBone Black. I have to use QNX operating System (due to Real-Time Constraints) on my BeagleBone. Do you have any suggestions how to do that? There is no out of the box QNX bsp to do that. If you want to use QNX, you'll have to perform all the hardware setup and configuration yourself. It's reasonably straight-forward to interface to the PWM registers (see the TRM for details), but you'll also need to setup the clock multiplexing and resets before anything will work at all. The Linux kernel code is a great reference for getting the clocks/resets configured properly, or you can refer to the TI bare-metal example applications. ...or see if the QNX folks will make a proper AM335x BSP for you. :) -- Charles Steinkuehler char...@steinkuehler.net -- 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: Bone VDD_3V3EXP Disable Issues
On 19 May 2015 at 22:41, Max msonnail...@gmail.com wrote: Did you try any change in the EN pin of U4 (enable signal of 3V3B)? No, we replaced U4 by this state-of-the-art voltage-tracking regulator: It can't supply as much current as the original, but our needs are modest enough. I'm about to try SYS_RESETn (PMIC_PGOOD after U16), but I'm concerned about the 20ms turn on delay (plus 10ms due to the RC). The other option is to go back to use 3V3AUX, and add a 1k load resistor to reduce the discharge time. I would advise against both of these choices: Only PORz guarantees that the AM335x IOs will be high-Z, SYS_RESETn is deasserted considerably later during power-on. Using it would also case 3v3b to be power-cycled during warm reset, which may have pros and cons but in any case if I'm reading the TRM right it is asserted too early in this case and therefore there's a risk the AM335x ends up driving into unpowered external peripherals. Any reason why you're not considering PMIC_PGOOD itself? In general I'd restrict to PMIC signals that transition somewhere between strobe 4 and PGOOD, which makes PGOOD itself basically the only signal that qualifies. If you do use LDO2 (3v3aux) for whatever reason, try to avoid having any signal to the AM335x being driven high from the 3v3b during boot. In particular, avoid having a console cable connected at boot (at least during production use) given the stress this would put on the UART0_RXD pin. It would then also be a good idea to reprogram LDO2 to strobe 7 as soon as possible during early boot (preferably in the SPL). A load resistor on 3v3b may be a good idea anyway since it lacks the active discharging that the PMIC LDOs have. -- 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] DTS for keyboard Keys question
Hello there,
I am trying to create a dts file for an 8 buttons keyboard. The pins I am
using are:
P8_35,
P8_36,
P8_39,
P8_40,
P8_41,
P8_42,
P8_43,
P8_44
HDMI is turned off. Using Dereks molloy book, I have found an example dts
file for P9_15 key: https://pastebin.com/kKp3ji7s
There are 2 main parts for me:
pinctrl-single,pins =
0x040 0x37 // P9_15 pull-up mode 7 GPIO1_16
This first one is quite straight forward for me, I have chnaged it to my
needs:
pinctrl-single,pins =
0x0d0 0x37 // P8_35 pull-up mode 7
0x0c8 0x37 // P8_36 pull-up mode 7
0x0b8 0x37 // P8_39 pull-up mode 7
0x0bc 0x37 // P8_40 pull-up mode 7
0x0b0 0x37 // P8_41 pull-up mode 7
0x0b4 0x37 // P8_42 pull-up mode 7
0x0a8 0x37 // P8_43 pull-up mode 7
0x0ac 0x37 // P8_44 pull-up mode 7
The problem is I dont know how to config this part:
button_P9_15 {
debounce_interval = 50;
linux,code = 28;
label = button9_15;
gpios = gpio2 16 0x1;
gpio-key,wakeup;
autorepeat;
I dont know how to interpret gpios = gpio2 16 0x1;. I Think that 16
0x1 stands for Gpio1[16], but I dont know what does gpio2 stands for.
Please correct me if I am wrong. What would be the configuration for the
P8_44 button? I tried gpios = gpio2 9 0x2; but that did not work. The
overlay loaded but the button doesnt work. It is wired correctly though. I
Would aprichiate all 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] DTS for keyboard Keys question
On Tue, May 19, 2015 at 9:08 AM, Bremenpl breme...@gmail.com wrote: This is 3.8+. So is gpio2 = gpio3? Then in my case, if my button lines are internally pulled up and the keys short them to gnd, should i use: gpios = gpio3 9 0x0; ? Correct 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Kernel panic trying to load SD-Card
On Tue, May 19, 2015 at 9:00 AM, Dennis Kerrisk dennisk8...@gmail.com wrote: Every time I try to load code from an SD-card it kernel panics. I have tried to load several different images. This is from the console: - Formatting: /dev/mmcblk1 complete - Copying: /dev/mmcblk0p1 - /dev/mmcblk1p1 rsync: /boot/uboot/ - /tmp/boot/ rsync: ignore the % values when shown as they are not accurate... [ 180.521791] INFO: task mmcqd/0:71 blocked for more than 60 seconds. [ 180.530529] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 180.540762] mmcqd/0 D c04d04a5 071 2 0x [ 180.549470] Kernel panic - not syncing: hung_task: blocked tasks [ 180.557784] [c00114f1] (unwind_backtrace+0x1/0x9c) from [c04cb2fd] (panic +0x59/0x15c) [ 180.568424] [c04cb2fd] (panic+0x59/0x15c) from [c0073955] (watchdog+0x19d /0x1c0) [ 180.578647] [c0073955] (watchdog+0x19d/0x1c0) from [c00454eb] (kthread+0x 6b/0x78) [ 180.588954] [c00454eb] (kthread+0x6b/0x78) from [c000c8fd] (ret_from_fork +0x11/0x34) [ 180.599525] drm_kms_helper: panic occurred, switching back to text console Any Ideas what I can try next? This is an issue with 3.8.x.. Try any other manufacture's microSD card and a good known 5volt dc power supply. Later kernels (such as 3.14.x) handle this much better.. 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] DTS for keyboard Keys question
Thank you, gonna test it asap. On May 19, 2015 4:12:37 PM Robert Nelson robertcnel...@gmail.com wrote: On Tue, May 19, 2015 at 9:08 AM, Bremenpl breme...@gmail.com wrote: This is 3.8+. So is gpio2 = gpio3? Then in my case, if my button lines are internally pulled up and the keys short them to gnd, should i use: gpios = gpio3 9 0x0; ? Correct 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/aEGy-NGt81I/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. -- 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] DTS for keyboard Keys question
On Tue, May 19, 2015 at 8:51 AM, bremenpl breme...@gmail.com wrote:
Hello there,
I am trying to create a dts file for an 8 buttons keyboard. The pins I am
using are:
P8_35,
P8_36,
P8_39,
P8_40,
P8_41,
P8_42,
P8_43,
P8_44
HDMI is turned off. Using Dereks molloy book, I have found an example dts
file for P9_15 key: https://pastebin.com/kKp3ji7s
There are 2 main parts for me:
pinctrl-single,pins =
0x040 0x37 // P9_15 pull-up mode 7 GPIO1_16
This first one is quite straight forward for me, I have chnaged it to my
needs:
pinctrl-single,pins =
0x0d0 0x37 // P8_35 pull-up mode 7
0x0c8 0x37 // P8_36 pull-up mode 7
0x0b8 0x37 // P8_39 pull-up mode 7
0x0bc 0x37 // P8_40 pull-up mode 7
0x0b0 0x37 // P8_41 pull-up mode 7
0x0b4 0x37 // P8_42 pull-up mode 7
0x0a8 0x37 // P8_43 pull-up mode 7
0x0ac 0x37 // P8_44 pull-up mode 7
The problem is I dont know how to config this part:
button_P9_15 {
debounce_interval = 50;
linux,code = 28;
label = button9_15;
gpios = gpio2 16 0x1;
gpio-key,wakeup;
autorepeat;
I dont know how to interpret gpios = gpio2 16 0x1;. I Think that 16 0x1
stands for Gpio1[16], but I dont know what does gpio2 stands for. Please
correct me if I am wrong. What would be the configuration for the P8_44
button? I tried gpios = gpio2 9 0x2; but that did not work. The overlay
loaded but the button doesnt work. It is wired correctly though. I Would
aprichiate all help.
Well, first is this v3.8.x or anything later?
In 3.8.x: Gpio1[16] = gpio2
while, in 3.14.x: Gpio1[16] = gpio1 ;)
So for 3.8.x: GPIO1[16]
gpios = gpio2 16 0x1;
gpio2 = GPIO1
16 = 16
0x1: GPIO_ACTIVE_HIGH (0x0 = GPIO_ACTIVE_LOW)
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.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Board selection
Not much of a spec. Nothing about how much you are willing to pay for this board. Nothing about processor frequency. But, as long as this is all you care about, the BeagleBone Black can handle this with added circuitry. Gerald On Tue, May 19, 2015 at 8:37 AM, bilalelh...@gmail.com wrote: Hello, We are looking for a board which allows us to build a costum board with these specific futures: -GB Ethernet, -USB -8 bit Parallel camera interface -Ubuntu We want to know which of these boards are the most optimat for our needs. thank you for your support. -- 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. -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- 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] Removing BeagleBoneBlack USB driver from Windows 7
https://lh3.googleusercontent.com/-CSSJRHzGyC8/VVqxE3aEVgI/ACU/EWeVd_r1d6U/s1600/USB%2BDrivers.JPG Thank you for your response. I looked in the device manager tree showing hidden devices and I'm not seeing anything that would give me a hint that it's the Beaglebone black driver. Thoughts on what it may be called? I'm thinking it may be a conflict because my backup drive is USB and the back up dashboard no longer sees the drive even though Windows does. Thanks On Thursday, May 14, 2015 at 10:01:32 PM UTC-5, William Hermans wrote: First, you may, or may not need to be running in safe mode. This part is unclear to me with Windows 7, but with WinXP this was all but a requirement. I always just remove drivers from Win7 in safe mode anyway . . . Second, you will likely have to do this with the board unplugged. Then once in device manager you would have to use view-show hidden devices. Then uninstall the device driver once found. Right click - uninstall etc. Typically, device driver installers have an uninstall executable as well. But unless things have changed recently, this driver does not have one. Lastly, I'm unsure how to approach the potential conflict problem. But I would probably start by making sure the backup drive was disconnected, and that you have drivers handy for it if needed. It's kind of hard for me to understand how that could happen, but in 3-4 years of using Windows 7 x64 . . . I've yet to run into a similar problem. Not saying it isn't possible though, just that I've not had the need to look into such a situation. On Thu, May 14, 2015 at 1:43 PM, TomTibbetts via BeagleBoard beagl...@googlegroups.com javascript: wrote: Hi. I'm trying to remove the BeagleBoneBlack USB driver from Windows 7 as I believe it is conflicting with a backup drive I have. I've searched for a way to do this but am not finding answers. Does anyone know how to do this? Thanks -- 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 javascript:. 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: Add a new cape for BeagleBone
I apologize for my poor english. I admit that may sound strange. But, I would say that the capes are used to make prototypes and not a final product (consumer or industrial market). I will modify this in the manual. On Sunday, May 17, 2015 at 9:41:22 PM UTC+2, William Hermans wrote: Well somewhere in user manual it states something like lab / experimentation use only . . . Which i thought was odd in of its self anyhow. I wont be buying one. On Sun, May 17, 2015 at 12:06 PM, evilwulfie evilw...@gmail.com javascript: wrote: Just a note for you. Selling this in the USA requires you to get FCC approval. It also requires you to get approval from the cell phone providers. Its NOT cheap for approval. On 5/17/2015 11:21 AM, Gerald Coley wrote: Yes, you did. But I do not maintain that page. The people that do are listed there. I do not handle that page. I do not own that page. I cannot change that page to post your link. Gerald On Sat, May 16, 2015 at 4:01 AM, Pascal FIFRE pascal...@iotys.com javascript: wrote: Hi, Yesterday, I’ve told you that I‘ve created a wiki page for my new cape IOTCape. I’ve changed this wiki page to http://elinux.org/IOTYS:IOTCape. Thanks a lot for your help. Best Regards, Pascal *Pascal FIFRE* IOTYS 43, Garenne Poull ar Rouz 22300 LANNION www.iotys.com *De :* Pascal FIFRE [mailto:pascal...@iotys.com javascript:] *Envoyé :* vendredi 15 mai 2015 18:40 *À :* 'beagl...@googlegroups.com javascript:' *Objet :* Add a new cape for BeagleBone Hi, I want to add the my new cape (IOTCape) for BeagleBone to BeagleBone capes site. I’ve created a wiki page http://elinux.org/User:IOTCape based on the http://elinux.org/CircuitCo:BeagleBone_LCD3 wiki page. Attached to this mail you will find : · A user manual of this new cape. · DTS file for cape Thanks a lot for your help. Best Regards, *Pascal FIFRE* IOTYS 43, Garenne Poull ar Rouz 22300 LANNION www.iotys.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...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- Gerald ger...@beagleboard.org javascript: http://beagleboard.org/ http://circuitco.com/support/ -- 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 javascript:. 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 javascript:. 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] PRU_EVTOUT_1 sent from PRU0 does not clear with sysevent = PRU0_ARM_INTERRUPT
Hello all! I have been working on a code where in which I use the interrupt PRU_EVTOUT_1 as a heartbeat from the PRU to the host. Currently, however, I have not been able to clear the interrupt so that it can be sent again. A (partial) minimal example is found below. As it is, the code does not work (for me at least... maybe I'm doing something stupid). This code works when PRU_EVTOUT_1 is replaced by PRU_EVTOUT_0 or when PRU0_ARM_INTERRUPT is replaced by PRU1_ARM_INTERRUPT. I edited prussdrv.c to find out where the issue is coming from and it seems that the wrong bit is cleared in SECR1 using the values below. That is: - when I send PRU0_R31_VEC_VALID | PRU_EVTOUT_0, I get SERC1 = 0x8, which is correctly cleared by PRU0_ARM_INTERRUPT = 19 - when I send PRU0_R31_VEC_VALID | PRU_EVTOUT_1, I get SERC1 = 0x10, which is correctly cleared by PRU1_ARM_INTERRUPT = 20 That makes sense given that PRU0_R31_VEC_VALID | PRU_EVTOUT_1 = PRU1_ARM_INTERRUPT + 16. The second form is found in the example codes for prussdrv, whereas the first one is used in Derek Molloy's EBB (ultrasonic example, chapter 13). Is PRU_EVTOUT_1 from PRU0 the same as sending PRU_EVTOUT_0 from PRU1? That seems odd, but I wasn't able to figure it out from the reference guide. I must be doing something wrong, I just don't know what! Any help is appreciated! I am using the latest version of the am335x_pru_package (built directly from the repository). Cheers! *prumain.p:* .origin 0// start of program in PRU memory .entrypoint START// program entry point #define PRU0_R31_VEC_VALID 32 #define PRU_EVTOUT_0 3 #define PRU_EVTOUT_1 4 START: // Send interrupt to host MOV R31.b0, PRU0_R31_VEC_VALID | PRU_EVTOUT_1 // Wait for 1 second MOV r3, DELAY_MS DELAY: SUB r3, r3, 1 QBNE DELAY, r3, 0 // Send interrupt to host MOV R31.b0, PRU0_R31_VEC_VALID | PRU_EVTOUT_1 // Halt HALT *main.c:* /* Wait for PRU_EVTOUT_1 */ n = prussdrv_pru_wait_event(PRU_EVTOUT_1); printf(This is the PRU_EVTOUT_1 number %d.\n, n); prussdrv_pru_clear_event(PRU_EVTOUT_1, PRU0_ARM_INTERRUPT); /* Wait for PRU_EVTOUT_0 (will go through this one instead of waiting for the delay in prumain.p */ n = prussdrv_pru_wait_event(PRU_EVTOUT_1); printf(This is the PRU_EVTOUT_1 number %d.\n, n); prussdrv_pru_clear_event(PRU_EVTOUT_1, PRU0_ARM_INTERRUPT); -- 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] Board selection
Hello, We are looking for a board which allows us to build a costum board with these specific futures: -GB Ethernet, -USB -8 bit Parallel camera interface -Ubuntu We want to know which of these boards are the most optimat for our needs. thank you for your support. -- 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: Add a new cape for BeagleBone
That's mean that all the capes appear on the wiki site have FCC approval and CE approval for European Country? On Sunday, May 17, 2015 at 9:07:00 PM UTC+2, Wulf Man wrote: Just a note for you. Selling this in the USA requires you to get FCC approval. It also requires you to get approval from the cell phone providers. Its NOT cheap for approval. On 5/17/2015 11:21 AM, Gerald Coley wrote: Yes, you did. But I do not maintain that page. The people that do are listed there. I do not handle that page. I do not own that page. I cannot change that page to post your link. Gerald On Sat, May 16, 2015 at 4:01 AM, Pascal FIFRE pascal...@iotys.com javascript: wrote: Hi, Yesterday, I’ve told you that I‘ve created a wiki page for my new cape IOTCape. I’ve changed this wiki page to http://elinux.org/IOTYS:IOTCape. Thanks a lot for your help. Best Regards, Pascal *Pascal FIFRE* IOTYS 43, Garenne Poull ar Rouz 22300 LANNION www.iotys.com *De :* Pascal FIFRE [mailto:pascal...@iotys.com javascript:] *Envoyé :* vendredi 15 mai 2015 18:40 *À :* 'beagl...@googlegroups.com javascript:' *Objet :* Add a new cape for BeagleBone Hi, I want to add the my new cape (IOTCape) for BeagleBone to BeagleBone capes site. I’ve created a wiki page http://elinux.org/User:IOTCape based on the http://elinux.org/CircuitCo:BeagleBone_LCD3 wiki page. Attached to this mail you will find : · A user manual of this new cape. · DTS file for cape Thanks a lot for your help. Best Regards, *Pascal FIFRE* IOTYS 43, Garenne Poull ar Rouz 22300 LANNION www.iotys.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...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- Gerald ger...@beagleboard.org javascript: http://beagleboard.org/ http://circuitco.com/support/ -- 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 javascript:. 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] DTS for keyboard Keys question
This is 3.8+.
So is gpio2 = gpio3? Then in my case, if my button lines are internally
pulled up and the keys short them to gnd, should i use:
gpios = gpio3 9 0x0; ?
On May 19, 2015 4:04:30 PM Robert Nelson robertcnel...@gmail.com wrote:
On Tue, May 19, 2015 at 8:51 AM, bremenpl breme...@gmail.com wrote:
Hello there,
I am trying to create a dts file for an 8 buttons keyboard. The pins I am
using are:
P8_35,
P8_36,
P8_39,
P8_40,
P8_41,
P8_42,
P8_43,
P8_44
HDMI is turned off. Using Dereks molloy book, I have found an example dts
file for P9_15 key: https://pastebin.com/kKp3ji7s
There are 2 main parts for me:
pinctrl-single,pins =
0x040 0x37 // P9_15 pull-up mode 7 GPIO1_16
This first one is quite straight forward for me, I have chnaged it to my
needs:
pinctrl-single,pins =
0x0d0 0x37 // P8_35 pull-up mode 7
0x0c8 0x37 // P8_36 pull-up mode 7
0x0b8 0x37 // P8_39 pull-up mode 7
0x0bc 0x37 // P8_40 pull-up mode 7
0x0b0 0x37 // P8_41 pull-up mode 7
0x0b4 0x37 // P8_42 pull-up mode 7
0x0a8 0x37 // P8_43 pull-up mode 7
0x0ac 0x37 // P8_44 pull-up mode 7
The problem is I dont know how to config this part:
button_P9_15 {
debounce_interval = 50;
linux,code = 28;
label = button9_15;
gpios = gpio2 16 0x1;
gpio-key,wakeup;
autorepeat;
I dont know how to interpret gpios = gpio2 16 0x1;. I Think that 16 0x1
stands for Gpio1[16], but I dont know what does gpio2 stands for. Please
correct me if I am wrong. What would be the configuration for the P8_44
button? I tried gpios = gpio2 9 0x2; but that did not work. The overlay
loaded but the button doesnt work. It is wired correctly though. I Would
aprichiate all help.
Well, first is this v3.8.x or anything later?
In 3.8.x: Gpio1[16] = gpio2
while, in 3.14.x: Gpio1[16] = gpio1 ;)
So for 3.8.x: GPIO1[16]
gpios = gpio2 16 0x1;
gpio2 = GPIO1
16 = 16
0x1: GPIO_ACTIVE_HIGH (0x0 = GPIO_ACTIVE_LOW)
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/aEGy-NGt81I/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.
--
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] Future of BeagleBone (Black)?
If I knew that, I would have mentioned that. I would say maybe late September. We hope to have a few beta boards in about 6 weeks. Jason is handling who gets those boards. Right now, we are going back into layout to fix yet another TI feature. Gerald On Tue, May 19, 2015 at 9:06 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: On Tue, 19 May 2015, Gerald Coley wrote: BeagleBone Black at this point has no processor future due to TI's dead end road map. We are working on the BeagleBoard-X15 which is the next product to come out. Due to the form factor of the BBB, it cannot support the AM5728 processor. The BBB is just too small, but it does fit in the Altoids box. at what point will units be available? i wouldn't mind starting to move over my embedded linux and device driver courseware to the X15, at least in preparation for when the final units come out. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- 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] Future of BeagleBone (Black)?
BeagleBone Black at this point has no processor future due to TI's dead end road map. We are working on the BeagleBoard-X15 which is the next product to come out. Due to the form factor of the BBB, it cannot support the AM5728 processor. The BBB is just too small, but it does fit in the Altoids box. Gerald On Tue, May 19, 2015 at 2:05 AM, Peter Lawler relwalre...@gmail.com wrote: On 19/05/15 16:45, Karl Karpfen wrote: So: what future could be there for the BeagleBone (Black)? Will there be a somehow compatible successor? Or what else is planned? Well, there's the upcoming X15. http://elinux.org/Beagleboard:BeagleBoard-X15 And if I were a betting man, I'd put a few dollars on there eventually being a small version of that, as much as the BBB is a small version of the larger Board/Board xM thing. 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- 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 panic trying to load SD-Card
Every time I try to load code from an SD-card it kernel panics. I have tried to load several different images. This is from the console: - Formatting: /dev/mmcblk1 complete - Copying: /dev/mmcblk0p1 - /dev/mmcblk1p1 rsync: /boot/uboot/ - /tmp/boot/ rsync: ignore the % values when shown as they are not accurate... [ 180.521791] INFO: task mmcqd/0:71 blocked for more than 60 seconds. [ 180.530529] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 180.540762] mmcqd/0 D c04d04a5 071 2 0x [ 180.549470] Kernel panic - not syncing: hung_task: blocked tasks [ 180.557784] [c00114f1] (unwind_backtrace+0x1/0x9c) from [c04cb2fd] (panic +0x59/0x15c) [ 180.568424] [c04cb2fd] (panic+0x59/0x15c) from [c0073955] (watchdog+0x19d /0x1c0) [ 180.578647] [c0073955] (watchdog+0x19d/0x1c0) from [c00454eb] (kthread+0x 6b/0x78) [ 180.588954] [c00454eb] (kthread+0x6b/0x78) from [c000c8fd] (ret_from_fork +0x11/0x34) [ 180.599525] drm_kms_helper: panic occurred, switching back to text console Any Ideas what I can try next? Dennis -- 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] Future of BeagleBone (Black)?
On Tuesday, May 19, 2015 at 10:14:20 AM UTC-4, Gerald wrote: If I knew that, I would have mentioned that. I would say maybe late September. We hope to have a few beta boards in about 6 weeks. Jason is handling who gets those boards. Right now, we are going back into layout to fix yet another TI feature. Will the cape interface stay the same? Philip Gerald On Tue, May 19, 2015 at 9:06 AM, Robert P. J. Day rpj...@crashcourse.ca javascript: wrote: On Tue, 19 May 2015, Gerald Coley wrote: BeagleBone Black at this point has no processor future due to TI's dead end road map. We are working on the BeagleBoard-X15 which is the next product to come out. Due to the form factor of the BBB, it cannot support the AM5728 processor. The BBB is just too small, but it does fit in the Altoids box. at what point will units be available? i wouldn't mind starting to move over my embedded linux and device driver courseware to the X15, at least in preparation for when the final units come out. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- Gerald ger...@beagleboard.org javascript: http://beagleboard.org/ http://circuitco.com/support/ -- 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] Future of BeagleBone (Black)?
On Tue, May 19, 2015 at 9:24 AM, Philip philip.balis...@gmail.com wrote: On Tuesday, May 19, 2015 at 10:14:20 AM UTC-4, Gerald wrote: If I knew that, I would have mentioned that. I would say maybe late September. We hope to have a few beta boards in about 6 weeks. Jason is handling who gets those boards. Right now, we are going back into layout to fix yet another TI feature. Will the cape interface stay the same? Nope, and don't mention stuff like that, we don't want to give Gerald a heart attack.. 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Future of BeagleBone (Black)?
Hi, where did you get those information? Where did Texas say that it is over for the am335x? Le mar. 19 mai 2015 16:30, Robert Nelson robertcnel...@gmail.com a écrit : On Tue, May 19, 2015 at 9:24 AM, Philip philip.balis...@gmail.com wrote: On Tuesday, May 19, 2015 at 10:14:20 AM UTC-4, Gerald wrote: If I knew that, I would have mentioned that. I would say maybe late September. We hope to have a few beta boards in about 6 weeks. Jason is handling who gets those boards. Right now, we are going back into layout to fix yet another TI feature. Will the cape interface stay the same? Nope, and don't mention stuff like that, we don't want to give Gerald a heart attack.. 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. 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 panic loading firmware from SD-card
I am getting a kernel panic when I try to load firmware from an SD-card. I have tried several different images. Any suggestions what else I can try? Here is the console output: Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. [ 120.521745] INFO: task mmcqd/0:71 blocked for more than 60 seconds. [ 120.530919] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 120.541666] mmcqd/0 D c04d04a5 071 2 0x [ 120.550934] Kernel panic - not syncing: hung_task: blocked tasks [ 120.559813] [c00114f1] (unwind_backtrace+0x1/0x9c) from [c04cb2fd] (panic+0x59/0x15c) [ 120.571000] [c04cb2fd] (panic+0x59/0x15c) from [c0073955] (watchdog+0x19d/0x1c0) [ 120.581792] [c0073955] (watchdog+0x19d/0x1c0) from [c00454eb] (kthread+0x6b/0x78) [ 120.592698] [c00454eb] (kthread+0x6b/0x78) from [c000c8fd] (ret_from_fork+0x11/0x34) [ 120.603876] drm_kms_helper: panic occurred, switching back to text console -- 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: Beaglebone root access
I guess so too. I did in fact (with some trouble) and sudo -i works as before. Thanks! Harke On Mon, May 18, 2015 at 6:11 PM, William Hermans yyrk...@gmail.com wrote: Sounds like it is time for you to try out a new image . . . On Mon, May 18, 2015 at 8:50 AM, Harke Smits yrra...@gmail.com wrote: sudo -i also does not work anymore. On Monday, 18 May 2015 15:07:29 UTC+2, Harke Smits wrote: Hello, I must have done something stupid because all of a sudden /root is no longer existing or better probably: no more accessible. The ls command result starts with /bin . ends with /usr. But no /root anymore. Very annoying of course. I also no longer have access to IO pins. Please help. Thanks in advance Harke -- 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/nJPMi1n2WIg/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. -- 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] kernel panic loading firmware from SD-card
On Tue, May 19, 2015 at 10:00 AM, Dennis Kerrisk dennisk8...@gmail.com wrote: I am getting a kernel panic when I try to load firmware from an SD-card. I have tried several different images. Any suggestions what else I can try? Here is the console output: Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. [ 120.521745] INFO: task mmcqd/0:71 blocked for more than 60 seconds. [ 120.530919] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 120.541666] mmcqd/0 D c04d04a5 071 2 0x [ 120.550934] Kernel panic - not syncing: hung_task: blocked tasks [ 120.559813] [c00114f1] (unwind_backtrace+0x1/0x9c) from [c04cb2fd] (panic+0x59/0x15c) [ 120.571000] [c04cb2fd] (panic+0x59/0x15c) from [c0073955] (watchdog+0x19d/0x1c0) [ 120.581792] [c0073955] (watchdog+0x19d/0x1c0) from [c00454eb] (kthread+0x6b/0x78) [ 120.592698] [c00454eb] (kthread+0x6b/0x78) from [c000c8fd] (ret_from_fork+0x11/0x34) [ 120.603876] drm_kms_helper: panic occurred, switching back to text console This is an issue with 3.8.x.. Try any other manufacture's microSD card and a good known 5volt dc power supply. Later kernels (such as 3.14.x) handle this much better.. 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Removing BeagleBoneBlack USB driver from Windows 7
It's been a while since I've done this myself. But I believe the driver is not listed under the USB subsection. Try looking at the other subsections and see if you can spot it. On Mon, May 18, 2015 at 8:42 PM, TomTibbetts via BeagleBoard beagleboard@googlegroups.com wrote: https://lh3.googleusercontent.com/-CSSJRHzGyC8/VVqxE3aEVgI/ACU/EWeVd_r1d6U/s1600/USB%2BDrivers.JPG Thank you for your response. I looked in the device manager tree showing hidden devices and I'm not seeing anything that would give me a hint that it's the Beaglebone black driver. Thoughts on what it may be called? I'm thinking it may be a conflict because my backup drive is USB and the back up dashboard no longer sees the drive even though Windows does. Thanks On Thursday, May 14, 2015 at 10:01:32 PM UTC-5, William Hermans wrote: First, you may, or may not need to be running in safe mode. This part is unclear to me with Windows 7, but with WinXP this was all but a requirement. I always just remove drivers from Win7 in safe mode anyway . . . Second, you will likely have to do this with the board unplugged. Then once in device manager you would have to use view-show hidden devices. Then uninstall the device driver once found. Right click - uninstall etc. Typically, device driver installers have an uninstall executable as well. But unless things have changed recently, this driver does not have one. Lastly, I'm unsure how to approach the potential conflict problem. But I would probably start by making sure the backup drive was disconnected, and that you have drivers handy for it if needed. It's kind of hard for me to understand how that could happen, but in 3-4 years of using Windows 7 x64 . . . I've yet to run into a similar problem. Not saying it isn't possible though, just that I've not had the need to look into such a situation. On Thu, May 14, 2015 at 1:43 PM, TomTibbetts via BeagleBoard beagl...@googlegroups.com wrote: Hi. I'm trying to remove the BeagleBoneBlack USB driver from Windows 7 as I believe it is conflicting with a backup drive I have. I've searched for a way to do this but am not finding answers. Does anyone know how to do this? Thanks -- 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: Disabling HDMI makes mounted drives not authorized
*Dig your e-mail address by the way, I was/am a huge Elric fan, indeed all the Eternal Champion stuff.* Finally, someone who does not think the name comes from a french heavy metal band . . . On Tue, May 19, 2015 at 4:48 AM, Jack Fisher lotusf...@gmail.com wrote: That all makes perfect sense William. I have the debug cable already, I have learned the benefit of lowest level communication possible a long time ago. You don't always need it, but... Dig your e-mail address by the way, I was/am a huge Elric fan, indeed all the Eternal Champion stuff. Thanks again for your super help. Respectfully, Jack On Monday, May 18, 2015, William Hermans yyrk...@gmail.com wrote: As an aside / semi correction to what I wrote. I believe that u-boot has the USB serial gadget built in. Not sure how to go about using it, but I also believe it has to be loaded by u-boot first so will not give you as much output as a serial debug cable. If you're wondering if an FTDI cable is worth the $20 . . . it is. However I actually got a $2 prolific cable off ebay from China. That works fine. It's exactly the same as the new one ADA Fruit sells. You just need to make sure it's 3v3 TTL. If this is confusing to you, just stick with the recommended cables / adapters from the beagleboard.org ewiki pages. On Mon, May 18, 2015 at 4:50 PM, William Hermans yyrk...@gmail.com wrote: *just a newb trying to follow along and learn, byt he serial debug cable you mean the FTDI 3.3V serial-USB cable with the six pin header? It seems this one gives insight at a lower level than the straight mini-USB port...* Yes. The USB serial gadget driver is not funcitonal until the OS has control, and loads the driver. Where as the serial debug is functional far earlier. From memory, the serial debug serial interface is loaded late x-loader / MLO, but either way. For all intents and purposes. When u-boot is loaded into memory( and operational ), this is where you have communication potential with the system. This means you're able to view all uboot output, as well as when the kernel takes control of the board. You get all boot up kernel output as well. With the USB gadget, you will not get any ouput until late Linux boot, if any at all. The main purpose of the serial debug cable is exactly as the name implies. Debugging in the sense of something akin to code debugging using printf() in C. But it can also come in handy in a pinch for other uses as well. Such as gaining access to the board when there are no other means. On Mon, May 18, 2015 at 4:27 PM, Jack Fisher lotusf...@gmail.com wrote: William and Sam, Just a newb trying to follow along and learn, byt he serial debug cable you mean the FTDI 3.3V serial-USB cable with the six pin header? It seems this one gives insight at a lower level than the straight mini-USB port... Sorry for my gross ignorance, but I am working on that... Regards, Jack On Thursday, May 7, 2015 at 6:14:47 PM UTC-7, Sam wrote: Don't be sorry! I appreciate the help. It's a bit weird. Especially since no one else seems to be having the issue. I'll order myself a cable and continue the investigation. On Fri, 8 May 2015 9:59 am William Hermans yyr...@gmail.com wrote: Sorry I couldn't help more Sam . . . This problem seems kind of obscure to me. I do not remember reading about, or hearing of a similar issue. If you did happen to buy, or borrow a serial debug cable. You could run both configurations, logging the boot log output to file. Then run a diff on them to see if anything stands out. You can also try this with dmesg . . . and . . . just poking around myself . . . debian@beaglebone:~$* dmesg ~/file* debian@beaglebone:~$ *nano ./file* *[3.590829] bone-pinmux-helper P8_27_pinmux.18: Set initial pinmux mode to hdmi* *[3.598760] bone-pinmux-helper P8_28_pinmux.19: Set initial pinmux mode to hdmi* *[3.606640] bone-pinmux-helper P8_29_pinmux.20: Set initial pinmux mode to hdmi* *[3.614507] bone-pinmux-helper P8_30_pinmux.21: Set initial pinmux mode to hdmi* *[3.622286] bone-pinmux-helper P8_31_pinmux.22: Set initial pinmux mode to hdmi* *[3.630087] bone-pinmux-helper P8_32_pinmux.23: Set initial pinmux mode to hdmi* *[3.637903] bone-pinmux-helper P8_33_pinmux.24: Set initial pinmux mode to hdmi* *[3.645782] bone-pinmux-helper P8_34_pinmux.25: Set initial pinmux mode to hdmi* *[3.653558] bone-pinmux-helper P8_35_pinmux.26: Set initial pinmux mode to hdmi* *[3.661459] bone-pinmux-helper P8_36_pinmux.27: Set initial pinmux mode to hdmi* *[3.669453] bone-pinmux-helper P8_37_pinmux.28: Set initial pinmux mode to hdmi* *[3.677472] bone-pinmux-helper P8_38_pinmux.29: Set initial pinmux mode to hdmi* *[3.685519] bone-pinmux-helper P8_39_pinmux.30: Set initial pinmux mode to hdmi* *[3.693538] bone-pinmux-helper P8_40_pinmux.31: Set initial pinmux mode to hdmi* *[3.701634]
[beagleboard] Re: kernel panic loading firmware from SD-card
I have tried both Kingston and sandisk SD-cards. And i Am using a 1 amp 5 volt wall wart. Dennis -- 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] Future of BeagleBone (Black)?
This processor and board is no where near compatible with capes. Totally different connectors. Gerald On Tue, May 19, 2015 at 9:39 AM, Micka mickamus...@gmail.com wrote: Hi, where did you get those information? Where did Texas say that it is over for the am335x? Le mar. 19 mai 2015 16:30, Robert Nelson robertcnel...@gmail.com a écrit : On Tue, May 19, 2015 at 9:24 AM, Philip philip.balis...@gmail.com wrote: On Tuesday, May 19, 2015 at 10:14:20 AM UTC-4, Gerald wrote: If I knew that, I would have mentioned that. I would say maybe late September. We hope to have a few beta boards in about 6 weeks. Jason is handling who gets those boards. Right now, we are going back into layout to fix yet another TI feature. Will the cape interface stay the same? Nope, and don't mention stuff like that, we don't want to give Gerald a heart attack.. 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. 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. -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- 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: kernel panic loading firmware from SD-card
Yes it does. This is the one from computer-audio -- 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] will a buildroot build for BBB work out of the box?
OK so . ..
*reading uEnv.txt*
* 96 bytes read in 3 ms (31.3 KiB/s)*
* Loaded environment from uEnv.txt*
* Importing environment from mmc ...*
* Running uenvcmd ...*
* ## Error: loadimage not defined*
This is what a modern first stage uEnv.txt looks like ( Debian wheezy
7.8 )
http://pastebin.com/uheBAu99
Particularly:
loadximage=load mmc 0:1 ${loadaddr} /boot/vmlinuz-${uname_r}
Is you version of uboot patched with the beaglebone patchset ?
On Tue, May 19, 2015 at 2:03 AM, g...@novadsp.com wrote:
Thanks. With luck this is just for the record …
bootpart=0:1
bootdir=
bootfile=zImage
uenvcmd=run loadimage;run loadramdisk;run findfdt;run loadfdt;run ramboot
Lets see what your uEnv.txt looks like.
--
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: kernel panic loading firmware from SD-card
when replying to these mails please don't erase all the previous reply's makes it very hard to follow On 5/19/2015 9:39 AM, Dennis Kerrisk wrote: Yes it does. This is the one from computer-audio -- 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 mailto: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: kernel panic loading firmware from SD-card
*Yes it does. This is the one from computer-audio* This image you're trying to use from computer-audio, whoever that is. You should be contacting them, asking for help. Here, we know the official images, and try to support them the best we can. In my case, I'm not involved with building the actual official images for beagleboard.org. But I do build my own images, and have a couple years experience with my own, and the official images. In short, I know many things, and try to help. However, without being involved in the process of building these other images. There is no way we can tell what they've done, and by extension what is wrong with those images. It may be possible if you provided us with very detailed information we ight be able to help. But I've yet to see this . . . On Tue, May 19, 2015 at 10:02 AM, evilwulfie evilwul...@gmail.com wrote: when replying to these mails please don't erase all the previous reply's makes it very hard to follow On 5/19/2015 9:39 AM, Dennis Kerrisk wrote: Yes it does. This is the one from computer-audio -- 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] Removing BeagleBoneBlack USB driver from Windows 7
*Not sure what the original issue was. Obviously, not a USB driver issue. Thanks again for your help!* One thing Windows does terribly is how it handles driver enumeration. For example, if you use multiple USB-Serial interfaces. Windows creates a separate device instance for each ID. Regardless how many you actually have in use at one time, and regardless if it is the same exact device with a different ID or not . . . Most people using windows will probably notice this first, when creating multiple ethernet interfaces. Whether virtual or not, they never seem to go away . . .and after a while Windows just looses it's brain. What little it had to begin with. On Tue, May 19, 2015 at 8:55 AM, TomTibbetts via BeagleBoard beagleboard@googlegroups.com wrote: Thanks William! BTW, I was able to use my backup drive. Not sure what the original issue was. Obviously, not a USB driver issue. Thanks again for your help! On Tuesday, May 19, 2015 at 10:29:28 AM UTC-5, William Hermans wrote: It's been a while since I've done this myself. But I believe the driver is not listed under the USB subsection. Try looking at the other subsections and see if you can spot it. On Mon, May 18, 2015 at 8:42 PM, TomTibbetts via BeagleBoard beagl...@googlegroups.com wrote: https://lh3.googleusercontent.com/-CSSJRHzGyC8/VVqxE3aEVgI/ACU/EWeVd_r1d6U/s1600/USB%2BDrivers.JPG Thank you for your response. I looked in the device manager tree showing hidden devices and I'm not seeing anything that would give me a hint that it's the Beaglebone black driver. Thoughts on what it may be called? I'm thinking it may be a conflict because my backup drive is USB and the back up dashboard no longer sees the drive even though Windows does. Thanks On Thursday, May 14, 2015 at 10:01:32 PM UTC-5, William Hermans wrote: First, you may, or may not need to be running in safe mode. This part is unclear to me with Windows 7, but with WinXP this was all but a requirement. I always just remove drivers from Win7 in safe mode anyway . . . Second, you will likely have to do this with the board unplugged. Then once in device manager you would have to use view-show hidden devices. Then uninstall the device driver once found. Right click - uninstall etc. Typically, device driver installers have an uninstall executable as well. But unless things have changed recently, this driver does not have one. Lastly, I'm unsure how to approach the potential conflict problem. But I would probably start by making sure the backup drive was disconnected, and that you have drivers handy for it if needed. It's kind of hard for me to understand how that could happen, but in 3-4 years of using Windows 7 x64 . . . I've yet to run into a similar problem. Not saying it isn't possible though, just that I've not had the need to look into such a situation. On Thu, May 14, 2015 at 1:43 PM, TomTibbetts via BeagleBoard beagl...@googlegroups.com wrote: Hi. I'm trying to remove the BeagleBoneBlack USB driver from Windows 7 as I believe it is conflicting with a backup drive I have. I've searched for a way to do this but am not finding answers. Does anyone know how to do this? Thanks -- 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] TESTERS WANTED: beaglebone's cape manager
@William, Do you by chance have a board that needs the phy-id search patch? I just fixed the patch up, but don't actually have any boards that need it.. There should be a kernel *.deb here within the next hour.. http://builds.beagleboard.org/builders/build-kernel/builds/33 it would be nice to dmesg | grep mdio as my board is pretty blah... dmesg debian@beaglebone:~$ dmesg | grep mdio [4.609846] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [4.616265] davinci_mdio 4a101000.mdio: detected phy mask fffe [4.623106] davinci_mdio: dt: updated phy_id[0] from phy_mask[fffe] [4.630061] davinci_mdio: dt: updated phy_id[1] from phy_mask[fffe] 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: kernel panic loading firmware from SD-card
i had this issue and used 3.14.x with no issues since On 5/19/2015 8:32 AM, Dennis Kerrisk wrote: I have tried both Kingston and sandisk SD-cards. And i Am using a 1 amp 5 volt wall wart. Dennis -- 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 mailto: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] Removing BeagleBoneBlack USB driver from Windows 7
Thanks William! BTW, I was able to use my backup drive. Not sure what the original issue was. Obviously, not a USB driver issue. Thanks again for your help! On Tuesday, May 19, 2015 at 10:29:28 AM UTC-5, William Hermans wrote: It's been a while since I've done this myself. But I believe the driver is not listed under the USB subsection. Try looking at the other subsections and see if you can spot it. On Mon, May 18, 2015 at 8:42 PM, TomTibbetts via BeagleBoard beagl...@googlegroups.com javascript: wrote: https://lh3.googleusercontent.com/-CSSJRHzGyC8/VVqxE3aEVgI/ACU/EWeVd_r1d6U/s1600/USB%2BDrivers.JPG Thank you for your response. I looked in the device manager tree showing hidden devices and I'm not seeing anything that would give me a hint that it's the Beaglebone black driver. Thoughts on what it may be called? I'm thinking it may be a conflict because my backup drive is USB and the back up dashboard no longer sees the drive even though Windows does. Thanks On Thursday, May 14, 2015 at 10:01:32 PM UTC-5, William Hermans wrote: First, you may, or may not need to be running in safe mode. This part is unclear to me with Windows 7, but with WinXP this was all but a requirement. I always just remove drivers from Win7 in safe mode anyway . . . Second, you will likely have to do this with the board unplugged. Then once in device manager you would have to use view-show hidden devices. Then uninstall the device driver once found. Right click - uninstall etc. Typically, device driver installers have an uninstall executable as well. But unless things have changed recently, this driver does not have one. Lastly, I'm unsure how to approach the potential conflict problem. But I would probably start by making sure the backup drive was disconnected, and that you have drivers handy for it if needed. It's kind of hard for me to understand how that could happen, but in 3-4 years of using Windows 7 x64 . . . I've yet to run into a similar problem. Not saying it isn't possible though, just that I've not had the need to look into such a situation. On Thu, May 14, 2015 at 1:43 PM, TomTibbetts via BeagleBoard beagl...@googlegroups.com wrote: Hi. I'm trying to remove the BeagleBoneBlack USB driver from Windows 7 as I believe it is conflicting with a backup drive I have. I've searched for a way to do this but am not finding answers. Does anyone know how to do this? Thanks -- 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 javascript:. 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: kernel panic loading firmware from SD-card
This is on the console: Starting eMMC Flasher - Checking for Valid BBB EEPROM header Valid BBB EEPROM header found - copying: [/dev/mmcblk0] - [/dev/mmcblk1] lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1boot0 179:16 0 2M 1 disk mmcblk1boot1 179:24 0 2M 1 disk mmcblk0 179:00 14.6G 0 disk |-mmcblk0p1 179:1096M 0 part /boot/uboot `-mmcblk0p2 179:20 3.6G 0 part / mmcblk1 179:80 3.6G 0 disk |-mmcblk1p1 179:9096M 0 part `-mmcblk1p2 179:10 0 3.5G 0 part - df -h | grep rootfs: rootfs 3.5G 2.0G 1.4G 60% / - Erasing: /dev/mmcblk1 [ 120.520785] INFO: task mmcqd/0:71 blocked for more than 60 seconds. [ 120.527355] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 120.535527] mmcqd/0 D c04d04a5 071 2 0x [ 120.542195] Kernel panic - not syncing: hung_task: blocked tasks [ 120.548484] [c00114f1] (unwind_backtrace+0x1/0x9c) from [c04cb2fd] (panic+0x59/0x15c) [ 120.557012] [c04cb2fd] (panic+0x59/0x15c) from [c0073955] (watchdog+0x19d/0x1c0) [ 120.565103] [c0073955] (watchdog+0x19d/0x1c0) from [c00454eb] (kthread+0x6b/0x78) [ 120.573273] [c00454eb] (kthread+0x6b/0x78) from [c000c8fd] (ret_from_fork+0x11/0x34) [ 120.581714] drm_kms_helper: panic occurred, switching back to text console -- 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] Future of BeagleBone (Black)?
Small is a relative term. This thing has been one big headache after another. Gerlad On Tue, May 19, 2015 at 10:49 AM, William Hermans yyrk...@gmail.com wrote: 4 x 4.5 inches is still pretty darned small. Especially considering what is on the board. Looking forward to the board, even if not the price :/ On Tue, May 19, 2015 at 8:40 AM, Gerald Coley ger...@beagleboard.org wrote: Here are a couple of pictures. http://elinux.org/Beagleboard:BeagleBoard-X15 Gerald On Tue, May 19, 2015 at 10:36 AM, Gerald Coley ger...@beagleboard.org wrote: This processor and board is no where near compatible with capes. Totally different connectors. Gerald On Tue, May 19, 2015 at 9:39 AM, Micka mickamus...@gmail.com wrote: Hi, where did you get those information? Where did Texas say that it is over for the am335x? Le mar. 19 mai 2015 16:30, Robert Nelson robertcnel...@gmail.com a écrit : On Tue, May 19, 2015 at 9:24 AM, Philip philip.balis...@gmail.com wrote: On Tuesday, May 19, 2015 at 10:14:20 AM UTC-4, Gerald wrote: If I knew that, I would have mentioned that. I would say maybe late September. We hope to have a few beta boards in about 6 weeks. Jason is handling who gets those boards. Right now, we are going back into layout to fix yet another TI feature. Will the cape interface stay the same? Nope, and don't mention stuff like that, we don't want to give Gerald a heart attack.. 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. 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. -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- 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. -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- 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: kernel panic loading firmware from SD-card
oops https://rcn-ee.com/rootfs/bb.org/testing/2015-05-17/lxqt-4gb/bone-debian-8.0-lxqt-4gb-armhf-2015-05-17-4gb.img.xz On 5/19/2015 9:07 AM, Robert Nelson wrote: On Tue, May 19, 2015 at 11:03 AM, Dennis Kerrisk dennisk8...@gmail.com wrote: This is on the console: Starting eMMC Flasher - Checking for Valid BBB EEPROM header Valid BBB EEPROM header found - copying: [/dev/mmcblk0] - [/dev/mmcblk1] lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1boot0 179:16 0 2M 1 disk mmcblk1boot1 179:24 0 2M 1 disk mmcblk0 179:00 14.6G 0 disk |-mmcblk0p1 179:1096M 0 part /boot/uboot `-mmcblk0p2 179:20 3.6G 0 part / mmcblk1 179:80 3.6G 0 disk |-mmcblk1p1 179:9096M 0 part `-mmcblk1p2 179:10 0 3.5G 0 part - df -h | grep rootfs: rootfs 3.5G 2.0G 1.4G 60% / - Erasing: /dev/mmcblk1 [ 120.520785] INFO: task mmcqd/0:71 blocked for more than 60 seconds. [ 120.527355] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 120.535527] mmcqd/0 D c04d04a5 071 2 0x [ 120.542195] Kernel panic - not syncing: hung_task: blocked tasks [ 120.548484] [c00114f1] (unwind_backtrace+0x1/0x9c) from [c04cb2fd] (panic+0x59/0x15c) [ 120.557012] [c04cb2fd] (panic+0x59/0x15c) from [c0073955] (watchdog+0x19d/0x1c0) [ 120.565103] [c0073955] (watchdog+0x19d/0x1c0) from [c00454eb] (kthread+0x6b/0x78) [ 120.573273] [c00454eb] (kthread+0x6b/0x78) from [c000c8fd] (ret_from_fork+0x11/0x34) [ 120.581714] drm_kms_helper: panic occurred, switching back to text console Just use one of the jessie images here: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-05-17 which default to 3.14.x, then if you need 3.8.x just downgrade thru apt-get: sudo apt-get update sudo apt-get install linux-image-3.8.13-bone71 sudo reboot 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.
Re: [beagleboard] Re: kernel panic loading firmware from SD-card
@Robert Does your latest flasher image still use a two partition layout ? He's showing two partitions on both mmc devices . . . On Tue, May 19, 2015 at 9:29 AM, Dennis Kerrisk dennisk8...@gmail.com wrote: I'll try it next and see where is gets me. Thanks. Dennis -- 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] Future of BeagleBone (Black)?
On Tue, 19 May 2015, Gerald Coley wrote: BeagleBone Black at this point has no processor future due to TI's dead end road map. We are working on the BeagleBoard-X15 which is the next product to come out. Due to the form factor of the BBB, it cannot support the AM5728 processor. The BBB is just too small, but it does fit in the Altoids box. at what point will units be available? i wouldn't mind starting to move over my embedded linux and device driver courseware to the X15, at least in preparation for when the final units come out. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday
Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.
On Tue, May 19, 2015 at 3:56 PM, Robert Nelson robertcnel...@gmail.com wrote:
On Tue, May 19, 2015 at 3:48 PM, Fernando Derkoski bril...@gmail.com wrote:
Hi, first thank you for the response, here is the output where the network
did not work:
root@beaglebone:~# dmesg | grep mdio
[1.040419] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[1.040439] davinci_mdio 4a101000.mdio: detected phy mask fffb
[1.047217] libphy: 4a101000.mdio: probed
[1.047246] davinci_mdio 4a101000.mdio: phy[2]: device 4a101000.mdio:02,
driver SMSC LAN8710/LAN8720
Humm, that is odd, it corrected for [phy mask fffb] with
[4a101000.mdio:02]
But it should have been phy[4]... [4a101000.mdio:04]
The math conversion in the phy search patch is:
phy_mask = fffb
for (i = 0; i PHY_MAX_ADDR; i++) {
if ((phy_mask (1 i)) == 0) {
addr = (u32) i;
break;
}
}
This looks like a fun rabbit hole:
From: http://www.ti.com/lit/ug/spruh73l/spruh73l.pdf
Table 14-252. MDIOALIVE Register Field Descriptions
The alive bits are only meant to be used to give an indication of the
presence or not of a PHY with the corresponding address.
Whereas in the kernel:
/* get phy mask from the alive register */
phy_mask = __raw_readl(data-regs-alive);
if (phy_mask) {
/* restrict mdio bus to live phys only */
dev_info(data-dev, detected phy mask %x\n, ~phy_mask);
phy_mask = ~phy_mask;
} else {
/* desperately scan all phys */
dev_warn(data-dev, no live phy, scanning all\n);
phy_mask = 0;
}
data-bus-phy_mask = phy_mask;
We assume phy_mask to be 100% correct. Maybe we should just force
the dt value of phy_id always into phy_mask?
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.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.
Hi, first thank you for the response, *here is the output where the network did not work:* root@beaglebone:~# dmesg | grep mdio [1.040419] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [1.040439] davinci_mdio 4a101000.mdio: detected phy mask fffb [1.047217] libphy: 4a101000.mdio: probed [1.047246] davinci_mdio 4a101000.mdio: phy[2]: device 4a101000.mdio:02, driver SMSC LAN8710/LAN8720 [6.101577] libphy: PHY 4a101000.mdio:03 not found [6.106625] net eth0: phy 4a101000.mdio:03 not found on slave 1 root@beaglebone:~# sudo ifconfig -a eth0 Link encap:Ethernet HWaddr 78:a5:04:e6:6a:89 inet addr:192.168.0.21 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:40 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:227 errors:0 dropped:0 overruns:0 frame:0 TX packets:227 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:21648 (21.1 KiB) TX bytes:21648 (21.1 KiB) usb0 Link encap:Ethernet HWaddr 0e:d5:67:ae:38:c8 inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252 inet6 addr: fe80::cd5:67ff:feae:38c8/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:182 errors:0 dropped:0 overruns:0 frame:0 TX packets:25 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:24685 (24.1 KiB) TX bytes:6304 (6.1 KiB) root@beaglebone:~# ping 192.168.0.10 PING 192.168.0.10 (192.168.0.10) 56(84) bytes of data. From 192.168.0.21 icmp_seq=1 Destination Host Unreachable From 192.168.0.21 icmp_seq=2 Destination Host Unreachable From 192.168.0.21 icmp_seq=3 Destination Host Unreachable From 192.168.0.21 icmp_seq=4 Destination Host Unreachable ^C --- 192.168.0.10 ping statistics --- 6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 5001ms pipe 4 *And Here is the boot that the network works:* root@beaglebone:~# dmesg | grep mdio [1.040170] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [1.040187] davinci_mdio 4a101000.mdio: detected phy mask fffe [1.046996] libphy: 4a101000.mdio: probed [1.047025] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720 [5.425524] libphy: PHY 4a101000.mdio:01 not found [5.430563] net eth0: phy 4a101000.mdio:01 not found on slave 1 [8.501638] libphy: 4a101000.mdio:00 - Link is Up - 100/Full root@beaglebone:~# sudo ifconfig -a eth0 Link encap:Ethernet HWaddr 78:a5:04:e6:6a:89 inet addr:192.168.0.21 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::7aa5:4ff:fee6:6a89/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:137 errors:0 dropped:0 overruns:0 frame:0 TX packets:188 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:12183 (11.8 KiB) TX bytes:17169 (16.7 KiB) Interrupt:40 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:1 errors:0 dropped:0 overruns:0 frame:0 TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:79 (79.0 B) TX bytes:79 (79.0 B) usb0 Link encap:Ethernet HWaddr d6:2f:6f:eb:3c:2f inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252 inet6 addr: fe80::d42f:6fff:feeb:3c2f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:192 errors:0 dropped:0 overruns:0 frame:0 TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:25410 (24.8 KiB) TX bytes:9669 (9.4 KiB) root@beaglebone:~# ping 192.168.0.10 PING 192.168.0.10 (192.168.0.10) 56(84) bytes of data. 64 bytes from 192.168.0.10: icmp_req=1 ttl=128 time=1.50 ms 64 bytes from 192.168.0.10: icmp_req=2 ttl=128 time=1.44 ms 64 bytes from 192.168.0.10: icmp_req=3 ttl=128 time=1.49 ms ^C --- 192.168.0.10 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 1.449/1.480/1.502/0.038 ms On Tuesday, May 19, 2015 at 5:27:33 PM UTC-3, RobertCNelson wrote: On Tue, May 19, 2015 at 3:24 PM, Fernando Derkoski bri...@gmail.com javascript: wrote: Hello, This problem happens to me as well, I have 3 beaglebones black Rev C, with the latest kernel,
Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.
As an aside, is this in fact the problem, it would probably be listed as
nameserver 192.168.1.1 Which seems to be the default value as shipped
On Tue, May 19, 2015 at 2:44 PM, William Hermans yyrk...@gmail.com wrote:
But the network interface seems to be working fine.
What nameserver is listed in /etc/resolv.conf under nameserver ? If it
is different from your network, then you should probably change it to be
accurate.
Then try to ping local IPs again . . .
On Tue, May 19, 2015 at 1:56 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Tue, May 19, 2015 at 3:48 PM, Fernando Derkoski bril...@gmail.com
wrote:
Hi, first thank you for the response, here is the output where the
network
did not work:
root@beaglebone:~# dmesg | grep mdio
[1.040419] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[1.040439] davinci_mdio 4a101000.mdio: detected phy mask fffb
[1.047217] libphy: 4a101000.mdio: probed
[1.047246] davinci_mdio 4a101000.mdio: phy[2]: device
4a101000.mdio:02,
driver SMSC LAN8710/LAN8720
Humm, that is odd, it corrected for [phy mask fffb] with
[4a101000.mdio:02]
But it should have been phy[4]... [4a101000.mdio:04]
The math conversion in the phy search patch is:
phy_mask = fffb
for (i = 0; i PHY_MAX_ADDR; i++) {
if ((phy_mask (1 i)) == 0) {
addr = (u32) i;
break;
}
}
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.
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] Beaglebone Black Ethernet Phy Not Detected on Boot.
name servers have nothing to do with anything when pinging with IP numbers.
On 5/19/2015 2:45 PM, William Hermans wrote:
As an aside, is this in fact the problem, it would probably be listed
as nameserver 192.168.1.1 Which seems to be the default value as
shipped
On Tue, May 19, 2015 at 2:44 PM, William Hermans yyrk...@gmail.com
mailto:yyrk...@gmail.com wrote:
But the network interface seems to be working fine.
What nameserver is listed in /etc/resolv.conf under nameserver ?
If it is different from your network, then you should probably
change it to be accurate.
Then try to ping local IPs again . . .
On Tue, May 19, 2015 at 1:56 PM, Robert Nelson
robertcnel...@gmail.com mailto:robertcnel...@gmail.com wrote:
On Tue, May 19, 2015 at 3:48 PM, Fernando Derkoski
bril...@gmail.com mailto:bril...@gmail.com wrote:
Hi, first thank you for the response, here is the output
where the network
did not work:
root@beaglebone:~# dmesg | grep mdio
[1.040419] davinci_mdio 4a101000.mdio: davinci mdio
revision 1.6
[1.040439] davinci_mdio 4a101000.mdio: detected phy mask
fffb
[1.047217] libphy: 4a101000.mdio: probed
[1.047246] davinci_mdio 4a101000.mdio: phy[2]: device
4a101000.mdio:02,
driver SMSC LAN8710/LAN8720
Humm, that is odd, it corrected for [phy mask fffb] with
[4a101000.mdio:02]
But it should have been phy[4]... [4a101000.mdio:04]
The math conversion in the phy search patch is:
phy_mask = fffb
for (i = 0; i PHY_MAX_ADDR; i++) {
if ((phy_mask (1 i)) == 0) {
addr = (u32) i;
break;
}
}
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
mailto:beagleboard%2bunsubscr...@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
mailto: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] Beaglebone Black Ethernet Phy Not Detected on Boot.
On Tue, May 19, 2015 at 5:00 PM, Robert Nelson robertcnel...@gmail.com wrote:
On Tue, May 19, 2015 at 4:57 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Tue, May 19, 2015 at 3:56 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Tue, May 19, 2015 at 3:48 PM, Fernando Derkoski bril...@gmail.com
wrote:
Hi, first thank you for the response, here is the output where the network
did not work:
root@beaglebone:~# dmesg | grep mdio
[1.040419] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[1.040439] davinci_mdio 4a101000.mdio: detected phy mask fffb
[1.047217] libphy: 4a101000.mdio: probed
[1.047246] davinci_mdio 4a101000.mdio: phy[2]: device 4a101000.mdio:02,
driver SMSC LAN8710/LAN8720
Humm, that is odd, it corrected for [phy mask fffb] with
[4a101000.mdio:02]
But it should have been phy[4]... [4a101000.mdio:04]
The math conversion in the phy search patch is:
phy_mask = fffb
for (i = 0; i PHY_MAX_ADDR; i++) {
if ((phy_mask (1 i)) == 0) {
addr = (u32) i;
break;
}
}
This looks like a fun rabbit hole:
From: http://www.ti.com/lit/ug/spruh73l/spruh73l.pdf
Table 14-252. MDIOALIVE Register Field Descriptions
The alive bits are only meant to be used to give an indication of the
presence or not of a PHY with the corresponding address.
Whereas in the kernel:
/* get phy mask from the alive register */
phy_mask = __raw_readl(data-regs-alive);
if (phy_mask) {
/* restrict mdio bus to live phys only */
dev_info(data-dev, detected phy mask %x\n, ~phy_mask);
phy_mask = ~phy_mask;
} else {
/* desperately scan all phys */
dev_warn(data-dev, no live phy, scanning all\n);
phy_mask = 0;
}
data-bus-phy_mask = phy_mask;
We assume phy_mask to be 100% correct. Maybe we should just force
the dt value of phy_id always into phy_mask?
nm... total 5pm brain fart..
I really need to find a board that 'never' boots with 0xfffe..
I'm thinking yanking r117 and shorting RXD3/PHYAD2 - vdd_3v3b
r116 yeap.. time to go home. ;)
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.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.
On Tue, May 19, 2015 at 3:24 PM, Fernando Derkoski bril...@gmail.com wrote: Hello, This problem happens to me as well, I have 3 beaglebones black Rev C, with the latest kernel, 3.8.13-bone70. Anyone knows how to resolve this problem? unlikely... show us the output off: dmesg | grep mdio sudo ifconfig -a 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.
Hello, This problem happens to me as well, I have 3 beaglebones black Rev C, with the latest kernel, 3.8.13-bone70. Anyone knows how to resolve 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: kernel panic loading firmware from SD-card
It is not an image issue. It load fine on another board. I guess this board is broken -- 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] Beaglebone Black Ethernet Phy Not Detected on Boot.
On Tue, May 19, 2015 at 4:57 PM, Robert Nelson robertcnel...@gmail.com wrote:
On Tue, May 19, 2015 at 3:56 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Tue, May 19, 2015 at 3:48 PM, Fernando Derkoski bril...@gmail.com wrote:
Hi, first thank you for the response, here is the output where the network
did not work:
root@beaglebone:~# dmesg | grep mdio
[1.040419] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[1.040439] davinci_mdio 4a101000.mdio: detected phy mask fffb
[1.047217] libphy: 4a101000.mdio: probed
[1.047246] davinci_mdio 4a101000.mdio: phy[2]: device 4a101000.mdio:02,
driver SMSC LAN8710/LAN8720
Humm, that is odd, it corrected for [phy mask fffb] with
[4a101000.mdio:02]
But it should have been phy[4]... [4a101000.mdio:04]
The math conversion in the phy search patch is:
phy_mask = fffb
for (i = 0; i PHY_MAX_ADDR; i++) {
if ((phy_mask (1 i)) == 0) {
addr = (u32) i;
break;
}
}
This looks like a fun rabbit hole:
From: http://www.ti.com/lit/ug/spruh73l/spruh73l.pdf
Table 14-252. MDIOALIVE Register Field Descriptions
The alive bits are only meant to be used to give an indication of the
presence or not of a PHY with the corresponding address.
Whereas in the kernel:
/* get phy mask from the alive register */
phy_mask = __raw_readl(data-regs-alive);
if (phy_mask) {
/* restrict mdio bus to live phys only */
dev_info(data-dev, detected phy mask %x\n, ~phy_mask);
phy_mask = ~phy_mask;
} else {
/* desperately scan all phys */
dev_warn(data-dev, no live phy, scanning all\n);
phy_mask = 0;
}
data-bus-phy_mask = phy_mask;
We assume phy_mask to be 100% correct. Maybe we should just force
the dt value of phy_id always into phy_mask?
nm... total 5pm brain fart..
I really need to find a board that 'never' boots with 0xfffe..
I'm thinking yanking r117 and shorting RXD3/PHYAD2 - vdd_3v3b
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.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Bone VDD_3V3EXP Disable Issues
Matthijs, Did you try any change in the EN pin of U4 (enable signal of 3V3B)? I'm about to try SYS_RESETn (PMIC_PGOOD after U16), but I'm concerned about the 20ms turn on delay (plus 10ms due to the RC). The other option is to go back to use 3V3AUX, and add a 1k load resistor to reduce the discharge time. Thanks, Max On Friday, May 1, 2015 at 4:35:04 PM UTC-7, Matthijs van Duin wrote: On Friday, 1 May 2015 19:01:06 UTC+2, Matthijs van Duin wrote: I've captured the shutdown sequence on DC versus BAT power in more detail Just a quick clarification to avoid confusion: Unlike the scope images in my original post, these were captured with BATMON connected to BAT even in the DC-powered case. As I mentioned in my original post this somewhat changes the behaviour of the TPS65217, and in particular prevents BAT from ever dropping below 0V, which would be out of view in these images. The vertical range of these images is 0V...4V, grid lines are spaced 0.5V and 5ms, minor ticks 0.125V and 1ms. The images in my original post have vertical range -1V...6V, grid lines spaced 1V and 20ms, minor ticks 0.25V and 4ms. They were taken with serial cable attached. Matthijs -- 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] Beaglebone Black Ethernet Phy Not Detected on Boot.
On Tue, May 19, 2015 at 3:48 PM, Fernando Derkoski bril...@gmail.com wrote:
Hi, first thank you for the response, here is the output where the network
did not work:
root@beaglebone:~# dmesg | grep mdio
[1.040419] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[1.040439] davinci_mdio 4a101000.mdio: detected phy mask fffb
[1.047217] libphy: 4a101000.mdio: probed
[1.047246] davinci_mdio 4a101000.mdio: phy[2]: device 4a101000.mdio:02,
driver SMSC LAN8710/LAN8720
Humm, that is odd, it corrected for [phy mask fffb] with [4a101000.mdio:02]
But it should have been phy[4]... [4a101000.mdio:04]
The math conversion in the phy search patch is:
phy_mask = fffb
for (i = 0; i PHY_MAX_ADDR; i++) {
if ((phy_mask (1 i)) == 0) {
addr = (u32) i;
break;
}
}
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.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.
*r116 yeap.. time to go home. ;)*
Same here, and yeah wulf is right. My problem is: I'm already home. Maybe I
need a brewski . . .
On Tue, May 19, 2015 at 3:01 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Tue, May 19, 2015 at 5:00 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Tue, May 19, 2015 at 4:57 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Tue, May 19, 2015 at 3:56 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Tue, May 19, 2015 at 3:48 PM, Fernando Derkoski bril...@gmail.com
wrote:
Hi, first thank you for the response, here is the output where the
network
did not work:
root@beaglebone:~# dmesg | grep mdio
[1.040419] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[1.040439] davinci_mdio 4a101000.mdio: detected phy mask fffb
[1.047217] libphy: 4a101000.mdio: probed
[1.047246] davinci_mdio 4a101000.mdio: phy[2]: device
4a101000.mdio:02,
driver SMSC LAN8710/LAN8720
Humm, that is odd, it corrected for [phy mask fffb] with
[4a101000.mdio:02]
But it should have been phy[4]... [4a101000.mdio:04]
The math conversion in the phy search patch is:
phy_mask = fffb
for (i = 0; i PHY_MAX_ADDR; i++) {
if ((phy_mask (1 i)) == 0) {
addr = (u32) i;
break;
}
}
This looks like a fun rabbit hole:
From: http://www.ti.com/lit/ug/spruh73l/spruh73l.pdf
Table 14-252. MDIOALIVE Register Field Descriptions
The alive bits are only meant to be used to give an indication of the
presence or not of a PHY with the corresponding address.
Whereas in the kernel:
/* get phy mask from the alive register */
phy_mask = __raw_readl(data-regs-alive);
if (phy_mask) {
/* restrict mdio bus to live phys only */
dev_info(data-dev, detected phy mask %x\n, ~phy_mask);
phy_mask = ~phy_mask;
} else {
/* desperately scan all phys */
dev_warn(data-dev, no live phy, scanning all\n);
phy_mask = 0;
}
data-bus-phy_mask = phy_mask;
We assume phy_mask to be 100% correct. Maybe we should just force
the dt value of phy_id always into phy_mask?
nm... total 5pm brain fart..
I really need to find a board that 'never' boots with 0xfffe..
I'm thinking yanking r117 and shorting RXD3/PHYAD2 - vdd_3v3b
r116 yeap.. time to go home. ;)
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.
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: kernel panic loading firmware from SD-card
I have tried the latest debian and a special audio image from computer audio. I load the images onto an SD-card. I insert my sd-card into my neagle board. I then hold down S2 while powering up my board. It starts to boot and and then it panics. -- 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: kernel panic loading firmware from SD-card
On Tue, May 19, 2015 at 11:03 AM, Dennis Kerrisk dennisk8...@gmail.com wrote: This is on the console: Starting eMMC Flasher - Checking for Valid BBB EEPROM header Valid BBB EEPROM header found - copying: [/dev/mmcblk0] - [/dev/mmcblk1] lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1boot0 179:16 0 2M 1 disk mmcblk1boot1 179:24 0 2M 1 disk mmcblk0 179:00 14.6G 0 disk |-mmcblk0p1 179:1096M 0 part /boot/uboot `-mmcblk0p2 179:20 3.6G 0 part / mmcblk1 179:80 3.6G 0 disk |-mmcblk1p1 179:9096M 0 part `-mmcblk1p2 179:10 0 3.5G 0 part - df -h | grep rootfs: rootfs 3.5G 2.0G 1.4G 60% / - Erasing: /dev/mmcblk1 [ 120.520785] INFO: task mmcqd/0:71 blocked for more than 60 seconds. [ 120.527355] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 120.535527] mmcqd/0 D c04d04a5 071 2 0x [ 120.542195] Kernel panic - not syncing: hung_task: blocked tasks [ 120.548484] [c00114f1] (unwind_backtrace+0x1/0x9c) from [c04cb2fd] (panic+0x59/0x15c) [ 120.557012] [c04cb2fd] (panic+0x59/0x15c) from [c0073955] (watchdog+0x19d/0x1c0) [ 120.565103] [c0073955] (watchdog+0x19d/0x1c0) from [c00454eb] (kthread+0x6b/0x78) [ 120.573273] [c00454eb] (kthread+0x6b/0x78) from [c000c8fd] (ret_from_fork+0x11/0x34) [ 120.581714] drm_kms_helper: panic occurred, switching back to text console Just use one of the jessie images here: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-05-17 which default to 3.14.x, then if you need 3.8.x just downgrade thru apt-get: sudo apt-get update sudo apt-get install linux-image-3.8.13-bone71 sudo reboot 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Future of BeagleBone (Black)?
TI and their features eh lol On 5/19/2015 8:59 AM, Gerald Coley wrote: Small is a relative term. This thing has been one big headache after another. Gerlad On Tue, May 19, 2015 at 10:49 AM, William Hermans yyrk...@gmail.com mailto:yyrk...@gmail.com wrote: 4 x 4.5 inches is still pretty darned small. Especially considering what is on the board. Looking forward to the board, even if not the price :/ On Tue, May 19, 2015 at 8:40 AM, Gerald Coley ger...@beagleboard.org mailto:ger...@beagleboard.org wrote: Here are a couple of pictures. http://elinux.org/Beagleboard:BeagleBoard-X15 Gerald On Tue, May 19, 2015 at 10:36 AM, Gerald Coley ger...@beagleboard.org mailto:ger...@beagleboard.org wrote: This processor and board is no where near compatible with capes. Totally different connectors. Gerald On Tue, May 19, 2015 at 9:39 AM, Micka mickamus...@gmail.com mailto:mickamus...@gmail.com wrote: Hi, where did you get those information? Where did Texas say that it is over for the am335x? Le mar. 19 mai 2015 16:30, Robert Nelson robertcnel...@gmail.com mailto:robertcnel...@gmail.com a écrit : On Tue, May 19, 2015 at 9:24 AM, Philip philip.balis...@gmail.com mailto:philip.balis...@gmail.com wrote: On Tuesday, May 19, 2015 at 10:14:20 AM UTC-4, Gerald wrote: If I knew that, I would have mentioned that. I would say maybe late September. We hope to have a few beta boards in about 6 weeks. Jason is handling who gets those boards. Right now, we are going back into layout to fix yet another TI feature. Will the cape interface stay the same? Nope, and don't mention stuff like that, we don't want to give Gerald a heart attack.. 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 mailto:beagleboard%2bunsubscr...@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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Gerald ger...@beagleboard.org mailto:ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- Gerald ger...@beagleboard.org mailto:ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- 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 mailto: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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Gerald ger...@beagleboard.org mailto:ger...@beagleboard.org
[beagleboard] Re: kernel panic loading firmware from SD-card
That is one of the images I have tried to load. It panics when I try to load any image. -- 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] Future of BeagleBone (Black)?
Here are a couple of pictures. http://elinux.org/Beagleboard:BeagleBoard-X15 Gerald On Tue, May 19, 2015 at 10:36 AM, Gerald Coley ger...@beagleboard.org wrote: This processor and board is no where near compatible with capes. Totally different connectors. Gerald On Tue, May 19, 2015 at 9:39 AM, Micka mickamus...@gmail.com wrote: Hi, where did you get those information? Where did Texas say that it is over for the am335x? Le mar. 19 mai 2015 16:30, Robert Nelson robertcnel...@gmail.com a écrit : On Tue, May 19, 2015 at 9:24 AM, Philip philip.balis...@gmail.com wrote: On Tuesday, May 19, 2015 at 10:14:20 AM UTC-4, Gerald wrote: If I knew that, I would have mentioned that. I would say maybe late September. We hope to have a few beta boards in about 6 weeks. Jason is handling who gets those boards. Right now, we are going back into layout to fix yet another TI feature. Will the cape interface stay the same? Nope, and don't mention stuff like that, we don't want to give Gerald a heart attack.. 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. 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. -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- 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: kernel panic loading firmware from SD-card
The problem I can't load any code at all onto it. So how di I get 3.14.x onto it -- 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: kernel panic loading firmware from SD-card
@Dennis I think we should start over. Tell us the exact details, starting from where you began. Which image, how you got it to which flash media, board version. etc. On Tue, May 19, 2015 at 8:40 AM, Dennis Kerrisk dennisk8...@gmail.com wrote: The problem I can't load any code at all onto it. So how di I get 3.14.x onto it -- 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: kernel panic loading firmware from SD-card
I'll try it next and see where is gets me. Thanks. Dennis -- 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: kernel panic loading firmware from SD-card
@Dennis Have you tried just using a standalone image on an sdcard to see if that works. Based on your console output above you're trying to flash the eMMC. Your board also seems to be a RevC On Tue, May 19, 2015 at 9:19 AM, evilwulfie evilwul...@gmail.com wrote: oops https://rcn-ee.com/rootfs/bb.org/testing/2015-05-17/lxqt-4gb/bone-debian-8.0-lxqt-4gb-armhf-2015-05-17-4gb.img.xz On 5/19/2015 9:07 AM, Robert Nelson wrote: On Tue, May 19, 2015 at 11:03 AM, Dennis Kerrisk dennisk8...@gmail.com wrote: This is on the console: Starting eMMC Flasher - Checking for Valid BBB EEPROM header Valid BBB EEPROM header found - copying: [/dev/mmcblk0] - [/dev/mmcblk1] lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1boot0 179:16 0 2M 1 disk mmcblk1boot1 179:24 0 2M 1 disk mmcblk0 179:00 14.6G 0 disk |-mmcblk0p1 179:1096M 0 part /boot/uboot `-mmcblk0p2 179:20 3.6G 0 part / mmcblk1 179:80 3.6G 0 disk |-mmcblk1p1 179:9096M 0 part `-mmcblk1p2 179:10 0 3.5G 0 part - df -h | grep rootfs: rootfs 3.5G 2.0G 1.4G 60% / - Erasing: /dev/mmcblk1 [ 120.520785] INFO: task mmcqd/0:71 blocked for more than 60 seconds. [ 120.527355] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 120.535527] mmcqd/0 D c04d04a5 071 2 0x [ 120.542195] Kernel panic - not syncing: hung_task: blocked tasks [ 120.548484] [c00114f1] (unwind_backtrace+0x1/0x9c) from [c04cb2fd] (panic+0x59/0x15c) [ 120.557012] [c04cb2fd] (panic+0x59/0x15c) from [c0073955] (watchdog+0x19d/0x1c0) [ 120.565103] [c0073955] (watchdog+0x19d/0x1c0) from [c00454eb] (kthread+0x6b/0x78) [ 120.573273] [c00454eb] (kthread+0x6b/0x78) from [c000c8fd] (ret_from_fork+0x11/0x34) [ 120.581714] drm_kms_helper: panic occurred, switching back to text console Just use one of the jessie images here: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-05-17 which default to 3.14.x, then if you need 3.8.x just downgrade thru apt-get: sudo apt-get update sudo apt-get install linux-image-3.8.13-bone71 sudo reboot 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.
Re: [beagleboard] Future of BeagleBone (Black)?
4 x 4.5 inches is still pretty darned small. Especially considering what is on the board. Looking forward to the board, even if not the price :/ On Tue, May 19, 2015 at 8:40 AM, Gerald Coley ger...@beagleboard.org wrote: Here are a couple of pictures. http://elinux.org/Beagleboard:BeagleBoard-X15 Gerald On Tue, May 19, 2015 at 10:36 AM, Gerald Coley ger...@beagleboard.org wrote: This processor and board is no where near compatible with capes. Totally different connectors. Gerald On Tue, May 19, 2015 at 9:39 AM, Micka mickamus...@gmail.com wrote: Hi, where did you get those information? Where did Texas say that it is over for the am335x? Le mar. 19 mai 2015 16:30, Robert Nelson robertcnel...@gmail.com a écrit : On Tue, May 19, 2015 at 9:24 AM, Philip philip.balis...@gmail.com wrote: On Tuesday, May 19, 2015 at 10:14:20 AM UTC-4, Gerald wrote: If I knew that, I would have mentioned that. I would say maybe late September. We hope to have a few beta boards in about 6 weeks. Jason is handling who gets those boards. Right now, we are going back into layout to fix yet another TI feature. Will the cape interface stay the same? Nope, and don't mention stuff like that, we don't want to give Gerald a heart attack.. 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. 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. -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- 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: kernel panic loading firmware from SD-card
from that you are trying to flash the Emmc not boot off of the SD card so you are using the flasher image if you desire to just boot off the SD card try a non flasher image https://rcn-ee.com/rootfs/bb.org/testing/2015-05-17/lxqt-4gb/bb-debian-8.0-lxqt-4gb-armhf-2015-05-17-4gb.img.xz load to SD card and it should boot On 5/19/2015 9:03 AM, Dennis Kerrisk wrote: This is on the console: Starting eMMC Flasher - Checking for Valid BBB EEPROM header Valid BBB EEPROM header found - copying: [/dev/mmcblk0] - [/dev/mmcblk1] lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1boot0 179:16 0 2M 1 disk mmcblk1boot1 179:24 0 2M 1 disk mmcblk0 179:00 14.6G 0 disk |-mmcblk0p1 179:1096M 0 part /boot/uboot `-mmcblk0p2 179:20 3.6G 0 part / mmcblk1 179:80 3.6G 0 disk |-mmcblk1p1 179:9096M 0 part `-mmcblk1p2 179:10 0 3.5G 0 part - df -h | grep rootfs: rootfs 3.5G 2.0G 1.4G 60% / - Erasing: /dev/mmcblk1 [ 120.520785] INFO: task mmcqd/0:71 blocked for more than 60 seconds. [ 120.527355] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 120.535527] mmcqd/0 D c04d04a5 071 2 0x [ 120.542195] Kernel panic - not syncing: hung_task: blocked tasks [ 120.548484] [c00114f1] (unwind_backtrace+0x1/0x9c) from [c04cb2fd] (panic+0x59/0x15c) [ 120.557012] [c04cb2fd] (panic+0x59/0x15c) from [c0073955] (watchdog+0x19d/0x1c0) [ 120.565103] [c0073955] (watchdog+0x19d/0x1c0) from [c00454eb] (kthread+0x6b/0x78) [ 120.573273] [c00454eb] (kthread+0x6b/0x78) from [c000c8fd] (ret_from_fork+0x11/0x34) [ 120.581714] drm_kms_helper: panic occurred, switching back to text console -- 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 mailto: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: Add a new cape for BeagleBone
Yes, I know of course, I'm working in consulting for the biggest Telco in France (who have already bought some IOTCape). We have the same requirements for Europe and all the countries in the world have the same. But, my cape doesn't provide natively a modem. It provides a MiniPcie connector. I suggest the use of some modems that work and have been tested on it. All of these modems have been certified for the US (the manufacturers are Sierra wireless, Huawei and Telit). Regards, Pascal On Tuesday, May 19, 2015 at 4:21:49 PM UTC+2, Wulf Man wrote: when ever you connect a device to the cellular network in the USA they the network operators require you to get your device certified. http://www.ecnmag.com/articles/2012/07/cellular-carrier-certification-requirements On 5/18/2015 2:21 PM, pascal...@gmail.com javascript: wrote: I apologize for my poor english. I admit that may sound strange. But, I would say that the capes are used to make prototypes and not a final product (consumer or industrial market). I will modify this in the manual. On Sunday, May 17, 2015 at 9:41:22 PM UTC+2, William Hermans wrote: Well somewhere in user manual it states something like lab / experimentation use only . . . Which i thought was odd in of its self anyhow. I wont be buying one. On Sun, May 17, 2015 at 12:06 PM, evilwulfie evilw...@gmail.com wrote: Just a note for you. Selling this in the USA requires you to get FCC approval. It also requires you to get approval from the cell phone providers. Its NOT cheap for approval. On 5/17/2015 11:21 AM, Gerald Coley wrote: Yes, you did. But I do not maintain that page. The people that do are listed there. I do not handle that page. I do not own that page. I cannot change that page to post your link. Gerald On Sat, May 16, 2015 at 4:01 AM, Pascal FIFRE pascal...@iotys.com wrote: Hi, Yesterday, I’ve told you that I‘ve created a wiki page for my new cape IOTCape. I’ve changed this wiki page to http://elinux.org/IOTYS:IOTCape. Thanks a lot for your help. Best Regards, Pascal *Pascal FIFRE* IOTYS 43, Garenne Poull ar Rouz 22300 LANNION www.iotys.com *De :* Pascal FIFRE [mailto:pascal...@iotys.com] *Envoyé :* vendredi 15 mai 2015 18:40 *À :* 'beagl...@googlegroups.com' *Objet :* Add a new cape for BeagleBone Hi, I want to add the my new cape (IOTCape) for BeagleBone to BeagleBone capes site. I’ve created a wiki page http://elinux.org/User:IOTCape based on the http://elinux.org/CircuitCo:BeagleBone_LCD3 wiki page. Attached to this mail you will find : · A user manual of this new cape. · DTS file for cape Thanks a lot for your help. Best Regards, *Pascal FIFRE* IOTYS 43, Garenne Poull ar Rouz 22300 LANNION www.iotys.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...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Gerald ger...@beagleboard.org http://beagleboard.org/ http://circuitco.com/support/ -- 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...@googlegroups.com javascript:. 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.
