Earlier I said: When I get to your line mount /dev/sda1 /mnt/card I get the response mount point /mnt/card does not exist
=-=-=-=-=-=-==-=-=-=-=--==-=- Now I continue: I tried using BEAGLE_BONE as the name (that's the name that my 8GB SD card came with, pre-formatted from Adafruit) but no help. I then did a bit of digging and discovered that it was my responsibility to build (and name) a directory myself, so I created /mnt/SDcard and where the sample code referred to "card" I used my "SDcard" name, and the problem was solved. I'm new at this and there IS a lot to learn. Unfortunately, this success just exposed a bunch of other problems that I'm sure that I'm hitting just because of my inexperience. Right now, my system won't boot (the lights are on but PuTTY can't see the system) WITH my SD card in at power-on. Everything works fine if I boot from the on-board 4 GB eMMC without the SD card in pace. The card looks (in Windows) to have the same files in it as it did after I used it to capture the Win32 DiskImager download that allowed a successful flash of the eMMC, including the reduced size that I am trying to fix in this process (8 GB total space dropped to a little under 100 MB total space during the DiskImager download according to Windows - properties) There were a couple of deviations that I had from the sample code: The sample code said 'changed type to "c"' ... there was no type c, but there was a command option "c" (that I used) "compatible mode: 'dos' or 'nondos' (default)" so I moved to the 'dos' mode for partition 1. For the second partition, I did NOT use the "c" command on this second partition. I did install it as a Primary partition though as was suggested (should it have been an ext partition? I was allowed a partition size of 2048 to 15,523,839 for partition 1 and I used 2048 as a starting sector, and +1M as recommended to get the end sector. For partition 2, I was surprised to see my size choice start partition sectors limited to 62 - 15,523,839 with a default of 62 for a start. Shouldn't the 1024 bites per sector have taken the first partition from 2048 start to 3072 end? I accepted the default 62. The resulting available end sector range was then shown as 62 - 2047. Where did the end sector choice of 15,523,839 go to? I tried for it, but nothing higher than 2047 would work. I'm wondering if I should reformat the SD card under windows to get it back to its 8GB size and then retry the Debian fdisk approach. For now it's back to thinking and reading to figure out a rational next step. Hmmmm. Maybe I'll try something. Ok the following gets me a successful boot with the card inserted, and a full load of memory on the card. But I don't think that I quite have access to the card yet. Here's what I did (sort of) all at once (and yes, I do know that I'm only supposed to change one thing at a time between tests.) Partition 1 is Primary 2048 to +1M, just like before, but no more type "c" (command c) so it's NOT dos ... this lets me get a bigger Partition 2. Partition gets a start at 4096 (default) and takes 15,523,839 as the end sector (also now the default). I left the line "mkfs -V -t ext4 -j -L BoneData /dev/sda2" as it was although some reading I did says that the default for mkfs is ext2 rather than the ext4 in the sample. I'm stopping at this point as there are just too many variables to play with. If someone can point to the problems and say you did this one right and this other one wrong, then I can probably muddle my through from there. Time to get back to my reading. I'll sure be happy once I get some of the basics under control. Bob =-=-=-=-=-=-=-=-=-=-=--= On Wednesday, January 7, 2015 12:31:22 AM UTC-8, rjc2827 wrote: > > When I get to your line > mount /dev/sda1 /mnt/card > > I get the response > mount point /mnt/card does not exist > > Bob > > =-=-=-=-=-=-=-=-=-=-=- > > On Thursday, June 27, 2013 1:03:34 PM UTC-7, William C Bonner wrote: >> >> I was just going to mention my results along the same lines. I put my SD >> card in a USB adapter so it showed up as /dev/sda and then ran the >> following commands: >> >> fdisk /dev/sda >> (Deleted all existing partitions with the "d" command, created a new >> primary partition with the "n" command, default initial location, +1M size, >> changed type to "c". Created second primary partition that used the rest of >> the drive. "w" to exit and save changes.) >> mkfs -t vfat -F 32 -n BoneBoot /dev/sda1 >> mkfs -V -t ext4 -j -L BoneData /dev/sda2 >> mount /dev/sda1 /mnt/card >> (create /mnt/card/uEnv.txt with the lines >> mmcdev=1 >> bootpart=1:2 >> mmcroot=/dev/mmcblk1p2 >> optargs=quiet >> And then shutdown my board, put the card in the microSD slot, and power >> on. The board booted from the internal mmc, and the partitions were >> automounted under the /media directory.) >> >> Here's part of the df output after rebooting. >> Filesystem 1K-blocks Used Available Use% Mounted on >> /dev/mmcblk0p1 992 1 991 1% /media/BoneBoot >> /dev/mmcblk1p1 71133 55239 15895 78% /media/BEAGLEBONE >> /dev/mmcblk0p2 1918992 2928 1816916 1% /media/BoneData >> >> >> >> >> On Thu, Jun 27, 2013 at 12:47 PM, Tommy Snyder <[email protected]> >> wrote: >> >>> Never mind. I got the answer to my question. Sorry for the confusion. >>> >>> For anyone else not clear after reading this this is how I was able to >>> use a uSD card in the uSD card slot as extra storage while booting Angstrom >>> from the eMMC >>> >>> Insert the uSD into a USB hub connected to the BBB using a usb adapter >>> Open up the Disk Utility in Applications > System Tools > Disk Utility >>> Unmount the uSD >>> Format the drive >>> Click add a partition and make it of type FAT, name it and size it >>> however you want >>> After it has been formatted and partitioned mount the FAT 32 partition >>> you just made >>> Open it in file explorer and Right Click > Create Document >>> Name it uEnv.txt >>> Add the following lines to uEnv.txt: >>> >>> mmcdev=1 >>> bootpart=1:2 >>> mmcroot=/dev/mmcblk1p2 ro >>> optargs=quiet >>> >>> >>> Then power down your BBB >>> Remove the uSD from the hub and insert it into the uSD slot on the BBB >>> Power on the BBB and there should be a mounted storage device with the >>> name you gave it >>> >>> >>> >>> >>> On Thursday, June 27, 2013 1:49:18 PM UTC-5, William C Bonner wrote: >>> >>>> The important thing the script does is to create and format the first >>>> partition as FAT32. I am not positive as to the size requirements of the >>>> first partition, or the head/sector/cylinders that's setup in the >>>> translation. I know that the entire drive is accessed in LBA mode. >>>> >>>> I'm happy that I've now got my SD card in the reader and not taking up >>>> space on the USB hub. My uEnv.txt file is: >>>> mmcdev=1 >>>> bootpart=1:2 >>>> mmcroot=/dev/mmcblk1p2 >>>> optargs=quiet >>>> >>>> I've formatted the remainder of the drive with the command "mkfs -V -t >>>> ext4 -j -L /home /dev/sda2" but it's automounting the partition at >>>> /media/_home instead of the /home location I was hoping it would be >>>> mounted. Without manually editing /etc/fstab, is there a way to have it >>>> mounted at /home? >>>> >>>> (Obviously the /dev/sda2 location was when the card was in the USB >>>> adapter, now it would be /dev/mmcblk0p2) >>>> >>>> I've got a spare 2GB microSD sitting around. I'll test and see how >>>> simple it is to make the correct formatted card in a few minutes... >>>> >>>> >>>> On Thu, Jun 27, 2013 at 11:35 AM, Tommy Snyder <[email protected]> >>>> wrote: >>>> >>>>> To make sure I'm understanding correctly, you need to run the >>>>> mkcard.sh script on this >>>>> <http://dev.gentoo.org/~armin76/arm/beagleboneblack/install_emmc.xml#expand> >>>>> >>>>> page right? In order to format the microSD to have the correct format? >>>>> >>>>> There seems to be a gap of information here. It sounds like I can take >>>>> any old microSD and just put that text file in it and plug it into the >>>>> BBB >>>>> and the BBB will boot. I've tried several variations and I keep getting >>>>> stuck at 3 solid LED's >>>>> >>>>> Tommy >>>>> >>>>> >>>>> On Thursday, June 27, 2013 12:11:20 PM UTC-5, William Hermans wrote: >>>>> >>>>>> Depends on what you want to do. If all you want to do is boot from >>>>>> the emmc, and have access to the SD card( with SD card inserted at boot >>>>>> ), >>>>>> then yes, that is all you need. >>>>>> >>>>>> >>>>>> On Thu, Jun 27, 2013 at 9:37 AM, Tommy Snyder <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Is that ALL we need to have on the microSD? or do we need other >>>>>>> files on there as well? >>>>>>> >>>>>>> >>>>>>> On Wednesday, June 26, 2013 9:35:07 PM UTC-5, William Hermans wrote: >>>>>>> >>>>>>>> Grr, sorry for the multiposts kind of mufti tasking here. Sorry >>>>>>>> guys / Gals. >>>>>>>> >>>>>>>> mmcdev=1 >>>>>>>> bootpart=1:2 >>>>>>>> mmcroot=/dev/mmcblk1p2 ro >>>>>>>> >>>>>>>> That needs to be in a uEnv.txt file on the SD card. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Jun 26, 2013 at 7:33 PM, William Hermans <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Anyhow to boot from the emmc you need a uEnv >>>>>>>>> .txt file that looks something like this. >>>>>>>>> >>>>>>>>> >>>>>>>>> mmcdev=1 >>>>>>>>> bootpart=1:2 >>>>>>>>> mmcroot=/dev/mmcblk1p2 ro >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Jun 26, 2013 at 7:31 PM, William Hermans <[email protected] >>>>>>>>> > wrote: >>>>>>>>> >>>>>>>>>> What is the contents of your current uEnv.txt file ? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Jun 26, 2013 at 12:07 PM, William C Bonner < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> I spent a huge amount of time working with the original >>>>>>>>>>> BeagleBoard a few years ago, but have not been working with it >>>>>>>>>>> recently, >>>>>>>>>>> and not had a BBB until this past week. >>>>>>>>>>> >>>>>>>>>>> I'm trying to use a microsd card as extra storage while running >>>>>>>>>>> on my beaglebone black. I thought I'd followed the correct >>>>>>>>>>> directions to >>>>>>>>>>> get the memory card formatted and configured correctly, but when I >>>>>>>>>>> power on >>>>>>>>>>> the BBB with the sd card inserted, all I get is solid LEDS. >>>>>>>>>>> >>>>>>>>>>> Now I've got the SDCard in a usb adapter and mounted. I can see >>>>>>>>>>> that the built in flash is /dev/mmcblk0. I've added lines to my >>>>>>>>>>> uEnv.txt >>>>>>>>>>> file according to http://dev.gentoo.org/~armi >>>>>>>>>>> n76/arm/beagleboneblack/install_emmc.xml#expand in hopes of >>>>>>>>>>> getting the device to boot but am not having any luck. I think I'm >>>>>>>>>>> confused as to the specific parameters, and the processor doing >>>>>>>>>>> somethign >>>>>>>>>>> slightly different depending on if it sees the removable card. >>>>>>>>>>> >>>>>>>>>>> What I really want is for the board to boot from its internal >>>>>>>>>>> storage, and mount the second partition from the microsd card over >>>>>>>>>>> /home/ >>>>>>>>>>> so that I can use all of that space for user storage. >>>>>>>>>>> >>>>>>>>>>> I copied the entire contents of /dev/mmcblk0p1 to the FAT boot >>>>>>>>>>> partition on the memory card, and then modified the uEnv.txt file >>>>>>>>>>> on the >>>>>>>>>>> memory card. Should that work? >>>>>>>>>>> >>>>>>>>>>> Since it didn't work, can someone tell me if I was close, and >>>>>>>>>>> should have been able to fix it simply by using the correct options >>>>>>>>>>> in the >>>>>>>>>>> uEnv.txt file? >>>>>>>>>>> >>>>>>>>>>> root@beaglebone:/media/BEAGLEBONE_# fdisk -l >>>>>>>>>>> >>>>>>>>>>> Disk /dev/mmcblk0: 1920 MB, 1920991232 bytes >>>>>>>>>>> 255 heads, 63 sectors/track, 233 cylinders, total 3751936 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: 0x00000000 >>>>>>>>>>> >>>>>>>>>>> Device Boot Start End Blocks Id >>>>>>>>>>> System >>>>>>>>>>> /dev/mmcblk0p1 * 63 144584 72261 c W95 >>>>>>>>>>> FAT32 (LBA) >>>>>>>>>>> /dev/mmcblk0p2 144585 3743144 1799280 83 >>>>>>>>>>> Linux >>>>>>>>>>> >>>>>>>>>>> Disk /dev/mmcblk0boot1: 1 MB, 1048576 bytes >>>>>>>>>>> 4 heads, 16 sectors/track, 32 cylinders, total 2048 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 /dev/mmcblk0boot0: 1 MB, 1048576 bytes >>>>>>>>>>> 4 heads, 16 sectors/track, 32 cylinders, total 2048 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 /dev/sda: 31.9 GB, 31914983424 bytes >>>>>>>>>>> 64 heads, 32 sectors/track, 30436 cylinders, total 62333952 >>>>>>>>>>> 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: 0x00000000 >>>>>>>>>>> >>>>>>>>>>> Device Boot Start End Blocks Id System >>>>>>>>>>> /dev/sda1 * 63 144584 72261 c W95 >>>>>>>>>>> FAT32 (LBA) >>>>>>>>>>> /dev/sda2 144585 62333951 31094683+ 83 Linux >>>>>>>>>>> root@beaglebone:/media/BEAGLEBONE_# cat >>>>>>>>>>> /media/BEAGLEBONE_/uEnv.txt >>>>>>>>>>> bootpart=1:2 >>>>>>>>>>> mmcroot=/dev/mmcblk1p2 >>>>>>>>>>> optargs=quiet >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Sat, May 25, 2013 at 9:59 PM, <[email protected]> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> This page by Armin76 explains it quite well, and even provides >>>>>>>>>>>> a shell script to set up an sd card to be used as external storage >>>>>>>>>>>> (basically, when the SD card is inserted, it shows up as mmc0, >>>>>>>>>>>> which is >>>>>>>>>>>> what uBoot tries to boot from, so you have to give it some >>>>>>>>>>>> instructions in >>>>>>>>>>>> a uEnv.txt to tell it to boot from the internal memory instead) >>>>>>>>>>>> >>>>>>>>>>>> http://dev.gentoo.org/~armin76/arm/beagleboneblack/install_e >>>>>>>>>>>> mmc.xml#expand >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Saturday, May 11, 2013 7:41:40 PM UTC-4, William Hermans >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> look into the uEnv.txt parameters. presumably even if you want >>>>>>>>>>>>> to boot from eMMC the uEnv.txt file has to be present on the SD >>>>>>>>>>>>> card, and >>>>>>>>>>>>> with the correct parameters in it. If you google beaglebone black >>>>>>>>>>>>> + >>>>>>>>>>>>> uEnv.txt, you should land on the same wiki page i found a week or >>>>>>>>>>>>> so ago. >>>>>>>>>>>>> It seemed pretty informative. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Sat, May 11, 2013 at 4:33 PM, <[email protected]> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> All, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Can someone point me in the right direction. >>>>>>>>>>>>>> >>>>>>>>>>>>>> I've updated the Beagle Black via the SD card, now I want to >>>>>>>>>>>>>> be able to use an blank SD card for extra storage. If I just >>>>>>>>>>>>>> format a card >>>>>>>>>>>>>> and put it in the slot, the four LEDs light up and that's it. >>>>>>>>>>>>>> >>>>>>>>>>>>>> What do I need to do to use a blank card and mount it. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Many thanks, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Trefor >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> 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]. >>>>>>>>>>>>>> >>>>>>>>>>>>>> For more options, visit https://groups.google.com/grou >>>>>>>>>>>>>> ps/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 [email protected]. >>>>>>>>>>>> >>>>>>>>>>>> For more options, visit https://groups.google.com/grou >>>>>>>>>>>> ps/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 [email protected]. >>>>>>>>>>> >>>>>>>>>>> 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 [email protected]. >>>>>>> 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 [email protected]. >>>>> 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 [email protected]. >>> 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
