Hi Ali.. No, none of the kernel 3.2.0 based images will be able to see the eMMC. But, lateron I was able to support it with that old kernel by a patch I found online was originally made for Android JB. Supporting the eMMC is easy; not more than 10 lines. You can even extract it from new versions of board-am33x file.
With that update yes, I can see two mmc blocks under the /dev/.. one for the eMMC and the other for the SDCard.. Now I have the beaglebone black booting up from the eMMC without any sdcards with the capacitive 7' LCD fully functional on ubuntu 12.10+LXDE, and can access the sdcard as an external storage. Beaglebone is fun, please enjoy it. Best regards Mahammad On Sun, Jan 12, 2014 at 7:19 AM, Ali J. Ghandour <[email protected]> wrote: > Hi Mahammad, > > If you try "ls -lt /dev/", can you find *mmcblk1?* > > Regards, > > Ali J. Ghandour > www.alighandour.org > > “Intellectual growth should commence at birth and cease only at death.” > > > On 8 January 2014 10:42, Mahammad Mostafa <[email protected]> wrote: > >> Hi Ali.. >> >> I was using ubuntu 12.10: ubuntu-12.10-console-armhf-2013-04-26 >> Kernel is 3.2.0 that comes with chipsee capacitive 7"lcd. It is based on >> the TI sdk with a few changes to support the LCD on BBB. >> >> Best Regards >> >> Mahammad >> >> >> >> >> On Wed, Jan 8, 2014 at 8:38 AM, Ali <[email protected]> wrote: >> >>> Hi Mahammad, >>> >>> Which 3.2 kernel you are using? And what version of Ubuntu? >>> >>> >>> On Tuesday, January 7, 2014 10:00:23 PM UTC+2, Mahammad wrote: >>>> >>>> Hi There... >>>> >>>> Did anyone succeed running 3.2 from the eMMC on BBB? >>>> >>>> I managed to run ubuntu with 3.2 on BBB but from sdcard only.. it can't >>>> see the eMMC.. not even as a storage. 'lsblk' only shows the sdcard. Any >>>> idea how to support the eMMC under kernel 3.2? I feel it could be a >>>> backport effort to the eMMC driver... any help will be appreciated. >>>> >>>> Best Regards >>>> >>>> Mahammad >>>> >>>> >>>> On Thursday, December 12, 2013 8:34:23 PM UTC+2, Ali wrote: >>>>> >>>>> I have noticed that your are not supporting 3.2 kernel. >>>>> But Maxim mentioned that he was able to run your 3.2 kernel on the BBB. >>>>> That's why I was asking Maxim to provide me with the patched 3.2 >>>>> kernel that he was able to run on the BBB. >>>>> >>>>> On Thursday, December 12, 2013 8:26:51 PM UTC+2, RobertCNelson wrote: >>>>>> >>>>>> On Thu, Dec 12, 2013 at 12:24 PM, Ali <[email protected]> wrote: >>>>>> > Thanks Robert and Maxim. >>>>>> > I started again with a fresh git clone and was able to compile a >>>>>> new 3.2 >>>>>> > kernel. >>>>>> > >>>>>> > When I tried booting the compiled kernel on a BBB, it hits the >>>>>> following >>>>>> > error related to EEProm Configuration Option variable: >>>>>> > >>>>>> > ............................. >>>>>> > No daughter card found >>>>>> > [ 1.103912] at24 1-0050: 32768 byte 24c256 EEPROM, writable, 64 >>>>>> > bytes/write >>>>>> > [ 1.119110] Board config.name: >>>>>> > A335BNLT0A5C3513BBBK0428�������������������������������� >>>>>> > [ 1.127502] Board name: A335BNLT >>>>>> > [ 1.130889] Board version: 0A5C >>>>>> > [ 1.134155] SKU: ������ >>>>>> > [ 1.136718] The error message above indicates that there is an >>>>>> issue with >>>>>> > [ 1.136718] the EEPROM or the EEPROM contents. After verifying >>>>>> the >>>>>> > EEPROM >>>>>> > [ 1.136718] contents, if any, refer to the am335x_evm_setup >>>>>> function in >>>>>> > the >>>>>> > [ 1.136718] arch/arm/mach-omap2/board-am335xevm.c file to >>>>>> modify the >>>>>> > board >>>>>> > [ 1.136749] initialization code to match the hardware >>>>>> configuration >>>>>> > ............................. >>>>>> >>>>>> Laughs, no it's working perfectly, ! >>>>>> >>>>>> As previous stated, " I never added BBB support to my 3.2 based >>>>>> kernel, I consider 3.2 long dead." >>>>>> >>>>>> AKA: DO NOT USE my 3.2 branch on the BBB, use 3.8... >>>>>> >>>>>> 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 a topic in the >>> Google Groups "BeagleBoard" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/beagleboard/H2R8dCj8xyI/unsubscribe. >>> To unsubscribe from this group and all its topics, 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 a topic in the >> Google Groups "BeagleBoard" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/beagleboard/H2R8dCj8xyI/unsubscribe. >> To unsubscribe from this group and all its topics, 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 a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/H2R8dCj8xyI/unsubscribe. > To unsubscribe from this group and all its topics, 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.
