[beagleboard] Pin mux during bootloader and reset press

Hi, I've noticed that when you press the reset button on the BBB pin P9_17 and P9_18 are raised up and then they go down when you release the reset button. Same for P9_15 and P9_12 but those two stay turned on until kernel launch the device tree. For P9_12 and P9_15 i've figured out that this is

[beagleboard] Beaglebone unable to print complete page

Hi, I am using Beagelebone Black RevC with Debian8 and cups 1.7.5 for printing to HP Deskjet 1112 printer. I am able to print correctly on PC but when I try to print on BBB, the last 10% (almost) is not getting printed. I have used 'apt-get install' to install cups and the necessary packages.

[beagleboard] Beaglebone Black Kernel 4.1 PWM and OCP?

Hey guys, I'm working on a project where as I was using the ocp.X/bone_pwm_P9_11 and such in kernel 3.8. I just recently updated my Beaglebone black to kernel 4.1 and couldn't get PWM to work... I was trying to use dtc, rebuild the device tree overlay. I pulled the old am33xx_pwm from https://

[beagleboard] Re: CADSTAR Schematic and PCB Layout for BeagleboardXM A2 now available

I'd like a copy too. Do you have also have files for Beaglebone Black? Am Sonntag, 10. Juli 2011 21:38:25 UTC+2 schrieb cdbintexas: > > ANNOUNCEMENT:For those of you who want to do hardware modification, I > have converted the original design data into CADSTAR format. This > universally recogn

Re: [beagleboard] Much hardware failures with Element14-boards

...and an other one from same batch: - Ethernet not working Seems for me the small price difference between Circuitco and Element14 boards is finally a very expensive one... 2015-08-06 7:45 GMT+02:00 Karl Karpfen : > Hi, > > I currently have a set of 20 BBB's that come from Element14 and show

Re: [beagleboard] element14 vs Circuitco Rev C

Hello! the element14 version has my own image (what I optimize for me) the Circuitco version has the original image But I want to use my image also on the Circuitco version. I always thought that BBB RevC = BBB RevC Thank you! In the meantime I flash the eMMC with the original Debian Image: Log

Re: [beagleboard] element14 vs Circuitco Rev C

On Wed, Sep 9, 2015 at 6:25 AM, Fohnbit wrote: > Hello! > > the element14 version has my own image (what I optimize for me) > the Circuitco version has the original image > > But I want to use my image also on the Circuitco version. > I always thought that BBB RevC = BBB RevC They are.. > > Than

Re: [beagleboard] element14 vs Circuitco Rev C

> On Sep 9, 2015, at 8:58 AM, Robert Nelson wrote: > >> On Wed, Sep 9, 2015 at 6:25 AM, Fohnbit wrote: >> Hello! >> >> the element14 version has my own image (what I optimize for me) >> the Circuitco version has the original image >> >> But I want to use my image also on the Circuitco vers

Re: [beagleboard] element14 vs Circuitco Rev C

Part number? Gerald On Wed, Sep 9, 2015 at 8:39 AM, Jason Kridner wrote: > > > > > > On Sep 9, 2015, at 8:58 AM, Robert Nelson > wrote: > > > >> On Wed, Sep 9, 2015 at 6:25 AM, Fohnbit wrote: > >> Hello! > >> > >> the element14 version has my own image (what I optimize for me) > >> the Circu

Re: [beagleboard] element14 vs Circuitco Rev C

On Wed, Sep 9, 2015 at 9:03 AM, Gerald Coley wrote: > Part number? #Micron 3744MB (bbb): 3925868544 bytes -> 3925.86 Megabyte #Kingston 3688MB (bbb): 3867148288 bytes -> 3867.15 Megabyte Only an issue for "dd" flashing.. ;) Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options,

[beagleboard] Re: Beagle Board REV.C

Dear RBH, could you send me this files in Altium format? Thank you. Aleix. aleix.lopez.an...@gmail.com El dilluns, 25 juliol de 2011 8:11:35 UTC+2, RBH va escriure: > > Dear All, > > Dose anyone need Altium Designer Format of Beagle Board REV.C? > > Beagle board source files are designe

Re: [beagleboard] element14 vs Circuitco Rev C

Sounds like we need to move to 8G. Gerald On Wed, Sep 9, 2015 at 9:06 AM, Robert Nelson wrote: > On Wed, Sep 9, 2015 at 9:03 AM, Gerald Coley > wrote: > > Part number? > > #Micron 3744MB (bbb): 3925868544 bytes -> 3925.86 Megabyte > #Kingston 3688MB (bbb): 3867148288 bytes -> 3867.15 Megabyte

Re: [beagleboard] Re: Beagle Board REV.C

http://www.elinux.org/Beagleboard:BeagleBoneBlack#LATEST_PRODUCTION_FILES_.28C.29 Gerald On Wed, Sep 9, 2015 at 9:56 AM, wrote: > Dear RBH, > > could you send me this files in Altium format? > > Thank you. > > Aleix. > aleix.lopez.an...@gmail.com > > > > El dilluns, 25 juliol de 2011 8:11:35 UT

Re: [beagleboard] element14 vs Circuitco Rev C

Hi! Maybe I found a problem. I put my Image on the uSD and flash again. The Log: http://pastebin.com/HiZR9USh Here I see now: Running /dev/mmcblk0p1/autorun.sh...<\r><\n> dd: writing '/dev/mmcblk1': No space left on device<\r><\n> 0+115617 records in<\r><\n> 0+115616 records out<\r><\n> [ 373.63

Re: [beagleboard] element14 vs Circuitco Rev C

Looks like you missed a response. Gerald On Wed, Sep 9, 2015 at 10:23 AM, Fohnbit wrote: > Hi! > > Maybe I found a problem. I put my Image on the uSD and flash again. The > Log: > http://pastebin.com/HiZR9USh > > Here I see now: > Running /dev/mmcblk0p1/autorun.sh...<\r><\n> > dd: writing '/dev

Re: [beagleboard] element14 vs Circuitco Rev C

On Wed, Sep 9, 2015 at 10:23 AM, Fohnbit wrote: > Hi! > > Maybe I found a problem. I put my Image on the uSD and flash again. The Log: > http://pastebin.com/HiZR9USh > > Here I see now: > Running /dev/mmcblk0p1/autorun.sh...<\r><\n> > dd: writing '/dev/mmcblk1': No space left on device<\r><\n> > 0

Re: [beagleboard] element14 vs Circuitco Rev C

Keep in mind that NAND has bad sectors. That is why they use NAND controllers. NAND size will vary from one part to another. Gerald On Wed, Sep 9, 2015 at 10:28 AM, Robert Nelson wrote: > On Wed, Sep 9, 2015 at 10:23 AM, Fohnbit wrote: > > Hi! > > > > Maybe I found a problem. I put my Image o

[beagleboard] debian: nodejs: v4.0.0

Hey Everyone, nodejs v4.0.0 is being queued for debian experimental.. https://anonscm.debian.org/gitweb/?p=collab-maint/nodejs.git Once pushed to Debian Sid/Stretch, i'm planning to back port this for Wheezy/Jessie (both currently have v0.10.38) Since is a pretty big jump, i figured i'd give ev

[beagleboard] BBB: Which kernel version of linux 3.8.13-boneXY gives more stable wifi with Tp-Link TL-WN727N

Greetings, I have two questions. 1) We are now working on two BBB one with latest kernel version of v3.8.13-bone74(updated kernel version) and other with v3.8.13-bone47(build in kernel version). To install driver of Tp-Link TL-WN727N on BBB it required the header files of the kernel. I was ab

Re: [beagleboard] BBB: Which kernel version of linux 3.8.13-boneXY gives more stable wifi with Tp-Link TL-WN727N

On Wed, Sep 9, 2015 at 10:50 AM, Upol Ryskulova wrote: > Greetings, > > I have two questions. > > 1) We are now working on two BBB one with latest kernel version of > v3.8.13-bone74(updated kernel version) and other with v3.8.13-bone47(build > in kernel version). To install driver of Tp-Link TL-W

[beagleboard] Cannot set pins by overlay

Hello there, I just got back to my BeagleBone Black and i have no idea why but I just cannot change a pin configuration using overlay nor through export. This is what I am trying to do: I want to set P8_29 and P8_31 Pins to inputs with a pullup (0x37). here is my overlay: /dts-v1/; /plugin/;

Re: [beagleboard] Working links to blank-EEPROM flasher image?

Robert, I'm not having success - the serial monitor continues to display "C" as soon as it's powered up, so that seems to indicate that it's not finding anything bootable on that SD card with the blank flasher image. 1. My setup: 64-bit Debian Jessie (as VirtualBox VM on a Win7 host);

Re: [beagleboard] Working links to blank-EEPROM flasher image?

On Wed, Sep 9, 2015 at 12:52 PM, Phil Mills wrote: > Robert, > > I'm not having success - the serial monitor continues to display "C" as > soon as it's powered up, so that seems to indicate that it's not finding > anything bootable on that SD card with the blank flasher image. Yeah... "Virtua

Re: [beagleboard] Working links to blank-EEPROM flasher image?

Did you set the "boot" bit on the uSD card? --- Graham == On Wednesday, September 9, 2015 at 12:52:31 PM UTC-5, Phil Mills wrote: > > Robert, > > I'm not having success - the serial monitor continues to display "C" > as soon as it's powered up, so that seems to indicate that it's not finding

Re: [beagleboard] Working links to blank-EEPROM flasher image?

On Wed, Sep 9, 2015 at 1:01 PM, Graham wrote: > Did you set the "boot" bit on the uSD card? > --- Graham 'boot' bit is set in the raw *.img If the vm skipped setting that one bit, who knows what else it skipped.. :) Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit ht

Re: [beagleboard] Re: Beagle Board REV.C

Thank you Gerald but in this link only there are files for Orcad and Allegro. Are there these files for Altium? Thanks again, Regards, Aleix. ___ *Aleix López* *Mòbil: 699.92.96.83* *aleix.lopez.an...@gmail.com * *es.linkedin.com/pub/aleix-lopez/

Re: [beagleboard] Re: Beagle Board REV.C

Look down. Gerald If you are interested in an *Altium* version, there is a version for the original A5B board they can be found at Altium A5B . These files are provided *AS IS* with no sup

Re: [beagleboard] Working links to blank-EEPROM flasher image?

Guys . . it's not the boot bit, and it's not the virtual machine. I use virtualbox _all_the_time_ and have no such issues. @Phil What sdcard reader does your laptop have in it ? Name brand, and type. Chances are pretty good that you're just unaware of how to setup such devices in the virtualbox

Re: [beagleboard] Working links to blank-EEPROM flasher image?

So short version. . . Virtualbox main screen -> click settings. subsection "USB" -> click it. On the USB filter section - Far right - Click the second from the top icon that looks like a pen with a plus sign on it. >From here, a fly out will popup listing the USB devices virtualbox sees. If your

Re: [beagleboard] Working links to blank-EEPROM flasher image?

Also, for the record Win32imager is garbage, and is one reason why I recommend setting up either a real machine, or virtual machine with Linux ( preferably Debian ) when developing for the beaglebone black. There is also another options Phil. You can use the beaglebone to write the image for you.

Re: [beagleboard] Working links to blank-EEPROM flasher image?

Ah, but I keep forgetting . . . I can do this personally because I boot NFS root . . . with tons of additional space left. So unles you're able to get NFS root working, or use a USB thumb( USB host on the BBB ) drive this won't work. On Wed, Sep 9, 2015 at 12:45 PM, William Hermans wrote: > Also

Re: [beagleboard] Working links to blank-EEPROM flasher image?

Win32Imager definitely works better for my setup (and resulted in a bootable SD card). I'm happy leaving the VM out of this part of the process - detection and mounting of USB devices that get transferred to it from the host is INCREDIBLY hit-or-miss on this VM. First pass at running with a ca

Re: [beagleboard] Working links to blank-EEPROM flasher image?

Sound like you have it under control then. Glad you got it working. A couple of side notes . . . I use Debian Wheezy i386 ( 32bit ) for all my dev machines for the beaglebone. Have had great success with all. Virtual machine, or real. However, I do not use X at all. Just a basic command line inter

[beagleboard] BBB LCD4 display

Hi, I am trying for a while to get a BBB display working. It is the small version with the cape BB-View from Element 14. I built to the newest Debian kernel and copied from the BB-View Image: cp am335x-boneblack-lcd4.dtb am335x-boneblac k.dtb Then I tried a: optargs=capemgr.disable_partn

Re: [beagleboard] BBB LCD4 display

We are not mind readers . . . So, what kernel ? As in version, and did you build this kernel from source yourself ? How ? Did you compare your config with the element14 kernel config to make sure you did not miss anything ? Obvious inconsistencies . . cp am335x-boneblack-lcd4.dtb am335x-boneblac

[beagleboard] PRU/ARM communication with shared memory

Hi I am facing a strange problem with my application. I have some code running on PRU0 and PRU1 that share some data using scratchpad. PRU1 also send some data to ARM, 32 bytes at each time with a counter value as timestamp. each time a new chuck of data is ready, it is written in a circular b

Re: [beagleboard] PRU/ARM communication with shared memory

Hard to guess, but if I were to guess I would guess that the OS side of things is reading the memory faster than the PRU can build the buffer - Sometimes. I also experienced using POSIX shared memory between two process in Linux. How I dealt with this was pretty simplistic. struct shared {

Re: [beagleboard] PRU/ARM communication with shared memory

Well, buffer in my case was actually fixed size buffer[], and not a pointer type character array, but you get the idea I hope. On Wed, Sep 9, 2015 at 4:10 PM, William Hermans wrote: > Hard to guess, but if I were to guess I would guess that the OS side of > things is reading the memory faster th

Re: [beagleboard] PRU/ARM communication with shared memory

In addition to the above . . . It sounds as though you're not clearing your data once you're done with it. So perhaps, and I'm speculating here. The value the PRU is put into a variable initially - Where then you copy that value into a ring / circular buffer. If you're getting identical time stamp

[beagleboard] Beaglebone Black : miss mii.ko and usbnet.ko so no USB to ethernet converter work !

Hi guys ! I need a second ethernet interface on my BBB so I am using an asix usb to ethernet converter On my linux desktop I discovered that mii and usbnet modules access to the module asix ( lsmod ), but these modules miss from my BBB debian image ! so ifconfig don't recognize a

Re: [beagleboard] Beaglebone Black : miss mii.ko and usbnet.ko so no USB to ethernet converter work !

First off, you should probably tell us what you have running for Linux on your beaglebone black. Debian ? Is it custom, and if so where did it come from ? Passed that, usbnet is probably on your system. william@xanbustester:~/can-dev/can-web$ sudo find / -name usbnet.ko [sudo] password for willia

Re: [beagleboard] Proper way to Mux PRU pin without Cape Manager

Hi Charles, No experience with how patches should be introduced, but below is a patch for config-pin on linux 3.14.51 Hope this helps someone. md5sum of the original config pin: 74a71c0a84c46d2df4e14113dea4834a The problem was related to changes in how the /sys/ files are named. Tried 4.1.x a

Re: [beagleboard] Proper way to Mux PRU pin without Cape Manager

On Sep 9, 2015 7:17 PM, wrote: > > Hi Charles, > > No experience with how patches should be introduced, but below is a patch for config-pin on linux 3.14.51 > Hope this helps someone. > > md5sum of the original config pin: 74a71c0a84c46d2df4e14113dea4834a > > The problem was related to changes in

Re: [beagleboard] element14 vs Circuitco Rev C

Ok, the good thing is: now we know where the problem is But ... How can I backup from element14 to Circuitc? I used this: http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents Thank you! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you