[beagleboard] interfacing the Sterling LWB module to the BeagleBone Black
We are developing a new product around the BeagleBone Black that uses the Sterling LWB Wi-Fi/Bluetooth module. LSR supplies some rather convoluted information on their website to build the drivers for this product in a Linux environment. Following their steps yields results completely different from their guidance. Has anyone ever attempted to integrate this radio into a BeagleBone Black project? If so did you get it to work and how did you accomplish 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/11a883d5-f068-4a0d-a3e5-7fd9825427ec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: BB-Blue and stepper motor
Hi Too much difficult for me in this way. Best regards, many 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/ce76a8fc-af59-4d76-984b-0f8c589fb3cf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Windows 10 Bone_D64.exe Failing
Updating the BIOS did not work for me, but installing RNDIS drive worked with the following instructions (found somewhere else that I cannot find now) device manager Under other devices choose RNDIS right click on it and update driver Browse my computer let me pick "Network adapters" select microsoft from on the left choose "USB RNDIS" Click next click yes then close DONE!!! YEAH !!! On Wednesday, August 12, 2015 at 8:13:13 PM UTC-7, mscleavite wrote: > > I have just upgraded to Windows 10 on a machine that I have not previously > connected my BBB to. I had success on other windows 8 machines as well as > SSHing using Putty. I have spent SOME time searching forums and not > finding much at all on Windows 10. During the install of the Bone_D64.exe, > the driver the status returned on all the drivers is "Install Failed". Let > the flaming begin. Or hopefully there is someone out there that has > encountered and concurred this. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/ea57cd86-83db-424d-b7fd-ea9490f42893%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Serial Communication on Beaglebone Black
I've been using a beaglebone black (in debian) to communicate with my Matsuura MC800 VF (1993). It's got an old yasnac I-80 controller on it, and I have to drip feed most stuff because I've only got about 30k of program memory. For the record I was unable to get this to work with USB to serial adapters, in both Windows and Linux. As soon as I went directly to the UART pins it was easy. I recommend using stty to set the serial port, and the just copy the file you want to the serial port. For example, I run at 4800 baud, 7 data bits even parity 1 stop bit with software "flow control". Here's how I set the port settings for the beaglebone black: stty -F /dev/ttyS1 4800 parenb cs7 -icrnl ixon nl1 cr1 then do something like this to copy the file to the serial port and have the beaglebone spit it out. In my case I'm using serial (uart) 1: cp /pathtofile/mycncfile.nc /dev/ttyS1 You can do it in Python, but I'd get it working at the most basic level first. With Python there could be additional software buffers between you and the cnc machine that could cause issues. I use a max232 between the beaglebone and the machine for level shifting. I'm currently using an old one a buddy soldered up and had laying around, but I'm going to put in a more professional max232 in the next couple days. The one I got was on Amazon link here: https://www.amazon.com/gp/product/B00HKIMBZW/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 It looks, good, but I haven't tested it yet. Now, I've got a question for you guys. Has anyone been able to get hardware flow control working on the beaglebone black in debian? -Marc On Wednesday, November 15, 2017 at 1:49:26 AM UTC-8, Jeff Andich wrote: > > Yeah we also stumbled last-week on Tx and Rx being swapped/ ‘crossed’ for > UART1 (?only?) on the BB-X15 AND TI 572x evm REVA3 schematics. The other > UARTS appear fine. Details to follow. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/ffda1210-e667-4ca6-b8df-3bf2f97cfc01%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Windows 10 Bone_D64.exe Failing
On Fri, Feb 2, 2018 at 9:48 PM, wrote: > Updating the BIOS did not work for me, but installing RNDIS drive worked > with the following instructions (found somewhere else that I cannot find > now) > > device manager > Under other devices choose RNDIS > right click on it and update driver > Browse my computer > let me pick > "Network adapters" > select microsoft from on the left > choose "USB RNDIS" > Click next > click yes > then close > DONE!!! YEAH !!! We transitioned to using Microsoft's built-in drivers about a year ago. All the 'latest' images no longer require that signed driver. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYgS5%3DNnLCi72thguYcGXgtKcZM%2Bun1uwwpG3wDez0hKRQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] PocketBeagle SD Card Extra Storage
On Fri, Feb 2, 2018 at 5:00 PM Robert Nelson wrote: > On Fri, Feb 2, 2018 at 9:15 AM, Jack_H wrote: > > Hello all. > > > > > > I was wondering if there were any resources for adding an additional > > microSD card to the pocketbeagle for storage. I currently have a microSD > > click from MikroElektronika but it’s not listed under the pocketbeagle > > "working" mikrobus. > > Oh, that's easy, prove it can work, and provide a pull request here > for both spix positions: > > https://github.com/beagleboard/bb.org-overlays/ > > Then update the wiki. > > Just because I haven't purchased that click doesn't mean it 'will not' > work.. ;) > > > > I currently have an ethernet click working with my pocketbealge and > > beaglebone black using very similar code snippets. I have found resources > > for using a microSD card for the beaglebone black from > > > > here > > > > and here > > > > and this tutorial > > > > Will any of this translate over to the pocketbeagle? > > There's a new driver in v4.14.x? and a device tree node; "mmc-slot" > CONFIG_MMC_SPI > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt I found it in the 4.9 driver and made an attempt to build it natively as a module and give it a try: https://gist.github.com/jadonk/53ae22d550021bf32a299acbd7b546aa I optimized the loading time for the git clone with a shallow checkout. The build happens pretty fast. It didn't load for me at first. I was able to load it, by doing a depmod and modprobe manually, but it never reports anything beyond: mmc_spi spi2.1: SD/MMC host mmc3, no WP, no poweroff So, got any ideas? How should I specify the interrupts? sudo apt-get update sudo apt-get install linux-headers-`uname -r` cd mkdir linux cd linux/ git init git config core.sparsecheckout true git remote add origin https://github.com/beagleboard/linux echo drivers/mmc/host > .git/info/sparse-checkout git fetch origin/4.9 --depth 1 git checkout 4.9 cd drivers/mmc/host CONFIG_MMC_SPI=m make -C /lib/modules/`uname -r`/build M=$PWD sudo make -C /lib/modules/`uname -r`/build M=$PWD INSTALL_MOD_DIR=kernel/drivers/mmc/host modules_install cd /lib/modules/`uname -r` sudo depmod -a sudo /opt/scripts/tools/developers/update_initrd.sh cd /opt/source/bb.org-overlays echo < src/arm/PB-SPI1-MICROSD-CLICK.dts /* * Copyright (C) 2018 Texas Instruments, Jason Kridner * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License version 2 as * published by the Free Software Foundation. * * https://www.mikroe.com/microsd-click * https://download.mikroe.com/documents/add-on-boards/click/microsd/microsd-click-schematic.pdf */ /dts-v1/; /plugin/; #include #include #include / { /* * Free up the pins used by the cape from the pinmux helpers. */ fragment@0 { target = <&ocp>; __overlay__ { P1_36_pinmux { status = "disabled"; }; /* CD - gpio3_14*/ P2_25_pinmux { status = "disabled"; }; /* MOSI - gpio1_9 */ P2_27_pinmux { status = "disabled"; }; /* MISO - gpio1_8 */ P2_29_pinmux { status = "disabled"; }; /* CLK - gpio0_7 */ P2_31_pinmux { status = "disabled"; }; /* CS - gpio0_19 */ cape-universal { status = "disabled"; }; cape-universal@1 { status = "disabled"; }; }; }; fragment@1 { target = <&spi1>; __overlay__ { #address-cells = <1>; #size-cells = <0>; status = "okay"; channel@0 { status = "disabled"; }; channel@1 { status = "disabled"; }; mikroe_microsd: mikroe_microsd@0{ compatible = "mmc-spi-slot"; pinctrl-names = "default"; pinctrl-0 = < &P2_31_spi_cs_pin &P2_29_spi_sclk_pin &P2_27_spi_pin &P2_25_spi_pin &P1_36_gpio_pin >; reg = <1>; gpios = <&gpio3 14 0>; voltage-ranges = <3300 3300>; spi-max-frequency = <5000>; }; }; }; }; make sudo make install sudo perl -i -pe 's/^#(.*)/$1PB-SPI1-MICROSD-CLICK/;' /boot/uEnv.txt -- [0.