These lines in the .build file should start the SD and eMMC:
#######################################################################
## MMC/SD driver
#######################################################################
display_msg Starting MMC/SD driver...
# MMC 0 pio
# devb-sdmmc-j5_generic sdio
addr=0x48060000,irq=64,dma=25,dma=24,dma=128,dma=32,verbose=3,bs=nocd:nowp
cam pio,cache,pnp,async blk cache=8M disk name=sd
# MMC 0 dma
devb-sdmmc-j5_generic sdio
addr=0x48060000,irq=64,dma=25,dma=24,dma=128,dma=32,verbose=3,bs=nocd:nowp
cam cache,pnp,async blk cache=8M disk name=sd
# eMMC 0 dma
devb-sdmmc-j5_generic sdio
addr=0x481D8000,irq=28,verbose=3,dma=3,dma=2,dma=160,dma=32,bs=emmc,bw=4
cam quiet,cache blk rw,cache=2M disk name=emmc
They should show up as /dev/hd0 and /dev/hd1. I am using a different
driver. That could be a QNX 6.5 thing. Try typing 'sloginfo' to see if that
gives you any clues. Of course, if they didn't start, the devices won't
show up as evidenced by your original post:
*Starting MMC/SD driver...*
*Unable to start "devb-sdmmc-j5_generic" (2)*
*Unable to start "devb-sdmmc-j5_generic" (2)*
The SD card is usually split into 2 partitions. A small bootable FAT32
partition to hold MLO, u-boot.bin and the QNX image. The other partition is
usually set to type 131 for the QNX filesystem. I am booting from the eMMC.
Here is what fdisk shows for eMMC:
FDISK
Ignore Next Prev Change Delete Boot Unboot Restore Loader Save Quit
_____OS_____ Start End ______Number_____ Size
Boot
name type Cylinder Cylinder Cylinders Blocks
--> 1. FAT32 ( 11) 0 511 512 1048544 511 MB *
2. Linux (131) 512 7439 6928 14188544 6928 MB
3. ______ (___) _ _ _ _ _____
4. ______ (___) _ _ _ _ _____
Choose a partition by typing the partition number OR moving the pointer
with the UP/DOWN arrows.
Then, choose one of the actions on the top line of the screen.
Drive : /dev/hd0 Config: 64 Heads
Size : 7440 Mbytes 32 Sectors/track
Loader: Unknown 7440 Cylinders
Blocks: 15237120 512 Block Size
Last cylinder is 7439
On Tuesday, March 1, 2016 at 3:00:18 PM UTC-7, Steven Hartmann wrote:
>
> I hope there is someone here successfully using QNX on the BBB. I am
> currently doing a QNX evaluation and am having trouble with the BBB BSP. I
> am using the BSP_ti-am335x-beaglebone_br-660_be-660_SVN797070_JBN574.zip
> BSP. The package comes with a pre-built image, which boots up fine. I
> have been able to do a few test programs with it, but now I need to modify
> the BSP to change which features are used. The first step in doing this
> was to just recompile the BSP to make sure I can recreate the precompiled
> version. The build goes fine and creates an image. I can boot off the
> image, but it gives a lot of errors:
>
> U-Boot# fatload mmc 0 81000000 ifs-ti-am335x-beaglebone.bin
> reading ifs-ti-am335x-beaglebone.bin
> 5794620 bytes read in 657 ms (8.4 MiB/s)
> U-Boot# go 81000000
> ## Starting application at 0x81000000 ...
>
> __________Board ID__________
> header: ee3355aa
> name: A335BNLT
> ____________________________
> BeagleBone Black detected
>
> VFPv3: fpsid=410330c3
> coproc_attach(10): attach fe08a3fc (fe08ad24)
> coproc_attach(11): attach fe08a3fc (fe08ad24)
> Welcome to QNX Neutrino 6.6.0 on the Texas Instruments AM335x BeagleBone
> (ARMv7 Cortex-A8 core) - Board
> Unable to start "devc-seromap" (2)
> Unable to access "/dev/ser1" (2)
> Unable to access "/dev/ser1" (2)
> Starting MMC/SD driver...
> Unable to start "devb-sdmmc-j5_generic" (2)
> Unable to start "devb-sdmmc-j5_generic" (2)
> starting I2C driver...
> Unable to start "i2c-omap35xx-j5" (2)
> Unable to access "/dev/i2c0" (2)
> starting WDT reset utility...
> Unable to start "dm814x-wdtkick" (2)
> starting Board ID driver...
> Unable to start "am335x-boardid" (2)
> Unable to access "/dev/bdid" (2)
> Setting OS Clock from on-board RTC
> Unable to start "rtc" (2)
> Sat Jan 01 00:00:15 GMT 2000
> Starting USB OTG Host driver...
> Starting SPI driver...
> Unable to start "spi-master" (2)
> Starting network driver...
> starting leds driver...
> Unable to start "am335x-leds" (2)
> Unable to access "/dev/leds" (2)
> Setting environment variables...
> done.
> Starting Screen Graphics...
> done.
> Starting HDMI Audio driver...
> Unable to access /dev/snd/pcmC0D1p
> ksh: No controlling tty (open /dev/tty: No such device or address)
> ksh: warning: won't have full job control
>
>
> All of the software that reports "unable to start" does not have execute
> permissions. When I tried to add execute permissions by hand, it said the
> file did not exist.
>
> My build host is linux mint.
>
> Thanks!
>
--
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/d/optout.
