Hi Fred, This Gateway Cape is extra special. It's eeprom is blank, it was designed without following our cape spec, so it's basically impossible to detect on bootup.. Then they added random jumpers to change other connections.. So yeah pain in the.....
set: disable_uboot_overlay_emmc=1 uboot_overlay_addr0=/lib/firmware/BB-GATEWAY-WL1837-00A0.dtbo in /boot/uEnv.txt If you change any jumpers, make sure to us the source under /opt/source/bb.org-overlays/ to update BB-GATEWAY-WL1837-00A0.dtbo... Yes, the Windows 7's "built-in" serial driver doesn't work.. Micosoft added this "built-in" serial driver in Windows 8, and didn't back port to Windows 7. Windows 7 only has one more year left in "extended support" and I do not have any Windows 7 (nor Windows 8 machines to test..) Yes root was removed from ssh, as a few BeagleBoard Blacks ended up in bot nets.. Regards, On Thu, Jan 17, 2019 at 6:23 AM 'Yorkey, Christopher' via BeagleBoard < [email protected]> wrote: > Hi Fred, > > If you can bear with us, we're going to retrieve the same Cape and pull > the exact image and instructions and see if we can provide you some > guidance shortly. > > Not to get ahead of ourselves, but there are also several quality > third-party developers with specific experience on this platform. If you > may be interested in learning more, please do let us know. > > Regardless, stay tuned for more information shortly. > > Thank you, > Chris & Team > > > -------- Original message -------- > From: Fred DUFFY <[email protected]> > Date: 1/15/19 2:24 PM (GMT-05:00) > To: "Yorkey, Christopher" <[email protected]>, Jason Kridner < > [email protected]>, Rachel Adamec <[email protected]> > Cc: "DiNino, Nick" <[email protected]>, "Coletti, Jeffrey" <[email protected]>, > [email protected] > Subject: RE: [EXTERNAL] Re: TI Follow Up Material - Beagleboard setup > instructions > > Hi Chris et al., > > > > Thanks for following up. I was able to begin the evaluation. There was a > driver issue where windows (7) would not load the CDC serial driver. I > could not follow the start procedure then as the pc could not communicate > with the Beaglebone. I tried it on my Macbook Pro and was able to get it > to work. I did perform the update and wrote the update FW to the eMMC. > This resolved many of the issues. The serial driver still does not load > properly on windows (7) but I was able to run the getting started steps. I > followed the advice and tried on a windows 10 pc. While it did work there > is still a message that drivers were not loaded (CDC ECM). The elements on > the (Beaglebone 101) page do work. My next step was to try and attach the > BBONE-GATEWAY-CAPE. Following the steps in the Readme I have not been able > to get that up and running. First problem is the root password. This is > not accepted - says access denied. I was able to get in by SSH/PuTTY and > used the username Debian and password temppwd. I tried setting a root > password with sudo but after a restart root still won't work - not sure > that is a problem since I can proceed with the Debian username. It would > be nice if the documentation reflected the actual experience. > > > > What exactly needs to be done to enable the wireless cape. The readme > instructions are either not correct or not enough explanation for me to > make the changes needed to enable it. Perhaps I am not as versed in what > needs to be done and it is an insufficiency on my part. > > > > The uEnv.txt from the /boot and the latest firmware is: > > ============================================ > > uEnv.txt > > #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 > > > > uname_r=4.14.71-ti-r80 > > #uuid= > > #dtb= > > > > ###U-Boot Overlays### > > ###Documentation: > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays > > ###Master Enable > > enable_uboot_overlays=1 > > ### > > ###Overide capes with eeprom > > #uboot_overlay_addr0=/lib/firmware/<file0>.dtbo > > #uboot_overlay_addr1=/lib/firmware/<file1>.dtbo > > #uboot_overlay_addr2=/lib/firmware/<file2>.dtbo > > #uboot_overlay_addr3=/lib/firmware/<file3>.dtbo > > ### > > ###Additional custom capes > > #uboot_overlay_addr4=/lib/firmware/<file4>.dtbo > > #uboot_overlay_addr5=/lib/firmware/<file5>.dtbo > > #uboot_overlay_addr6=/lib/firmware/<file6>.dtbo > > #uboot_overlay_addr7=/lib/firmware/<file7>.dtbo > > ### > > ###Custom Cape > > #dtb_overlay=/lib/firmware/<file8>.dtbo > > ### > > ###Disable auto loading of virtual capes (emmc/video/wireless/adc) > > #disable_uboot_overlay_emmc=1 > > #disable_uboot_overlay_video=1 > > #disable_uboot_overlay_audio=1 > > #disable_uboot_overlay_wireless=1 > > #disable_uboot_overlay_adc=1 > > ### > > ###PRUSS OPTIONS > > ###pru_rproc (4.4.x-ti kernel) > > #uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo > > ###pru_rproc (4.14.x-ti kernel) > > uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo > > ###pru_uio (4.4.x-ti, 4.14.x-ti & mainline/bone kernel) > > #uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo > > ### > > ###Cape Universal Enable > > enable_uboot_cape_universal=1 > > ### > > ###Debug: disable uboot autoload of Cape > > #disable_uboot_overlay_addr0=1 > > #disable_uboot_overlay_addr1=1 > > #disable_uboot_overlay_addr2=1 > > #disable_uboot_overlay_addr3=1 > > ### > > ###U-Boot fdt tweaks... (60000 = 384KB) > > #uboot_fdt_buffer=0x60000 > > ###U-Boot Overlays### > > > > cmdline=coherent_pool=1M net.ifnames=0 quiet > > > > #In the event of edid real failures, uncomment this next line: > > #cmdline=coherent_pool=1M net.ifnames=0 quiet video=HDMI-A-1:1024x768@60e > > > > #Use an overlayfs on top of a read-only root filesystem: > > #cmdline=coherent_pool=1M net.ifnames=0 quiet overlayroot=tmpfs > > > > ##enable Generic eMMC Flasher: > > ##make sure, these tools are installed: dosfstools rsync > > #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh > > > > ================================================================ > > > > I was able to uncomment the last line so that on a re-start the updated FW > flashed to the onboard eMMC. > > > > Any assistance you could provide to enable the Cape would be appreciated. > > > > We still feel this could be a usable design for what we are looking to do > but I am not sure that we have the time and resources for the amount of > work that is needed. Some of the other solutions we are looking at readier > to go IoT Zigbee gateways. > > > > The core thing we are looking to do is quickly create a design that can be > ready for production by Q3 2019 due to the new needs required by projects > as well as the hole created by the collapse of the Artik infrastructure for > which we were developing. We have proprietary lighting control protocol > (known as TopDog) developed by Legrand (Wattstopper) and used on the CC1000 > and CC1110. We will integrate this onto a Zigbee IoT gateway to control > other devices by company items joined to Legrand (Q motion shades). This > gateway will connect to a cloud to enable Alexa and Google via ethernet and > possibly Wi-Fi. We have determined the Ethernet is essential so it will > have that as a minimum. We may add the Wi-Fi to allow for both depending > on product management decisions. > > > > What we need is a platform that is at least fairly hardware ready, then > just develop the Linux based code and migrate control schema from our > previous lighting controller that had an embedded processor (non Linux). > > > > We are still considering all options. Any help would be appreciated! > > > > Thanks > > > > > > *Fred Duffy* > Electrical Engineer, Sr > AUDIO VIDEO > 7175465413 / Fax 7177022546 > [email protected] > www.legrand.us > > www.legrandav.com > > [image: > https://servicecenterqa.legrand.us/lna/infotech/notes/signature/logos/legrandav.png] > > *Legrand, North & Central America* > 301 Fulling Mill Road > Suite G > Middletown, PA, US, 17057 > Nuvo | On-Q > > > > *From:* Yorkey, Christopher [mailto:[email protected]] > *Sent:* Monday, January 14, 2019 10:27 AM > *To:* Jason Kridner <[email protected]>; Fred DUFFY < > [email protected]>; Rachel Adamec <[email protected]> > *Cc:* DiNino, Nick <[email protected]>; Coletti, Jeffrey <[email protected]>; > [email protected] > *Subject:* RE: [EXTERNAL] Re: TI Follow Up Material - Beagleboard setup > intructions > > > > *Jason* – thanks much for your comments and guidance. > > > > *Fred and Rachel* – can one of you please provide us an update? We stand > ready to assist but want to understand where you are specifically in the > evaluation process with the beaglebone hardware. Thank you. > > > > Regards, > > Chris & Team > > > > *From:* Jason Kridner [mailto:[email protected] <[email protected]>] > *Sent:* Monday, January 07, 2019 7:10 PM > *To:* Yorkey, Christopher > *Cc:* Rachel Adamec; DiNino, Nick; Fred DUFFY; Coletti, Jeffrey; > [email protected] > *Subject:* [EXTERNAL] Re: TI Follow Up Material - Beagleboard setup > intructions > > > > Support for the latest Windows versions is something addressed in releases > following the one likely on your board. The Microsoft folks did some > annoying refactoring of their code and it broke the driver loads. The > current process is described in the Getting Started materials Christopher > pointed out and is now a fair bit simpler than the older READMEs you have > found. No driver installation is required and Windows 10 will properly > reference the drivers it already includes. This does require a newer image > than the one provided on the board and running from a microSD card is the > easiest solution. We have pre-release versions of the Etcher.io > application that can program the on-board flash, and that would be the > simplest way to do so, if desired. > > > On Jan 7, 2019, at 2:54 PM, Yorkey, Christopher <[email protected]> > wrote: > > Hi Rachel, > > > > Again, we apologize for the struggles you and Fred are experiencing with > the beagle boards. If this is some sort of Windows-thing, that might be > something a little out of our ‘jurisdiction’ so-to-speak. But if it’s > general beagebone startup stuff, which it sounds like maybe it is, we > definitely need to jump in and help you guys out. Actually, either way we > are here to help. > > > > First off, I suggest giving this particular Getting Started page a good > read. Your board out of the box may not include a bootable image so you > will likely need the SD card installed for this purpose. Can you please > double-check that and follow the respective Getting Starting steps for your > specific installation (Windows drivers, Linux image, etc)? > http://beagleboard.org/getting-started > > > > I would like to know where/if it fails. If Fred can perhaps provide more > details around that (screenshots, errors, warnings, etc) that would be > helpful. Thank you for anything you can provide. > > > > Lastly, there is a small FAQ landing page found here: > http://beagleboard.org/support/faq > > > > This may be helpful too. Are you using the Beaglebone Black > specifically? These boards have been in mass production for years, so > typically the out-of-box experience is pretty decent and user friendly. > > > > I’ve also looped Jason from the Beagleboard.org for further comment. > > > > Thank you, > Chris > > > > *From:* Rachel Adamec [mailto:[email protected] > <[email protected]>] > *Sent:* Monday, January 07, 2019 3:40 PM > *To:* Yorkey, Christopher; DiNino, Nick; Fred DUFFY > *Cc:* Coletti, Jeffrey; [email protected] > *Subject:* [EXTERNAL] Re: TI Follow Up Material - Beagleboard setup > intructions > > > > Chris, > > > > Our efforts with the updated directions and links are leading us down > similar, if not the same, rabbit holes. > > > > We are very dis-heartened at the effort to just connect and start up the > hardware. Thoughts of bringing up our own boards and doing development on > them is the stuff that makes nightmares. > > > > These boards have been around for a while. Hasn't there been some QA work > performed so that there's a chance for a positive out-of-box experience? > > > > R > > > > > > Rachel Adamec > > Team Lead - Processors and Controllers > > Electrical Wiring Systems > > On-Q, Legrand North America > > 301 Fulling Mill Rd, Suite G > > Middletown, PA 17057 > > 717.546.5407 > > [email protected] > > www.legrand.us > ------------------------------ > > *From:* Yorkey, Christopher <[email protected]> > *Sent:* Monday, January 7, 2019 2:53:42 PM > *To:* Rachel Adamec; DiNino, Nick; Fred DUFFY > *Cc:* Coletti, Jeffrey; [email protected] > *Subject:* RE: TI Follow Up Material - Beagleboard setup intructions > > > > Hi Rachel, Fred; > > > > We completely understand and agree. We appreciate your feedback! > > > > For starters, while it may not be obvious, the Windows drivers are > available here (using the Virtual COM drivers): > > https://www.ftdichip.com/Drivers/VCP.htm > > > > Please take a look at this (try to download and install the latest please) > and also review the README setup instruction links here for the specific > Beagleboard you are targeting: > http://beagleboard.org/static/beaglebone/latest/README.htm > > > > (About ½ way down are the notes for the FTDI USB drivers) > > > > Please let me know if this helps? Again, we really appreciate your > efforts with the TI/Beagle eco-system. > > > Regards, > Chris > > > > *From:* Rachel Adamec [mailto:[email protected] > <[email protected]>] > *Sent:* Monday, January 07, 2019 2:33 PM > *To:* DiNino, Nick; Fred DUFFY > *Cc:* Yorkey, Christopher; Coletti, Jeffrey > *Subject:* [EXTERNAL] Re: TI Follow Up Material > > > > Nick, > > > > We're trying to use, get familiar with, a BeagleBone device and have one > here, on-site. > > > > Fred has been trying to set up basic connection to it and cannot get some > of the drivers to load for his Windows machines. He can get some more stuff > working with a MAC, but some of us use Windows pretty much all the time. > > > > Are there updated drivers that are needed? Updated images for the device? > > > > Could you reach out to Fred Duffy to get the full story and get us set > right? Issues like this make us leery when considering the platform we want > to move forward with. > > > > Thanks > > > > R > > > > > > Rachel Adamec > > Team Lead - Processors and Controllers > > Electrical Wiring Systems > > On-Q, Legrand North America > > 301 Fulling Mill Rd, Suite G > > Middletown, PA 17057 > > 717.546.5407 > > [email protected] > > www.legrand.us > > > ------------------------------ > > *From:* DiNino, Nick <[email protected]> > *Sent:* Friday, December 21, 2018 9:42 AM > *To:* Rachel Adamec; Yianni KOSTARIS; Sam Frantz; Donald R Fletcher; Fred > DUFFY > *Cc:* Yorkey, Christopher; Coletti, Jeffrey; Paul Harrington > *Subject:* TI Follow Up Material > > > > Legrand Team, > > > > It was a pleasure meeting with you on Wednesday. We appreciate you > discussing your projects and reviewing our latest products. > > > > I have attached slides used during the presentations. We jumped between > some different decks, so I apologize for the size. I have also summarized > specific devices and additional web pages below. If you need help finding > anything specific please ask. > > > > We can follow up individually on any specifics. Let us know how else we > can help! > > > > Everyone have a Happy Holiday and New Year! > > > > SimpleLink MCU + Wireless Platform > > · SimpleLink Academy <https://training.ti.com/simplelink-academy> > TI Training > > · Beaglebone Black Wireless > <https://beagleboard.org/black-wireless> > > o Octavo OSD3358 <https://octavosystems.com/octavo_products/osd335x/> > > § Sitara AM335x Processors > <http://www.ti.com/processors/sitara-arm/am335x-cortex-a8/overview.html> > > o WL1835MOD <http://www.ti.com/product/WL1835MOD/description> > > § This is a scalable WiLink family > > · Zigbee Cape > > o Wireless Connectivity Cape > <https://www.element14.com/community/docs/DOC-79264?ICID=bbb-connect-ban> > > § CC2530 <http://www.ti.com/product/CC2530/description> for Zigbee. > > · See Low Power RF roadmap (attached) for newer devices in family. > > > > Industrial Radar > > · IWR6843 <http://www.ti.com/product/IWR6843/description> > > · IWR6843ISK <http://www.ti.com/tool/iwr6843isk> intelligent > mmWave sensor standard antenna plug-in module > > · MMWAVEICBOOST <http://www.ti.com/tool/mmwaveicboost> mmWave > sensors carrier card platform > > · TI is investing heavily in mmWave, so kits will continue to > release targeting specific applications. > > · People Counting Demo TIREX Landing Page > <http://dev.ti.com/tirex/#/DevTool/IWR6843ISK%20Antenna%20Plug-In%20Module/?link=Software%2FmmWave%20Sensors%2FIndustrial%20Toolbox%2FLabs%2FPeople%20Counting%20Demo%2F68xx%20-%20People%20Counting%20Demo> > > · mmWave Radar Demonstrations (TI Training Series) > <https://training.ti.com/mmwave-radar-demonstrations> > > o Check out the Industrial videos like People Counting and Gesture > Recognition! > > > > Optical ToF & Ultrasonic Sensing > > · OPT3101 <http://www.ti.com/product/OPT3101/description> – this > may be a simpler, lower cost solution for Occupancy Sensing. > > · Ultrasonic Sensing Landing Page > <http://www.ti.com/sensors/specialty-sensors/ultrasonic/overview.html> > > o PGA460 <http://www.ti.com/product/PGA460/description> > > > > AC/DC Cap Drop LDO > > · TPS7A78 is a Preview device. Samples and EVM are available today. > > > > Regards, > > > > *Nicholas DiNino* > > Technical Sales Representative > > Texas Instruments > > (860) 478-3277 > > [email protected] > > <image001.jpg> > <https://store.ti.com/?HQS=sdm-mm-null-americaseast-besig-store-null-wwe> > > > > > ------------------------------ > > Ce message, ainsi que tous les fichiers joints à ce message, peuvent > contenir des informations sensibles et/ ou confidentielles ne devant pas > être divulguées. Si vous n'êtes pas le destinataire de ce message (ou que > vous recevez ce message par erreur), nous vous remercions de le notifier > immédiatement à son expéditeur, et de détruire ce message. Toute copie, > divulgation, modification, utilisation ou diffusion, non autorisée, directe > ou indirecte, de tout ou partie de ce message, est strictement interdite. > > > > This e-mail, and any document attached hereby, may contain confidential > and/or privileged information. If you are not the intended recipient (or > have received this e-mail in error) please notify the sender immediately > and destroy this e-mail. Any unauthorized, direct or indirect, copying, > disclosure, distribution or other use of the material or parts thereof is > strictly forbidden. > > > ------------------------------ > > Ce message, ainsi que tous les fichiers joints à ce message, peuvent > contenir des informations sensibles et/ ou confidentielles ne devant pas > être divulguées. Si vous n'êtes pas le destinataire de ce message (ou que > vous recevez ce message par erreur), nous vous remercions de le notifier > immédiatement à son expéditeur, et de détruire ce message. Toute copie, > divulgation, modification, utilisation ou diffusion, non autorisée, directe > ou indirecte, de tout ou partie de ce message, est strictement interdite. > > > > This e-mail, and any document attached hereby, may contain confidential > and/or privileged information. If you are not the intended recipient (or > have received this e-mail in error) please notify the sender immediately > and destroy this e-mail. Any unauthorized, direct or indirect, copying, > disclosure, distribution or other use of the material or parts thereof is > strictly forbidden. > > > ------------------------------ > > Ce message, ainsi que tous les fichiers joints à ce message, peuvent > contenir des informations sensibles et/ ou confidentielles ne devant pas > être divulguées. Si vous n'êtes pas le destinataire de ce message (ou que > vous recevez ce message par erreur), nous vous remercions de le notifier > immédiatement à son expéditeur, et de détruire ce message. Toute copie, > divulgation, modification, utilisation ou diffusion, non autorisée, directe > ou indirecte, de tout ou partie de ce message, est strictement interdite. > > This e-mail, and any document attached hereby, may contain confidential > and/or privileged information. If you are not the intended recipient (or > have received this e-mail in error) please notify the sender immediately > and destroy this e-mail. Any unauthorized, direct or indirect, copying, > disclosure, distribution or other use of the material or parts thereof is > strictly forbidden. > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/a76a7dc43df1454ca8e019a1f175087a%40ti.com > <https://groups.google.com/d/msgid/beagleboard/a76a7dc43df1454ca8e019a1f175087a%40ti.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhunMcwE%3Dx9TXfYazaSHK_CjK3GQZcu8hOYpebdteN2iQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
