Re: [beagleboard] How to install linux-headers-3.8.13-bone30
Fixed it finally with the help of you Robert and your wiki at http://www.google.com/url?q=http%3A%2F%2Feewiki.net%2Fdisplay%2Flinuxonarm%2FBeagleBone%2BBlack%23BeagleBoneBlack-LinuxKernelsa=Dsntz=1usg=AFQjCNEi3aoe_0Ji869KciAB8XsYvDQyVA But aptitude finds a package on my ubuntu desktop but doesn't from your image, but its not a problem, I used to cheese and the webcam is detected. Thanks for the support. One last question? Shall I install ubuntu desktop in my sd card now. I hope that will not mess up the kernel in any way. And cheese works sometimes and doesn't sometimes. What's your comment about cheese. To make /dev/video0 appear from my webcam what can I do, the steps that I followed in my laptop ubuntu to install driver for my webcam was http://superuser.com/questions/31853/how-to-make-creative-vista-webcam-041e405f-work-with-recent-ubuntu I am not able find ov51x-jpeg if I use the command sudo m-a a-i ov51x-jpeg Its works fine in my Ubuntu on laptop. But in BBB, sometimes it doesn't and with cheese, it detects sometimes and sometimes it doesn't. What can be the reason? On Tuesday, 25 February 2014 00:44:05 UTC+5:30, RobertCNelson wrote: On Mon, Feb 24, 2014 at 10:52 AM, jayakar...@gmail.com javascript:wrote: I did from beginning with the image from https://rcn-ee.net/deb/microsd/saucy/bone-ubuntu-13.10-2014-02-16-2gb.img.xz If I am write, I followed your wiki http://elinux.org/BeagleBoardUbuntu And did cd /opt/scripts/tools git pull ./grow_partition.sh sudo reboot then cd /opt/scripts/tools git pull then ./update_kernel.sh --kernel v3.8.13-bone40 then sudo apt-get update sudo apt-get install bc build-essential device-tree-compiler fakeroot lzma lzop man-db libncurses5-dev:armhf then when I try again to build the kernel using your wiki Building the Kernel git clone git://github.com/RobertCNelson/stable-kernel.git I should just delete that repo... Look closely: http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel Regards, -- Robert Nelson http://www.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/groups/opt_out.
Re: [beagleboard] How to install linux-headers-3.8.13-bone30
Robert I did as you said, wget https://raw.github.com/gkaindl/beaglebone-ubuntu-scripts/master/bb-get-rcn-kernel-source.shhttps://www.google.com/url?q=https%3A%2F%2Fraw.github.com%2Fgkaindl%2Fbeaglebone-ubuntu-scripts%2Fmaster%2Fbb-get-rcn-kernel-source.shsa=Dsntz=1usg=AFQjCNGfskw3YeISuBv6xklle5atCCworg chmod +x bb-get-rcn-kernel-source.sh ./bb-get-rcn-kernel-source.sh I got message that kernel installed successfully, when I did cloning from git hub. git clone git://github.com/RobertCNelson/stable-kernel.git I got the following message: root@arm:~# ls stable-kernel root@arm:~# cd stable-kernel root@arm:~/stable-kernel# root@arm:~/stable-kernel# ls branches.list build_kernel.sh LICENSE patch.sh repo_maintenance system.sh tools build_deb.sh deploy patches READMEscripts system.sh.sample version.sh root@arm:~/stable-kernel# ./build_kernel.sh + Detected build host [Ubuntu 13.10] + host: [armv7l] + git HEAD commit: [47443e07185a3c26c7bfd0919a9f874fdb234ef5] - Please checkout one of the active branches: - [git checkout origin/v3.7.x -b tmp] (BeagleBoard Cx/xM PandaBoard/PandaBoard ES) [git checkout origin/v3.9.x -b tmp] (BeagleBoard Cx/xM PandaBoard/PandaBoard ES) It is not building. What can be the reason? On Sunday, 23 February 2014 23:04:30 UTC+5:30, RobertCNelson wrote: On Sun, Feb 23, 2014 at 12:11 AM, jayakar...@gmail.com javascript:wrote: First of all, sorry for posting such a big message, I just want to make things clear... Robert I tried your images available at https://rcn-ee.net/deb/microsd/saucy/bone-ubuntu-13.10-2014-02-16-2gb.img.xz Booted my beaglebone black with the image on sd card. and ran the following commands cd /opt/scripts/tools git pull ./grow_partition.sh sudo reboot cd /opt/scripts/tools git pull root@arm:/home/ubuntu# cd /opt/scripts/tools root@arm:/opt/scripts/tools# git pull Already up-to-date. root@arm:/opt/scripts/tools# ./update_kernel.sh --2014-02-23 06:04:21-- http://rcn-ee.net/deb/saucy-armhf/LATEST-omap-psp Resolving rcn-ee.net (rcn-ee.net)... 69.163.128.251 Connecting to rcn-ee.net (rcn-ee.net)|69.163.128.251|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 237 [text/plain] Saving to: ‘LATEST-omap-psp’ 100%[==] 237 --.-K/s in 0s 2014-02-23 06:04:22 (2.90 MB/s) - ‘LATEST-omap-psp’ saved [237/237] v3.8.13-bone40 is latest Third party modules... Then I did Now just do: wget https://raw.github.com/gkaindl/beaglebone-ubuntu-scripts/master/bb-get-rcn-kernel-source.sh chmod +x bb-get-rcn-kernel-source.sh ./bb-get-rcn-kernel-source.sh git clone git://github.com/RobertCNelson/stable-kernel.git Wrong repo... BTW: just because we can install the headers, doesn't always guarentee some crappy upstream's out of tree modules will build against it.. Regards, -- Robert Nelson http://www.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/groups/opt_out.
Re: [beagleboard] How to install linux-headers-3.8.13-bone30
I did from beginning with the image from https://rcn-ee.net/deb/microsd/saucy/bone-ubuntu-13.10-2014-02-16-2gb.img.xz If I am write, I followed your wiki http://elinux.org/BeagleBoardUbuntu And did cd /opt/scripts/tools git pull ./grow_partition.sh sudo reboot then cd /opt/scripts/tools git pull then ./update_kernel.sh --kernel v3.8.13-bone40 then sudo apt-get update sudo apt-get install bc build-essential device-tree-compiler fakeroot lzma lzop man-db libncurses5-dev:armhf then when I try again to build the kernel using your wiki Building the Kernel git clone git://github.com/RobertCNelson/stable-kernel.git ls ./build_kernel.sh I get the same ubuntu@arm:~/stable-kernel$ sudo ./build_kernel.sh + Detected build host [Ubuntu 13.10] + host: [armv7l] + git HEAD commit: [47443e07185a3c26c7bfd0919a9f874fdb234ef5] - Please checkout one of the active branches: - [git checkout origin/v3.7.x -b tmp] (BeagleBoard Cx/xM PandaBoard/PandaBoard ES) [git checkout origin/v3.9.x -b tmp] (BeagleBoard Cx/xM PandaBoard/PandaBoard ES) tell me what I am doing wrong. On Monday, 24 February 2014 19:22:48 UTC+5:30, RobertCNelson wrote: On Sun, Feb 23, 2014 at 9:07 PM, jayakar...@gmail.com javascript:wrote: Robert I did as you said, wget https://raw.github.com/gkaindl/beaglebone-ubuntu- scripts/master/bb-get-rcn-kernel-source.shhttps://www.google.com/url?q=https%3A%2F%2Fraw.github.com%2Fgkaindl%2Fbeaglebone-ubuntu-scripts%2Fmaster%2Fbb-get-rcn-kernel-source.shsa=Dsntz=1usg=AFQjCNGfskw3YeISuBv6xklle5atCCworg chmod +x bb-get-rcn-kernel-source.sh ./bb-get-rcn-kernel-source.sh I got message that kernel installed successfully, when I did cloning from git hub. git clone git://github.com/RobertCNelson/stable-kernel.git I got the following message: root@arm:~# ls stable-kernel root@arm:~# cd stable-kernel root@arm:~/stable-kernel# root@arm:~/stable-kernel# ls branches.list build_kernel.sh LICENSE patch.sh repo_maintenance system.sh tools build_deb.sh deploy patches READMEscripts system.sh.sample version.sh root@arm:~/stable-kernel# ./build_kernel.sh + Detected build host [Ubuntu 13.10] + host: [armv7l] + git HEAD commit: [47443e07185a3c26c7bfd0919a9f874fdb234ef5] - Please checkout one of the active branches: - [git checkout origin/v3.7.x -b tmp] (BeagleBoard Cx/xM PandaBoard/PandaBoard ES) [git checkout origin/v3.9.x -b tmp] (BeagleBoard Cx/xM PandaBoard/PandaBoard ES) It is not building. What can be the reason? The error is pretty obvious, it clearly shows what branch you need to checkout to support a specific board. As to why you specifically checked out stable-kernel.git git repo.. I can't explain that. As clearly in all my wiki documentation i reference a different repo/branch for the beaglebone family. Regards, -- Robert Nelson http://www.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/groups/opt_out.
Re: [beagleboard] How to install linux-headers-3.8.13-bone30
First of all, sorry for posting such a big message, I just want to make things clear... Robert I tried your images available at https://rcn-ee.net/deb/microsd/saucy/bone-ubuntu-13.10-2014-02-16-2gb.img.xz Booted my beaglebone black with the image on sd card. and ran the following commands cd /opt/scripts/tools git pull ./grow_partition.sh sudo reboot cd /opt/scripts/tools git pull root@arm:/home/ubuntu# cd /opt/scripts/tools root@arm:/opt/scripts/tools# git pull Already up-to-date. root@arm:/opt/scripts/tools# ./update_kernel.sh --2014-02-23 06:04:21-- http://rcn-ee.net/deb/saucy-armhf/LATEST-omap-psp Resolving rcn-ee.net (rcn-ee.net)... 69.163.128.251 Connecting to rcn-ee.net (rcn-ee.net)|69.163.128.251|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 237 [text/plain] Saving to: ‘LATEST-omap-psp’ 100%[==] 237 --.-K/s in 0s 2014-02-23 06:04:22 (2.90 MB/s) - ‘LATEST-omap-psp’ saved [237/237] v3.8.13-bone40 is latest Third party modules... Then I did git clone git://github.com/RobertCNelson/stable-kernel.git I got root@arm:~# ls stable-kernel root@arm:~# cd stable-kernel root@arm:~/stable-kernel# ls branches.listdeploy patch.sh scripts tools build_deb.sh LICENSE READMEsystem.sh version.sh build_kernel.sh patches repo_maintenance system.sh.sample root@arm:~/stable-kernel# ./build_kernel.sh + Detected build host [Ubuntu 13.10] + host: [armv7l] + git HEAD commit: [47443e07185a3c26c7bfd0919a9f874fdb234ef5] - Please checkout one of the active branches: - [git checkout origin/v3.7.x -b tmp] (BeagleBoard Cx/xM PandaBoard/PandaBoard ES) [git checkout origin/v3.9.x -b tmp] (BeagleBoard Cx/xM PandaBoard/PandaBoard ES) - Then I ran the following commands and got this... ubuntu@arm:~$ uname -a Linux arm 3.8.13-bone40 #1 SMP Fri Jan 31 10:36:05 UTC 2014 armv7l armv7l armv7l GNU/Linux ubuntu@arm:~$ ls ubuntu@arm:~$ sudo su [sudo] password for ubuntu: root@arm:/home/ubuntu# sudo m-a prepare Getting source for kernel version: 3.8.13-bone40 apt-get install linux-headers-3.8.13-bone40 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package linux-headers-3.8.13-bone40 E: Couldn't find any package by regex 'linux-headers-3.8.13-bone40' apt-get install build-essential Reading package lists... Done Building dependency tree Reading state information... Done build-essential is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Done! I don't know how to fix this E: Unable to locate package linux-headers-3.8.13-bone40 E: Couldn't find any package by regex 'linux-headers-3.8.13-bone40' Because of this I am not able to build the package for my webcam, stuck with this for the past three weeks... Can anyone help me fix this... On Sunday, 23 February 2014 00:33:59 UTC+5:30, jayakar...@gmail.com wrote: Thanks for the reply Robert. I did it using wget https://raw.github.com/gkaindl/beaglebone-ubuntu-scripts/master/bb-get-rcn-kernel-source.sh chmod +x bb-get-rcn-kernel-source.sh ./bb-get-rcn-kernel-source.sh as you said. It installed the kernel successfully and said done: kernel sources for 3.8.13-bone30 are now installed. you should be able to compile kernel modules. But even after this, when I try to compile a module I am not able to it, I get the same error. I have added the snapshots, kindly check and tell me how to solve this. https://lh3.googleusercontent.com/-AZWZkF0hUTE/Uwj0cZ6l72I/Bz8/pwRGJJQqOq0/s1600/c1.PNG https://lh3.googleusercontent.com/-JZfYL_pRGug/Uwj0hNaGDKI/B0E/OzpF46CUngQ/s1600/c2.PNG https://lh3.googleusercontent.com/-znQiltyzS2A/Uwj0mM_yI1I/B0M/Rty4m00Uzbs/s1600/c3.PNG On Friday, 21 February 2014 20:01:05 UTC+5:30, RobertCNelson wrote: On Thu, Feb 20, 2014 at 10:31 PM, jayakar...@gmail.com wrote: Can you tell me how install this headers. wget file sudo dpkg -i file or even: wget https://raw.github.com/gkaindl/beaglebone-ubuntu-scripts/master/bb-get-rcn-kernel-source.sh chmod +x bb-get-rcn-kernel-source.sh ./bb-get-rcn-kernel-source.sh Will set it up automatically. If you ubuntu-armhf images are not supported by your scripts where can I find the image files support by yours. Let's see, the debian testing image posted to this group every week.. https://groups.google.com/d/msg/beagleboard/D1ioNrzzXfQ/LdfJ2ccuiY4J The ones posted here: http://elinux.org/BeagleBoardUbuntu and here: http://elinux.org/BeagleBoardDebian and here: http://eewiki.net/display/linuxonarm/Home etc/etc.. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard
Re: [beagleboard] How to install linux-headers-3.8.13-bone30
Thanks for the reply Robert. I did it using wget https://raw.github.com/gkaindl/beaglebone-ubuntu-scripts/master/bb-get-rcn-kernel-source.sh chmod +x bb-get-rcn-kernel-source.sh ./bb-get-rcn-kernel-source.sh as you said. It installed the kernel successfully and said done: kernel sources for 3.8.13-bone30 are now installed. you should be able to compile kernel modules. But even after this, when I try to compile a module I am not able to it, I get the same error. I have added the snapshots, kindly check and tell me how to solve this. https://lh3.googleusercontent.com/-AZWZkF0hUTE/Uwj0cZ6l72I/Bz8/pwRGJJQqOq0/s1600/c1.PNG https://lh3.googleusercontent.com/-JZfYL_pRGug/Uwj0hNaGDKI/B0E/OzpF46CUngQ/s1600/c2.PNG https://lh3.googleusercontent.com/-znQiltyzS2A/Uwj0mM_yI1I/B0M/Rty4m00Uzbs/s1600/c3.PNG On Friday, 21 February 2014 20:01:05 UTC+5:30, RobertCNelson wrote: On Thu, Feb 20, 2014 at 10:31 PM, jayakar...@gmail.com javascript:wrote: Can you tell me how install this headers. wget file sudo dpkg -i file or even: wget https://raw.github.com/gkaindl/beaglebone-ubuntu-scripts/master/bb-get-rcn-kernel-source.sh chmod +x bb-get-rcn-kernel-source.sh ./bb-get-rcn-kernel-source.sh Will set it up automatically. If you ubuntu-armhf images are not supported by your scripts where can I find the image files support by yours. Let's see, the debian testing image posted to this group every week.. https://groups.google.com/d/msg/beagleboard/D1ioNrzzXfQ/LdfJ2ccuiY4J The ones posted here: http://elinux.org/BeagleBoardUbuntu and here: http://elinux.org/BeagleBoardDebian and here: http://eewiki.net/display/linuxonarm/Home etc/etc.. Regards, -- Robert Nelson http://www.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/groups/opt_out.
Re: [beagleboard] How to install linux-headers-3.8.13-bone30
Can you tell me how install this headers. If you ubuntu-armhf images are not supported by your scripts where can I find the image files support by yours. On Friday, 21 February 2014 06:50:25 UTC+5:30, RobertCNelson wrote: On Thu, Feb 20, 2014 at 6:04 PM, jayakar...@gmail.com javascript:wrote: While trying to prepare a driver to be installed on my beaglebone black I came across the following error E: Unable to locate package linux-headers-3.8.13-bone30 E: Couldn't find any package by regex 'linux-headers-3.8.13-bone30' These headers? http://rcn-ee.net/deb/precise-armhf/v3.8.13-bone30/ I am running Ubuntu 12.04.4 LTS (GNU/Linux 3.8.13-bone30 armv7l) available at http://www.armhf.com/index.php/download/ I downloaded the source at https://github.com/RobertCNelson/linux-dev/releases/tag/3.8.13-bone30and then used the command ./build_kernel.sh. After the build, while using the command ./tools/install_kernel.sh as said at https://github.com/RobertCNelson/linux-dev I got the following message I see... fdisk -l: Disk /dev/mmcblk0: 15.9 GB, 15931539456 bytes Disk /dev/mmcblk1: 1920 MB, 1920991232 bytes Disk /dev/mmcblk1boot1: 1 MB, 1048576 bytes Disk /dev/mmcblk1boot0: 1 MB, 1048576 bytes lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1boot0 179:16 0 1M 1 disk mmcblk1boot1 179:24 0 1M 1 disk mmcblk0 179:00 14.9G 0 disk |-mmcblk0p1 179:10 1M 0 part /home/ubuntu/linux-dev-3.8.13-bone30/depl `-mmcblk0p2 179:20 14.9G 0 part / mmcblk1 179:80 1.8G 0 disk |-mmcblk1p1 179:9096M 0 part `-mmcblk1p2 179:10 0 1.7G 0 part - Are you 100% sure, on selecting [/dev/mmcblk0] (y/n)? y Debug: Existing Partition on drive: - Disk /dev/mmcblk0: 15.9 GB, 15931539456 bytes 4 heads, 16 sectors/track, 486192 cylinders, total 31116288 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x80008000 Device Boot Start End Blocks Id System /dev/mmcblk0p1 *2048409510241 FAT12 /dev/mmcblk0p240963111628715556096 83 Linux Unmounting Partitions - Starting Partition Search - Trying: [/dev/mmcblk0p1] Partition: [/dev/mmcblk0p1] trying: [vfat], [ext4] Partition: [vfat] Installing 3.8.13-bone30 to /dev/mmcblk0p1 `/home/ubuntu/linux-dev-3.8.13-bone30/deploy/3.8.13-bone30.zImage' - `/home/ubuntu/linux-dev-3.8.13-bone30/deploy/disk/zImage' cp: writing `/home/ubuntu/linux-dev-3.8.13-bone30/deploy/disk/zImage': No space left on device cp: failed to extend `/home/ubuntu/linux-dev-3.8.13-bone30/deploy/disk/zImage': No space left on device : In the system.sh file I have set MMC=/dev/mmcblk0 And for your information, I have an expanded file system in which I have installed ubuntu desktop. Patches welcome, armhf.com's images are not currently supported by my scripts. Regards, -- Robert Nelson http://www.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/groups/opt_out.
[beagleboard] How to install linux-headers-3.8.13-bone30
While trying to prepare a driver to be installed on my beaglebone black I came across the following error E: Unable to locate package linux-headers-3.8.13-bone30 E: Couldn't find any package by regex 'linux-headers-3.8.13-bone30' I am running Ubuntu 12.04.4 LTS (GNU/Linux 3.8.13-bone30 armv7l) available at http://www.armhf.com/index.php/download/ I downloaded the source at https://github.com/RobertCNelson/linux-dev/releases/tag/3.8.13-bone30 and then used the command ./build_kernel.sh. After the build, while using the command ./tools/install_kernel.sh as said at https://github.com/RobertCNelson/linux-dev I got the following message I see... fdisk -l: Disk /dev/mmcblk0: 15.9 GB, 15931539456 bytes Disk /dev/mmcblk1: 1920 MB, 1920991232 bytes Disk /dev/mmcblk1boot1: 1 MB, 1048576 bytes Disk /dev/mmcblk1boot0: 1 MB, 1048576 bytes lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1boot0 179:16 0 1M 1 disk mmcblk1boot1 179:24 0 1M 1 disk mmcblk0 179:00 14.9G 0 disk |-mmcblk0p1 179:10 1M 0 part /home/ubuntu/linux-dev-3.8.13-bone30/depl `-mmcblk0p2 179:20 14.9G 0 part / mmcblk1 179:80 1.8G 0 disk |-mmcblk1p1 179:9096M 0 part `-mmcblk1p2 179:10 0 1.7G 0 part - Are you 100% sure, on selecting [/dev/mmcblk0] (y/n)? y Debug: Existing Partition on drive: - Disk /dev/mmcblk0: 15.9 GB, 15931539456 bytes 4 heads, 16 sectors/track, 486192 cylinders, total 31116288 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x80008000 Device Boot Start End Blocks Id System /dev/mmcblk0p1 *2048409510241 FAT12 /dev/mmcblk0p240963111628715556096 83 Linux Unmounting Partitions - Starting Partition Search - Trying: [/dev/mmcblk0p1] Partition: [/dev/mmcblk0p1] trying: [vfat], [ext4] Partition: [vfat] Installing 3.8.13-bone30 to /dev/mmcblk0p1 `/home/ubuntu/linux-dev-3.8.13-bone30/deploy/3.8.13-bone30.zImage' - `/home/ubuntu/linux-dev-3.8.13-bone30/deploy/disk/zImage' cp: writing `/home/ubuntu/linux-dev-3.8.13-bone30/deploy/disk/zImage': No space left on device cp: failed to extend `/home/ubuntu/linux-dev-3.8.13-bone30/deploy/disk/zImage': No space left on device : In the system.sh file I have set MMC=/dev/mmcblk0 And for your information, I have an expanded file system in which I have installed ubuntu desktop. Anyone help me solve this issue. Thanks in advance. -- 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/groups/opt_out.
Re: [beagleboard] Unable to boot from SD Card for flashing eMMC with Debian/Ubuntu/Angstrom
That's the reason why I didn't apply for the RMA process myself Gerald, as per your advice, I contacted the vendor. They must be buying it from some distributor and they will contact them. I wish they must be buying it from an authorized distributor. On Thursday, 23 January 2014 00:30:36 UTC+5:30, Gerald wrote: Well, they are not an authorized distributor unfortunately. Gerald On Wed, Jan 22, 2014 at 10:33 AM, jayakar...@gmail.com javascript:wrote: The vendor of the product http://www.crazypi.com/ in India will take care of that for me. They also have a good support team like yours. Thanks for the support. On Wednesday, 22 January 2014 22:00:01 UTC+5:30, Gerald wrote: You must to go through the RMA processes before you can get it replaced. Gerald On Wed, Jan 22, 2014 at 10:25 AM, jayakar...@gmail.com wrote: I am using an adapter which gives me an output of 5V, 1A. Below are some pictures of my BBB. https://lh4.googleusercontent.com/-4DQ3mCzQca4/Ut_uhT2LdKI/BmY/pdm5ZWLGh7A/s1600/top.jpg https://lh3.googleusercontent.com/-0290kW0czLY/Ut_vJCSfAqI/Bmg/v-EYOUYqbPc/s1600/serialno.jpg https://lh5.googleusercontent.com/-MHr_BcSpXsA/Ut_vrSHU5zI/Bmo/Vg7VQ_oai9Q/s1600/bottom.jpg It has a beaglebone logo, so I think it is a original board and the vendor mentions it that it is original. The vendor is ready to check it and replace it if it has some hardware issues. Thanks for your support guys. Like I said, I had issue on the first day itself, but I re-flashed it, it worked for a week, after using ubuntu and expanding the file system in that, the issue began. On Wednesday, 22 January 2014 20:23:47 UTC+5:30, Jason Kridner wrote: On Tue, Jan 21, 2014 at 10:18 PM, jayakar...@gmail.com wrote: Can you tell me how to find out weather it is a clone or original. I don't think it is a clone. If it has the BeagleBoard.org logo, it better not be a clone! I think Robert's question was more along the lines of if you were making your own hardware. With the issue description, it really looks like a hardware issue. Because I flashed it once with the eMMC flasher image available at beagleboard website. It was working at that time. I followed the instructions to boot it from sd card with ubuntu and I tried to expand the file system, everything worked. And after that I removed sd card and tried to boot from eMMC I am stuck. I already posted my question in forum but didn't get any answer so I posted it in the way that you will look into it Robert to give a solution, the link of my previous post: http://beagleboard.org/Community/Forums?place=topic%2F beagleboard%2FQFp3aMdKIwQ%2Fdiscussion . I feel something else must have been done to the board. Finally yesterday I sent a mail to Jason and he has replied. I will like this post to my previous post so that Jason will also look into this in detail. And you two tech guys can help me on fixing this. Escalating to me when you don't get an answer with a link to the public post is good. I can't tell you how many times I tell people to post here FIRST! Anyway, given that you cannot read the EEPROM even from u-boot SPL, I think something must be up with the bus. I think it would give a different error if you had simply over written the EEPROM. What are you using as a power supply? What do you have connected to the board? On Wednesday, 22 January 2014 01:20:06 UTC+5:30, RobertCNelson wrote: On Tue, Jan 21, 2014 at 1:07 PM, jayakar...@gmail.com wrote: I am trying to flash my Beaglebone Black with Debain flasher image available at https://rcn-ee.net/deb/flasher/wheezy/BBB-eMMC-flasher-debia n-7.3-2013-12-17-2gb.img.xz But I am not able to do it. I am holding the boot button and then turning on the power supply for the board. The LEDs doesn't turn on even after a long time as I am holding the boot button. I tried to look into what is happening with the help of Serial to USB converter and go the message displayed bellow: U-Boot SPL 2013.10-00015-gab7a95a (Nov 08 2013 - 16:01:27) i2c_probe: pads on bus 0 probably not configured (status=0x10) Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Could not get board ID. i2c_probe: pads on bus 0 probably not configured (status=0x10) Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Could not get board ID. Oh, that's fun.. Your board's eeprom no longer has its id.. is this a real bbb or a clone? The reason the ancient rootfs works, it assumes a bbb, boots, then programs the eeprom and initial eMMC file system. Then ships to customers.. Regards, -- Robert Nelson http://www.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
Re: [beagleboard] Unable to boot from SD Card for flashing eMMC with Debian/Ubuntu/Angstrom
Can you tell me how to find out weather it is a clone or original. I don't think it is a clone. Because I flashed it once with the eMMC flasher image available at beagleboard website. It was working at that time. I followed the instructions to boot it from sd card with ubuntu and I tried to expand the file system, everything worked. And after that I removed sd card and tried to boot from eMMC I am stuck. I already posted my question in forum but didn't get any answer so I posted it in the way that you will look into it Robert to give a solution, the link of my previous post: http://beagleboard.org/Community/Forums?place=topic%2Fbeagleboard%2FQFp3aMdKIwQ%2Fdiscussion . Finally yesterday I sent a mail to Jason and he has replied. I will like this post to my previous post so that Jason will also look into this in detail. And you two tech guys can help me on fixing this. On Wednesday, 22 January 2014 01:20:06 UTC+5:30, RobertCNelson wrote: On Tue, Jan 21, 2014 at 1:07 PM, jayakar...@gmail.com javascript: wrote: I am trying to flash my Beaglebone Black with Debain flasher image available at https://rcn-ee.net/deb/flasher/wheezy/BBB-eMMC-flasher-debian-7.3-2013-12-17-2gb.img.xz But I am not able to do it. I am holding the boot button and then turning on the power supply for the board. The LEDs doesn't turn on even after a long time as I am holding the boot button. I tried to look into what is happening with the help of Serial to USB converter and go the message displayed bellow: U-Boot SPL 2013.10-00015-gab7a95a (Nov 08 2013 - 16:01:27) i2c_probe: pads on bus 0 probably not configured (status=0x10) Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Could not get board ID. i2c_probe: pads on bus 0 probably not configured (status=0x10) Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Could not get board ID. Oh, that's fun.. Your board's eeprom no longer has its id.. is this a real bbb or a clone? The reason the ancient rootfs works, it assumes a bbb, boots, then programs the eeprom and initial eMMC file system. Then ships to customers.. Regards, -- Robert Nelson http://www.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/groups/opt_out.
Re: [beagleboard] Booting Issue beaglebone black
Thanks for the quick support Jason. Since, I didn't get any reply from any of your support team for last few days, I posted a new post at http://beagleboard.org/Community/Forums?place=topic%2Fbeagleboard%2FyLAbudOgAIU%2Fdiscussion And Robert has entered the discussion. Kindly take a look at it to know what I tried after this. On Wednesday, 22 January 2014 03:52:31 UTC+5:30, Jason Kridner wrote: On Tue, Jan 14, 2014 at 3:50 AM, Jay letsplayw...@gmail.com javascript: wrote: My BBB doesn't boot, I tried flashing it with factory Angstrom image available at beagleboard.org website. The 4 LEDs light up and the process is completed. But doesn't boot even after that. To see what is happening I connected my Serial to USB converter to the BBB and using Putty I saw the U-Boot message which appears like the following: U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53) timed out in wait_for_pin: I2C_STAT=0 Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Do you have any boards attached? This is an odd response. Could not get board ID. Unknown board, assuming Beaglebone LT/Black.musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Peripheral mode controller at 47401000 using PIO, IRQ 0 musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Host mode controller at 47401800 using PIO, IRQ 0 OMAP SD/MMC: 0 mmc_send_cmd : timeout: No status update reading u-boot.img reading u-boot.img U-Boot 2013.04-dirty (Jul 10 2013 - 14:02:53) I2C: ready DRAM: 512 MiB WARNING: Caches not enabled timed out in wait_for_pin: I2C_STAT=0 Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Could not get board ID. NAND: No NAND device found!!! 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - readenv() failed, using default environment musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Peripheral mode controller at 47401000 using PIO, IRQ 0 musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Host mode controller at 47401800 using PIO, IRQ 0 Net: ethaddr not set. Validating first E-fuse MAC cpsw, usb_ether Hit any key to stop autoboot: 0 gpio: pin 53 (gpio 53) value is 1 Card did not respond to voltage select! mmc0(part 0) is current device Card did not respond to voltage select! No micro SD card found, setting mmcdev to 1 mmc_send_cmd : timeout: No status update mmc1(part 0) is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 1 reading uEnv.txt 26 bytes read in 3 ms (7.8 KiB/s) Loaded environment from uEnv.txt Importing environment from mmc ... gpio: pin 55 (gpio 55) value is 1 4385024 bytes read in 768 ms (5.4 MiB/s) gpio: pin 56 (gpio 56) value is 1 24808 bytes read in 54 ms (448.2 KiB/s) Booting from mmc ... ## Booting kernel from Legacy Image at 80007fc0 ... Image Name: Angstrom/3.8.13/beaglebone Image Type: ARM Linux Kernel Image (uncompressed) Data Size:4384960 Bytes = 4.2 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK ## Flattened Device Tree blob at 80f8 Booting using the fdt blob at 0x80f8 XIP Kernel Image ... OK OK Using Device Tree in place at 80f8, end 80f890e7 Starting kernel ... Uncompressing Linux... done, booting the kernel. [1.148261] omap_i2c 44e0b000.i2c: controller timed out [1.148304] tps65217 0-0024: Failed to read INT reg [1.148322] tps65217 0-0024: Failed to probe pwr_but [2.148252] omap_i2c 44e0b000.i2c: controller timed out [3.152151] omap_i2c 44e0b000.i2c: controller timed out [3.182788] omap2_mbox_probe: platform not supported [4.246560] omap_i2c 44e0b000.i2c: controller timed out [5.254176] omap_i2c 44e0b000.i2c: controller timed out [6.767826] omap_i2c 44e0b000.i2c: controller timed out [7.779563] omap_i2c 44e0b000.i2c: controller timed out [9.293213] omap_i2c 44e0b000.i2c: controller timed out [ 10.305060] omap_i2c 44e0b000.i2c: controller timed out [ 11.818596] omap_i2c 44e0b000.i2c: controller timed out [ 12.830340] omap_i2c 44e0b000.i2c: controller timed out It again looks like something is hanging on your I2C bus besides the EEPROM. It is conceivable the board has been damaged, but I'm more suspicious of something hanging on the
Re: [beagleboard] Booting Issue beaglebone black
I don't know Gerald. There must be a team of members who will be working for support. Do you have any idea on what the issue with my board is, any idea on how to fix it. On Wednesday, 22 January 2014 19:31:11 UTC+5:30, Gerald wrote: And which support team is that? Gerald On Tue, Jan 21, 2014 at 9:25 PM, jayakar...@gmail.com javascript:wrote: Thanks for the quick support Jason. Since, I didn't get any reply from any of your support team for last few days, I posted a new post at http://beagleboard.org/Community/Forums?place=topic%2Fbeagleboard%2FyLAbudOgAIU%2Fdiscussion And Robert has entered the discussion. Kindly take a look at it to know what I tried after this. On Wednesday, 22 January 2014 03:52:31 UTC+5:30, Jason Kridner wrote: On Tue, Jan 14, 2014 at 3:50 AM, Jay letsplayw...@gmail.com wrote: My BBB doesn't boot, I tried flashing it with factory Angstrom image available at beagleboard.org website. The 4 LEDs light up and the process is completed. But doesn't boot even after that. To see what is happening I connected my Serial to USB converter to the BBB and using Putty I saw the U-Boot message which appears like the following: U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53) timed out in wait_for_pin: I2C_STAT=0 Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Do you have any boards attached? This is an odd response. Could not get board ID. Unknown board, assuming Beaglebone LT/Black.musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Peripheral mode controller at 47401000 using PIO, IRQ 0 musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Host mode controller at 47401800 using PIO, IRQ 0 OMAP SD/MMC: 0 mmc_send_cmd : timeout: No status update reading u-boot.img reading u-boot.img U-Boot 2013.04-dirty (Jul 10 2013 - 14:02:53) I2C: ready DRAM: 512 MiB WARNING: Caches not enabled timed out in wait_for_pin: I2C_STAT=0 Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Could not get board ID. NAND: No NAND device found!!! 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - readenv() failed, using default environment musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Peripheral mode controller at 47401000 using PIO, IRQ 0 musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Host mode controller at 47401800 using PIO, IRQ 0 Net: ethaddr not set. Validating first E-fuse MAC cpsw, usb_ether Hit any key to stop autoboot: 0 gpio: pin 53 (gpio 53) value is 1 Card did not respond to voltage select! mmc0(part 0) is current device Card did not respond to voltage select! No micro SD card found, setting mmcdev to 1 mmc_send_cmd : timeout: No status update mmc1(part 0) is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 1 reading uEnv.txt 26 bytes read in 3 ms (7.8 KiB/s) Loaded environment from uEnv.txt Importing environment from mmc ... gpio: pin 55 (gpio 55) value is 1 4385024 bytes read in 768 ms (5.4 MiB/s) gpio: pin 56 (gpio 56) value is 1 24808 bytes read in 54 ms (448.2 KiB/s) Booting from mmc ... ## Booting kernel from Legacy Image at 80007fc0 ... Image Name: Angstrom/3.8.13/beaglebone Image Type: ARM Linux Kernel Image (uncompressed) Data Size:4384960 Bytes = 4.2 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK ## Flattened Device Tree blob at 80f8 Booting using the fdt blob at 0x80f8 XIP Kernel Image ... OK OK Using Device Tree in place at 80f8, end 80f890e7 Starting kernel ... Uncompressing Linux... done, booting the kernel. [1.148261] omap_i2c 44e0b000.i2c: controller timed out [1.148304] tps65217 0-0024: Failed to read INT reg [1.148322] tps65217 0-0024: Failed to probe pwr_but [2.148252] omap_i2c 44e0b000.i2c: controller timed out [3.152151] omap_i2c 44e0b000.i2c: controller timed out [3.182788] omap2_mbox_probe: platform not supported [4.246560] omap_i2c 44e0b000.i2c: controller timed out [5.254176] omap_i2c 44e0b000.i2c: controller timed out [6.767826] omap_i2c 44e0b000.i2c: controller timed out [7.779563] omap_i2c 44e0b000.i2c: controller timed out [9.293213] omap_i2c 44e0b000.i2c: controller timed out [
Re: [beagleboard] Booting Issue beaglebone black
Ok Gerald. Thanks for the support. On Wednesday, 22 January 2014 20:09:58 UTC+5:30, Gerald wrote: Well, considering the fact I have no idea what the issue is, that would be rather hard to do. Gerald On Wed, Jan 22, 2014 at 8:38 AM, jayakar...@gmail.com javascript:wrote: Ok, now I understand about the support. Is there no other way or option that I can try to fix it myself. I will take a look into RMA. Thanks for the reply. On Wednesday, 22 January 2014 20:01:52 UTC+5:30, Gerald wrote: All support is community based. There is a support email address and that comes to me. I see one email per month at that address. Sounds like the board is damaged to me or the EEPROM has been overwritten.. My suggestion is that you request an RMA so that we can take a look at the board to see what is wrong.. http://www.elinux.org/Beagleboard:BeagleBoneBlack#RMA_Support Gerald On Wed, Jan 22, 2014 at 8:27 AM, jayakar...@gmail.com wrote: I don't know Gerald. There must be a team of members who will be working for support. Do you have any idea on what the issue with my board is, any idea on how to fix it. On Wednesday, 22 January 2014 19:31:11 UTC+5:30, Gerald wrote: And which support team is that? Gerald On Tue, Jan 21, 2014 at 9:25 PM, jayakar...@gmail.com wrote: Thanks for the quick support Jason. Since, I didn't get any reply from any of your support team for last few days, I posted a new post at http://beagleboard.org/Community/Forums?place=topic%2Fbeagle board%2FyLAbudOgAIU%2Fdiscussion And Robert has entered the discussion. Kindly take a look at it to know what I tried after this. On Wednesday, 22 January 2014 03:52:31 UTC+5:30, Jason Kridner wrote: On Tue, Jan 14, 2014 at 3:50 AM, Jay letsplayw...@gmail.com wrote: My BBB doesn't boot, I tried flashing it with factory Angstrom image available at beagleboard.org website. The 4 LEDs light up and the process is completed. But doesn't boot even after that. To see what is happening I connected my Serial to USB converter to the BBB and using Putty I saw the U-Boot message which appears like the following: U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53) timed out in wait_for_pin: I2C_STAT=0 Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Do you have any boards attached? This is an odd response. Could not get board ID. Unknown board, assuming Beaglebone LT/Black.musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Peripheral mode controller at 47401000 using PIO, IRQ 0 musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Host mode controller at 47401800 using PIO, IRQ 0 OMAP SD/MMC: 0 mmc_send_cmd : timeout: No status update reading u-boot.img reading u-boot.img U-Boot 2013.04-dirty (Jul 10 2013 - 14:02:53) I2C: ready DRAM: 512 MiB WARNING: Caches not enabled timed out in wait_for_pin: I2C_STAT=0 Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Could not get board ID. NAND: No NAND device found!!! 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - readenv() failed, using default environment musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Peripheral mode controller at 47401000 using PIO, IRQ 0 musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Host mode controller at 47401800 using PIO, IRQ 0 Net: ethaddr not set. Validating first E-fuse MAC cpsw, usb_ether Hit any key to stop autoboot: 0 gpio: pin 53 (gpio 53) value is 1 Card did not respond to voltage select! mmc0(part 0) is current device Card did not respond to voltage select! No micro SD card found, setting mmcdev to 1 mmc_send_cmd : timeout: No status update mmc1(part 0) is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 1 reading uEnv.txt 26 bytes read in 3 ms (7.8 KiB/s) Loaded environment from uEnv.txt Importing environment from mmc ... gpio: pin 55 (gpio 55) value is 1 4385024 bytes read in 768 ms (5.4 MiB/s) gpio: pin 56 (gpio 56) value is 1 24808 bytes read in 54 ms (448.2 KiB/s) Booting from mmc ... ## Booting kernel from Legacy Image at 80007fc0 ... Image Name: Angstrom/3.8.13/beaglebone Image Type: ARM Linux Kernel Image (uncompressed) Data Size:4384960 Bytes = 4.2 MiB Load Address: 80008000 Entry Point:
Re: [beagleboard] Unable to boot from SD Card for flashing eMMC with Debian/Ubuntu/Angstrom
I am using a 5V, 1A power supply and I have connected the Ethernet and Serial to USB converter to connectors Tx, Rx, and Gnd. On Wednesday, 22 January 2014 20:23:47 UTC+5:30, Jason Kridner wrote: On Tue, Jan 21, 2014 at 10:18 PM, jayakar...@gmail.com javascript:wrote: Can you tell me how to find out weather it is a clone or original. I don't think it is a clone. If it has the BeagleBoard.org logo, it better not be a clone! I think Robert's question was more along the lines of if you were making your own hardware. With the issue description, it really looks like a hardware issue. Because I flashed it once with the eMMC flasher image available at beagleboard website. It was working at that time. I followed the instructions to boot it from sd card with ubuntu and I tried to expand the file system, everything worked. And after that I removed sd card and tried to boot from eMMC I am stuck. I already posted my question in forum but didn't get any answer so I posted it in the way that you will look into it Robert to give a solution, the link of my previous post: http://beagleboard.org/Community/Forums?place=topic%2Fbeagleboard%2FQFp3aMdKIwQ%2Fdiscussion. I feel something else must have been done to the board. Finally yesterday I sent a mail to Jason and he has replied. I will like this post to my previous post so that Jason will also look into this in detail. And you two tech guys can help me on fixing this. Escalating to me when you don't get an answer with a link to the public post is good. I can't tell you how many times I tell people to post here FIRST! Anyway, given that you cannot read the EEPROM even from u-boot SPL, I think something must be up with the bus. I think it would give a different error if you had simply over written the EEPROM. What are you using as a power supply? What do you have connected to the board? On Wednesday, 22 January 2014 01:20:06 UTC+5:30, RobertCNelson wrote: On Tue, Jan 21, 2014 at 1:07 PM, jayakar...@gmail.com wrote: I am trying to flash my Beaglebone Black with Debain flasher image available at https://rcn-ee.net/deb/flasher/wheezy/BBB-eMMC- flasher-debian-7.3-2013-12-17-2gb.img.xz But I am not able to do it. I am holding the boot button and then turning on the power supply for the board. The LEDs doesn't turn on even after a long time as I am holding the boot button. I tried to look into what is happening with the help of Serial to USB converter and go the message displayed bellow: U-Boot SPL 2013.10-00015-gab7a95a (Nov 08 2013 - 16:01:27) i2c_probe: pads on bus 0 probably not configured (status=0x10) Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Could not get board ID. i2c_probe: pads on bus 0 probably not configured (status=0x10) Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Could not get board ID. Oh, that's fun.. Your board's eeprom no longer has its id.. is this a real bbb or a clone? The reason the ancient rootfs works, it assumes a bbb, boots, then programs the eeprom and initial eMMC file system. Then ships to customers.. Regards, -- Robert Nelson http://www.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...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
Re: [beagleboard] Unable to boot from SD Card for flashing eMMC with Debian/Ubuntu/Angstrom
I am using an adapter which gives me an output of 5V, 1A. Below are some pictures of my BBB. https://lh4.googleusercontent.com/-4DQ3mCzQca4/Ut_uhT2LdKI/BmY/pdm5ZWLGh7A/s1600/top.jpg https://lh3.googleusercontent.com/-0290kW0czLY/Ut_vJCSfAqI/Bmg/v-EYOUYqbPc/s1600/serialno.jpg https://lh5.googleusercontent.com/-MHr_BcSpXsA/Ut_vrSHU5zI/Bmo/Vg7VQ_oai9Q/s1600/bottom.jpg It has a beaglebone logo, so I think it is a original board and the vendor mentions it that it is original. The vendor is ready to check it and replace it if it has some hardware issues. Thanks for your support guys. Like I said, I had issue on the first day itself, but I re-flashed it, it worked for a week, after using ubuntu and expanding the file system in that, the issue began. On Wednesday, 22 January 2014 20:23:47 UTC+5:30, Jason Kridner wrote: On Tue, Jan 21, 2014 at 10:18 PM, jayakar...@gmail.com javascript:wrote: Can you tell me how to find out weather it is a clone or original. I don't think it is a clone. If it has the BeagleBoard.org logo, it better not be a clone! I think Robert's question was more along the lines of if you were making your own hardware. With the issue description, it really looks like a hardware issue. Because I flashed it once with the eMMC flasher image available at beagleboard website. It was working at that time. I followed the instructions to boot it from sd card with ubuntu and I tried to expand the file system, everything worked. And after that I removed sd card and tried to boot from eMMC I am stuck. I already posted my question in forum but didn't get any answer so I posted it in the way that you will look into it Robert to give a solution, the link of my previous post: http://beagleboard.org/Community/Forums?place=topic%2Fbeagleboard%2FQFp3aMdKIwQ%2Fdiscussion. I feel something else must have been done to the board. Finally yesterday I sent a mail to Jason and he has replied. I will like this post to my previous post so that Jason will also look into this in detail. And you two tech guys can help me on fixing this. Escalating to me when you don't get an answer with a link to the public post is good. I can't tell you how many times I tell people to post here FIRST! Anyway, given that you cannot read the EEPROM even from u-boot SPL, I think something must be up with the bus. I think it would give a different error if you had simply over written the EEPROM. What are you using as a power supply? What do you have connected to the board? On Wednesday, 22 January 2014 01:20:06 UTC+5:30, RobertCNelson wrote: On Tue, Jan 21, 2014 at 1:07 PM, jayakar...@gmail.com wrote: I am trying to flash my Beaglebone Black with Debain flasher image available at https://rcn-ee.net/deb/flasher/wheezy/BBB-eMMC- flasher-debian-7.3-2013-12-17-2gb.img.xz But I am not able to do it. I am holding the boot button and then turning on the power supply for the board. The LEDs doesn't turn on even after a long time as I am holding the boot button. I tried to look into what is happening with the help of Serial to USB converter and go the message displayed bellow: U-Boot SPL 2013.10-00015-gab7a95a (Nov 08 2013 - 16:01:27) i2c_probe: pads on bus 0 probably not configured (status=0x10) Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Could not get board ID. i2c_probe: pads on bus 0 probably not configured (status=0x10) Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Could not get board ID. Oh, that's fun.. Your board's eeprom no longer has its id.. is this a real bbb or a clone? The reason the ancient rootfs works, it assumes a bbb, boots, then programs the eeprom and initial eMMC file system. Then ships to customers.. Regards, -- Robert Nelson http://www.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...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
Re: [beagleboard] Unable to boot from SD Card for flashing eMMC with Debian/Ubuntu/Angstrom
The vendor of the product http://www.crazypi.com/ in India will take care of that for me. They also have a good support team like yours. Thanks for the support. On Wednesday, 22 January 2014 22:00:01 UTC+5:30, Gerald wrote: You must to go through the RMA processes before you can get it replaced. Gerald On Wed, Jan 22, 2014 at 10:25 AM, jayakar...@gmail.com javascript:wrote: I am using an adapter which gives me an output of 5V, 1A. Below are some pictures of my BBB. https://lh4.googleusercontent.com/-4DQ3mCzQca4/Ut_uhT2LdKI/BmY/pdm5ZWLGh7A/s1600/top.jpg https://lh3.googleusercontent.com/-0290kW0czLY/Ut_vJCSfAqI/Bmg/v-EYOUYqbPc/s1600/serialno.jpg https://lh5.googleusercontent.com/-MHr_BcSpXsA/Ut_vrSHU5zI/Bmo/Vg7VQ_oai9Q/s1600/bottom.jpg It has a beaglebone logo, so I think it is a original board and the vendor mentions it that it is original. The vendor is ready to check it and replace it if it has some hardware issues. Thanks for your support guys. Like I said, I had issue on the first day itself, but I re-flashed it, it worked for a week, after using ubuntu and expanding the file system in that, the issue began. On Wednesday, 22 January 2014 20:23:47 UTC+5:30, Jason Kridner wrote: On Tue, Jan 21, 2014 at 10:18 PM, jayakar...@gmail.com wrote: Can you tell me how to find out weather it is a clone or original. I don't think it is a clone. If it has the BeagleBoard.org logo, it better not be a clone! I think Robert's question was more along the lines of if you were making your own hardware. With the issue description, it really looks like a hardware issue. Because I flashed it once with the eMMC flasher image available at beagleboard website. It was working at that time. I followed the instructions to boot it from sd card with ubuntu and I tried to expand the file system, everything worked. And after that I removed sd card and tried to boot from eMMC I am stuck. I already posted my question in forum but didn't get any answer so I posted it in the way that you will look into it Robert to give a solution, the link of my previous post: http://beagleboard.org/Community/Forums?place=topic% 2Fbeagleboard%2FQFp3aMdKIwQ%2Fdiscussion . I feel something else must have been done to the board. Finally yesterday I sent a mail to Jason and he has replied. I will like this post to my previous post so that Jason will also look into this in detail. And you two tech guys can help me on fixing this. Escalating to me when you don't get an answer with a link to the public post is good. I can't tell you how many times I tell people to post here FIRST! Anyway, given that you cannot read the EEPROM even from u-boot SPL, I think something must be up with the bus. I think it would give a different error if you had simply over written the EEPROM. What are you using as a power supply? What do you have connected to the board? On Wednesday, 22 January 2014 01:20:06 UTC+5:30, RobertCNelson wrote: On Tue, Jan 21, 2014 at 1:07 PM, jayakar...@gmail.com wrote: I am trying to flash my Beaglebone Black with Debain flasher image available at https://rcn-ee.net/deb/flasher/wheezy/BBB-eMMC-flasher- debian-7.3-2013-12-17-2gb.img.xz But I am not able to do it. I am holding the boot button and then turning on the power supply for the board. The LEDs doesn't turn on even after a long time as I am holding the boot button. I tried to look into what is happening with the help of Serial to USB converter and go the message displayed bellow: U-Boot SPL 2013.10-00015-gab7a95a (Nov 08 2013 - 16:01:27) i2c_probe: pads on bus 0 probably not configured (status=0x10) Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Could not get board ID. i2c_probe: pads on bus 0 probably not configured (status=0x10) Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Could not get board ID. Oh, that's fun.. Your board's eeprom no longer has its id.. is this a real bbb or a clone? The reason the ancient rootfs works, it assumes a bbb, boots, then programs the eeprom and initial eMMC file system. Then ships to customers.. Regards, -- Robert Nelson http://www.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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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
[beagleboard] Unable to boot from SD Card for flashing eMMC with Debian/Ubuntu/Angstrom
I am trying to flash my Beaglebone Black with Debain flasher image available at https://rcn-ee.net/deb/flasher/wheezy/BBB-eMMC-flasher-debian-7.3-2013-12-17-2gb.img.xz But I am not able to do it. I am holding the boot button and then turning on the power supply for the board. The LEDs doesn't turn on even after a long time as I am holding the boot button. I tried to look into what is happening with the help of Serial to USB converter and go the message displayed bellow: U-Boot SPL 2013.10-00015-gab7a95a (Nov 08 2013 - 16:01:27) i2c_probe: pads on bus 0 probably not configured (status=0x10) Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Could not get board ID. i2c_probe: pads on bus 0 probably not configured (status=0x10) Could not probe the EEPROM; something fundamentally wrong on the I2C bus. Could not get board ID. Unknown board, cannot configure pinmux.### ERROR ### Please RESET the board ### Does anyone know how to solve this issue. This is not the case only with Debian image. I am not able to boot from any image. I can only run the image Angstrom Distribution (BeagleBone, BeagleBone Black - 4GB SD) 2013-06-20https://s3.amazonaws.com/angstrom/demo/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img.xz available at http://beagleboard.org/latest-images. This image also doesn't boot up, if I press the boot button. It boots up automatically if I insert the sd card with the image in the beaglebone black and give power supply, without me pressing the boot button. And my Beaglebone black doesn't boot from eMMC also. -- 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/groups/opt_out.
