Thanks Robert, as usual you are a star ! Kind Regards Marc
w www.sancloud.co.uk m +44781 0812922 SANCLOUD LTD registered office: 164 Walkden Road, Worsley, Manchester, M28 7DP, England. Registration No: 8154061 VAT No: GB 153 7871 85 This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the addressee. If you are not the addressee please note that any distribution, reproduction, copying, publication or use of this communication or the information is prohibited. If you have received this communication in error, please contact us immediately and also delete the communication from your computer. >-----Original Message----- >From: Robert Nelson [mailto:[email protected]] >Sent: 22 May 2017 18:55 >To: Beagle Board; [email protected] >Cc: Marc Murphy >Subject: Re: [beagleboard] Latest test image with SanCloud BeagleBone Black >Enhanced (ethernet broken) > >Hi Paul, > >On Mon, May 22, 2017 at 6:17 AM, Paul Carpenter <[email protected]> >wrote: >> Hi all, >> I am using the BeagleBone Enhanced from SanCloud and using it for >> several IOT related projects. We have used the stable March build with >> success but we just recently added the latest LCD touch display from >> NewHaven. In order to get that to work, we went to the latest test >> image (5/14/2017) from the WiKi. It seems the onboard Ethernet connection >no longer works. The 'eth0' >> interface is recognized and is set up as a DHCP client. It sends the >> IP request out and the DHCP server responds. However, it appears the >> BBBe's driver/firmware does not process the response. Using a static >> IP address doesn't work nor does the latest console or LXQT images. >> >> Any thoughts? I know this image is a test image and I saw a note that >> the SanCloud BBBe needs work and more testing. I am wondering if a >> work-around has been found. > >Yeah i hadn't completely finished porting all the clone boards to u-boot >overlays. > >I just finished the SanCloud for you and Marc this morning.. It'll be a few >days, >(kernel builders are behind as 4.12.0-rc2 is being worked on), till i have a >new >out of the box image. > >But to get your board working now/today, follow these 7 steps..: > >*********************************************************** >*********************** >1: remove NewHaven display >2: bootup, login, disable "enable_uboot_overlays=1" > >sudo sed -i -e 's:enable_uboot_overlays=1:#enable_uboot_overlays=1:g' >/boot/uEnv.txt > >3: reboot (this will boot the old device tree) and ethernet should work. > >4: update Device Tree's > >cd /opt/source/dtb-4.4-ti/ >debian@beaglebone:/opt/source/dtb-4.4-ti$ git pull >remote: Counting objects: 10, done. >remote: Compressing objects: 100% (5/5), done. >remote: Total 10 (delta 4), reused 10 (delta 4), pack-reused 0 Unpacking >objects: 100% (10/10), done. >From https://github.com/RobertCNelson/dtb-rebuilder > 3bff3bd..3b44f63 4.4-ti -> origin/4.4-ti >Updating 3bff3bd..3b44f63 >Fast-forward > src/arm/am335x-boneblack-ctag-face.dts | 10 +- src/arm/am335x- >bonegreen-ctag-face.dts | 10 +- src/arm/am335x-sancloud-bbe- >common.dtsi | 466 ++++++++++++++++++++ > src/arm/am335x-sancloud-bbe-uboot.dts | 26 ++ > src/arm/am571x-sndrblock-common.dtsi | 749 >++++++++++++++++++++++++++++++++ > src/arm/am571x-sndrblock.dts | 125 ++++++ > 6 files changed, 1376 insertions(+), 10 deletions(-) create mode 100644 >src/arm/am335x-sancloud-bbe-common.dtsi > create mode 100644 src/arm/am335x-sancloud-bbe-uboot.dts > create mode 100644 src/arm/am571x-sndrblock-common.dtsi > create mode 100644 src/arm/am571x-sndrblock.dts >debian@beaglebone:/opt/source/dtb-4.4-ti$ make >debian@beaglebone:/opt/source/dtb-4.4-ti$ sudo make install > >5: update U-Boot > >$ cd /opt/scripts/tools/developers/ >debian@beaglebone:/opt/scripts/tools/developers$ git pull Already up-to- >date. >debian@beaglebone:/opt/scripts/tools/developers$ sudo >./update_bootloader.sh bootloader:[/dev/mmcblk1]:[U-Boot 2017.05-00002- >gc0970ed183] > ><noise> > >----------------------------- >Bootloader Updated >Bootloader Recovery Complete > >6: reboot and verfy U-Boot (2017.05-00002-gc0970ed183 this is today's build >that specifically add the SanCloud BBE to the u-boot overlays) > >Option A: (if you have a serial cable) > >*********************************************************** >*********************** >U-Boot SPL 2017.05-00002-gc0970ed183 (May 22 2017 - 11:14:48) Trying to >boot from MMC2 > >U-Boot 2017.05-00002-gc0970ed183 (May 22 2017 - 11:14:48 -0500), >Build: jenkins-github_Bootloader-Builder-556 > >CPU : AM335X-GP rev 2.1 >I2C: ready >DRAM: 1 GiB >Reset Source: Global warm SW reset has occurred. >Reset Source: Power-on reset has occurred. >MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 >Using default environment > >Board: BeagleBone Black >Model: SanCloud BeagleBone Enhanced >*********************************************************** >*********************** > >Option B: (if you don't have a serial cable) > >$ cd /opt/scripts/tools/ >debian@beaglebone:/opt/scripts/tools$ sudo ./version.sh | grep bootloader >[sudo] password for debian: >bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.05-00002- >gc0970ed183] > >7: Re-Enable "enable_uboot_overlays=1", shutdown, and re-install the New >HavenCape > >sudo sed -i -e 's:#enable_uboot_overlays=1:enable_uboot_overlays=1:g' >/boot/uEnv.txt >sudo systemctl poweroff > >*********************************************************** >*********************** > >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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/MM1P123MB08582B84B4E2B6655CF142A1DDF80%40MM1P123MB0858.GBRP123.PROD.OUTLOOK.COM. For more options, visit https://groups.google.com/d/optout.
