This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM8148 - NFS boot, problem with setting up settings

Other Parts Discussed in Thread: PCF8575, PMP

Hello,

I tried and I want to work on TMDXEVM8148 but I'm stuck at the beginning. I read in detail safely 1000 times SDG but EVM refusing to cooperate :( I tried some suggestions on this forum but to no avail.

Demo examples works fine (more or less) but when I want to run "helloworld" refuses. In my opinion the problem is in NFS boot. Target and host (Linux Ubuntu, dual OS with win7, won't work in VM) are connected via a serial cable and over switcher (although I think there is the problem so I directly connect via network cable). NAND is ON, BOOT MODE SEL (S1): 111010010000, and I tried with 111010000000


I'm new in this so please help me step-by-step :)

Here is report from boot:

Welcome to minicom 2.4

OPTIONS: I18n

Compiled on Jan 25 2010, 06:49:09.

Port /dev/ttyS0

Press CTRL-A Z for help on special keys

U-Boot 2010.06 (Sep 08 2011 - 16:14:46)

TI8148-GP rev 2.1

ARM clk: 600MHz

DDR clk: 400MHz

DRAM: 2 GiB

Using default environment

The 2nd stage U-Boot will now be auto-loaded

Please do not interrupt the countdown till TI8148_EVM prompt if 2nd stage is already flashed

Hit any key to stop autoboot: 0

mmc1 is available

reading u-boot.bin

179200 bytes read

## Starting application at 0x80800000 ...

U-Boot 2010.06 (Sep 08 2011 - 16:10:13)

TI8148-GP rev 2.1

ARM clk: 600MHz

DDR clk: 400MHz

I2C:   ready

DRAM: 2 GiB

NAND: HW ECC Hamming Code selected

256 MiB

*** Warning - bad CRC or NAND, using default environment

                          .:;rrr;;.                  

                   ,5#@@@@#####@@@@@@#2,            

                 ,A@@@hi;;;r5;;;;r;rrSG@@@A,          

               r@@#i;:;s222hG;rrsrrrrrr;ri#@@r        

             :@@hr:r;SG3ssrr2r;rrsrsrsrsrr;rh@@:      

           B@H;;rr;3Hs;rrr;sr;;rrsrsrsrsrsr;;H@B    

           @@s:rrs;5#;;rrrr;r#@H:;;rrsrsrsrsrr:s@@    

         @@;;srs&X#9;r;r;;,2@@@rrr:;;rrsrsrsrr;;@@  

         @@;;rrsrrs@MB#@@@@@###@@@@@@#rsrsrsrsrr;;@@  

       G@r;rrsrsr;#X;SX25Ss#@@#M@#9H9rrsrsrsrsrs;r@G

       @9:srsrsrs;2@;:;;:.X@@@@@H::;rrsrsrsrsrsrr:3@

       X@;rrsrsrsrr;XAi;;:&@@#@Bs:rrsrsrsrsrsrsrsrr;@X

       @#;rsrsrsrsrr;r2ir@@@###::rrsrsrsrsrsrsrsrsr:@@

       @A:rrsrsrsrr;:2@29@@M@@@;:;rrrrsrsrsrsrsrsrs;H@

      @&;rsrsrsrr;A@@@@@@###@@@s::;:;;rrsrsrsrsrsr;G@

       @#:rrsrsrsr;G@5Hr25@@@#@@@#9XG9s:rrrrsrsrsrs:#@

       M@;rsrsrsrs;r@&#;::S@@@@@@@M@@@@Grr:;rsrsrsr;@#

       :@s;rsrsrsrr:M#Msrr;;&#@@@@@@@@@@H@@5;rsrsr;s@,

       @@:rrsrsrsr;S@rrrsr;:;r3MH@@#@M5,S@@irrsrr:@@

         @A:rrsrsrsrrrrrsrsrrr;::;@##@r:;rH@h;srr:H@  

         ;@9:rrsrsrsrrrsrsrsrsr;,S@Hi@i:;s;MX;rr:h@;  

         r@B:rrrrsrsrsrsrsrr;;sA@#i,i@h;r;S5;r:H@r  

           ,@@r;rrrsrsrsrsrr;2BM3r:;r:G@:rrr;;r@@,    

             B@Mr;rrrrsrsrsr@@S;;;rrr:5M;rr;rM@H      

             .@@@i;;rrrrsrs2i;rrrrr;r@M:;i@@@.      

               .A@@#5r;;;r;;;rrr;r:r#AsM@@H.        

                   ;&@@@@MhXS5i5SX9B@@@@G;            

                       :ihM#@@@@@##hs,                

Net:   <ethaddr> not set. Reading from E-fuse

Detected MACID:40:5f:c2:26:46:52

cpsw

Hit any key to stop autoboot: 0

mmc1 is available

reading boot.scr

300 bytes read

Running bootscript from MMC/SD to set the ENV...

## Executing script at 80900000

reading uImage

2457320 bytes read

## Booting kernel from Legacy Image at 80009000 ...

   Image Name:   Arago/2.6.37-psp04.01.00.05/dm81

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:   2457256 Bytes = 2.3 MiB

   Load Address: 80008000

   Entry Point: 80008000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Linux version 2.6.37 (x0029463@swubn01) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Thu Sep 8 16:12:47 IST 2011

CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f

CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache

Machine: ti8148evm

vram size = 52428800 at 0

reserved size = 52428800 at 0

FB: Reserving 52428800 bytes SDRAM for VRAM

Memory policy: ECC disabled, Data cache writeback

OMAP chip is TI8148 2.0

Built 1 zonelists in Zone order, mobility grouping on. Total pages: 52224

Kernel command line: console=ttyO0,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=256M earlyprink notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfb.vram=0:16M,1:16M,2:6M ip

=off noinitrd

PID hash table entries: 1024 (order: 0, 4096 bytes)

Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

Memory: 206MB = 206MB total

Memory: 203408k/203408k available, 58736k reserved, 0K highmem

Virtual kernel memory layout:

   vector : 0xffff0000 - 0xffff1000   (   4 kB)

   fixmap : 0xfff00000 - 0xfffe0000   ( 896 kB)

   DMA     : 0xffc00000 - 0xffe00000   (   2 MB)

   vmalloc : 0xd0800000 - 0xf8000000   ( 632 MB)

   lowmem : 0xc0000000 - 0xd0000000   ( 256 MB)

   modules : 0xbf000000 - 0xc0000000   ( 16 MB)

     .init : 0xc0008000 - 0xc0037000   ( 188 kB)

     .text : 0xc0037000 - 0xc04a6000   (4540 kB)

     .data : 0xc04a6000 - 0xc04e9400   ( 269 kB)

SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

NR_IRQS:375

IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts

Total of 128 interrupts on 1 active controller

GPMC revision 6.0

Trying to install interrupt handler for IRQ368

Trying to install interrupt handler for IRQ369

Trying to install interrupt handler for IRQ370

Trying to install interrupt handler for IRQ371

Trying to install interrupt handler for IRQ372

Trying to install interrupt handler for IRQ373

Trying to install interrupt handler for IRQ374

Trying to install type control for IRQ375

Trying to set irq flags for IRQ375

OMAP clockevent source: GPTIMER1 at 20000000 Hz

Console: colour dummy device 80x30

Calibrating delay loop... 599.65 BogoMIPS (lpj=2998272)

pid_max: default: 32768 minimum: 301

Security Framework initialized

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

devtmpfs: initialized

omap_voltage_early_init: voltage driver support not added

regulator: core version 0.5

regulator: dummy:

NET: Registered protocol family 16

OMAP GPIO hardware version 0.1

OMAP GPIO hardware version 0.1

OMAP GPIO hardware version 0.1

OMAP GPIO hardware version 0.1

omap_mux_init: Add partition: #1: core, flags: 4

registered ti814x_vpss device

registered TI814x on-chip HDMI device

pm_dbg_init: only OMAP3 supported

Registered ti81xx_fb device

bio: create slab <bio-0> at 0

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz

pcf857x 1-0021: gpios 128..143 on a pcf8575

i2c i2c-1: Failed to register i2c client PCF_8575 at 0x21 (-16)

i2c i2c-1: Can't create device at 0x21

Advanced Linux Sound Architecture Driver Version 1.0.23.

Switching to clocksource gp timer

musb-hdrc: version 6.0, host, debug=0

musb-hdrc musb-hdrc.0: dma type: dma-cppi41

registerd cppi-dma Intr @ IRQ 17

Cppi41 Init Done

musb-hdrc musb-hdrc.0: MUSB HDRC host driver

musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1

usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

usb usb1: Product: MUSB HDRC host driver

usb usb1: Manufacturer: Linux 2.6.37 musb-hcd

usb usb1: SerialNumber: musb-hdrc.0

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

musb-hdrc musb-hdrc.0: USB Host mode controller at d080c000 using DMA, IRQ 18

musb-hdrc musb-hdrc.1: dma type: dma-cppi41

musb-hdrc musb-hdrc.1: MUSB HDRC host driver

musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2

usb usb2: New USB device found, idVendor=1d6b, idProduct=0002

usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1

usb usb2: Product: MUSB HDRC host driver

usb usb2: Manufacturer: Linux 2.6.37 musb-hcd

usb usb2: SerialNumber: musb-hdrc.1

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected

musb-hdrc musb-hdrc.1: USB Host mode controller at d081e800 using DMA, IRQ 19

NET: Registered protocol family 2

IP route cache hash table entries: 2048 (order: 1, 8192 bytes)

TCP established hash table entries: 8192 (order: 4, 65536 bytes)

TCP bind hash table entries: 8192 (order: 3, 32768 bytes)

TCP: Hash tables configured (established 8192 bind 8192)

TCP reno registered

UDP hash table entries: 256 (order: 0, 4096 bytes)

UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

NET: Registered protocol family 1

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

RPC: Registered tcp NFSv4.1 backchannel transport module.

NetWinder Floating Point Emulator V0.97 (double precision)

PMU: registered new PMU device of type 0

omap-iommu omap-iommu.0: ducati registered

omap-iommu omap-iommu.1: sys registered

JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.

msgmni has been set to 397

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0

console [ttyO0] enabled

omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1

omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2

omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3

omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4

omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5

brd: module loaded

loop: module loaded

ahci ahci.0: forcing PORTS_IMPL to 0x1

ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode

ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst

scsi0 : ahci_platform

ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16

omap2-nand driver initializing

NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron )

Creating 6 MTD partitions on "omap2-nand.0":

0x000000000000-0x000000020000 : "U-Boot-min"

0x000000020000-0x000000260000 : "U-Boot"

0x000000260000-0x000000280000 : "U-Boot Env"

0x000000280000-0x0000006c0000 : "Kernel"

0x0000006c0000-0x00000cee0000 : "File System"

0x00000cee0000-0x000010000000 : "Reserved"

davinci_mdio davinci_mdio.0: davinci mdio revision 1.6

davinci_mdio davinci_mdio.0: detected phy mask fffffffc

davinci_mdio.0: probed

davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown

davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown

usbcore: registered new interface driver cdc_ether

usbcore: registered new interface driver dm9601

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

mice: PS/2 mouse device common for all mice

ata1: SATA link down (SStatus 0 SControl 300)

qt602240_ts 1-004a: Family ID: 128 Variant ID: 1 Version: 22 Build: 171

qt602240_ts 1-004a: Matrix X Size: 18 Matrix Y Size: 12 Object Num: 17

input: AT42QT602240/ATMXT224 Touchscreen as /devices/platform/omap/omap_i2c.1/i2c-1/1-004a/input/input0

i2c /dev entries driver

Linux video capture interface: v2.00

usbcore: registered new interface driver uvcvideo

USB Video Class driver (v1.0.0)

OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec

usbcore: registered new interface driver usbhid

usbhid: USB HID core driver

notify_init : notify drivercreated for remote proc id 2 at physical Address 0xbf900000

usbcore: registered new interface driver snd-usb-audio

asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok

ALSA device list:

#0: TI81XX EVM

TCP cubic registered

NET: Registered protocol family 17

Registering the dns_resolver key type

VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3

omap_voltage_late_init: Voltage driver support not added

Detected MACID=0:0:0:0:0:0

Waiting for root device /dev/mmcblk0p2...

mmc0: new high speed SDHC card at address e624

mmcblk0: mmc0:e624 SD08G 7.40 GiB

mmcblk0: p1 p2 p3

EXT3-fs: barriers not enabled

kjournald starting. Commit interval 5 seconds

EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended

EXT3-fs (mmcblk0p2): using internal journal

EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode

VFS: Mounted root (ext3 filesystem) on device 179:2.

devtmpfs: mounted

Freeing init memory: 188K

INIT: version 2.86 booting

Please wait: booting...

Error opening /dev/fb0: No such file or directory

Starting udev

udevd (84): /proc/84/oom_adj is deprecated, please use /proc/84/oom_score_adj instead.

udev: starting version 141

Remounting root file system...

Caching udev devnodes

Populating dev cachemv: cannot rename '/tmp/devices': No such file or directory

NET: Registered protocol family 10

ALSA: Restoring mixer settings...

EXT3-fs: barriers not enabled

kjournald starting. Commit interval 5 seconds

EXT3-fs (mmcblk0p3): warning: maximal mount count reached, running e2fsck is recommended

EXT3-fs (mmcblk0p3): using internal journal

EXT3-fs (mmcblk0p3): mounted filesystem with writeback data mode

Configuring network interfaces...

CPSW phy found : id is : 0x4dd074

ADDRCONF(NETDEV_UP): eth0: link is not ready

udhcpc (v1.13.2) started

Sending discover...

Sending discover...

PHY: 0:00 - Link is Up - 1000/Full

ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Sending discover...

No lease, forking to background

done.

Setting up IP spoofing protection: rp_filter.

hwclock: can't open '/dev/misc/rtc': No such file or directory

Fri Sep 9 12:47:00 UTC 2011

hwclock: can't open '/dev/misc/rtc': No such file or directory

INIT: Entering runlevel: 5

Starting system message bus: dbus.

Loading HDVICP2 Firmware

DM814X prcm_config_app version: 2.0.0.1

Doing PRCM settings...

       PRCM for IVHD0 is in Progress, Please wait.....  

                       BW Phy Addr : 0x48180600 Data : 0x00000002

                       AW Phy Addr : 0x48180600 Data : 0x00000002

                       Phy Addr : 0x48180c04 Data : 0x00000037

                       BW Phy Addr : 0x48180620 Data : 0x00070000

                       AW Phy Addr : 0x48180620 Data : 0x00070002

                       BW Phy Addr : 0x48180624 Data : 0x00030000

                       AW Phy Addr : 0x48180624 Data : 0x00010002

                       Phy Addr : 0x48180600 Data : 0x00000102

                       BW Phy Addr : 0x48180c10 Data : 0x00000007

                       AW Phy Addr : 0x48180c10 Data : 0x00000003

                       Phy Addr : 0x48180c14 Data : 0x00000004

                       BW Phy Addr : 0x58088000 Data : 0xe889b429

                       AW Phy Addr : 0x58088000 Data : 0xeafffffe

                       BW Phy Addr : 0x58098000 Data : 0x07f256cc

                        AW Phy Addr : 0x58098000 Data : 0xeafffffe

                       BW Phy Addr : 0x48180c10 Data : 0x00000003

                       AW Phy Addr : 0x48180c10 Data : 0x00000000

                       Phy Addr : 0x48180c14 Data : 0x00000007

     PRCM for IVHD0 is Done Successfully  

PRCM Initialization completed

SysLink version : 2.00.02.80

SysLink module created on Date:Sep 8 2011 Time:16:36:33

FIRMWARE: Memory map bin file not passed

Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]

FIRMWARE: Default memory configuration is used

MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.1.1

FIRMWARE: Memory Configuration status : In Progress

FIRMWARE: 1 start Successful

Starting telnet daemon.

Loading HDVPSS Firmware

FIRMWARE: Memory map bin file not passed

Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]

FIRMWARE: Default memory configuration is used

MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.1.1

FIRMWARE: Memory Configuration status : In Progress

FIRMWARE: 2 start Successful

Configuring fb0 to LCD

cat: write error: No space left on device

cat: write error: No space left on device

HDMI W1 rev 4.0

Starting syslogd/klogd: done

Starting thttpd.

Starting PVR

/dev/mem opened.

Memory mapped at address 0x40302000.

Read at address 0x48180F04 (0x40302f04): 0x00000001

Write at address 0x48180F04 (0x40302f04): 0x00000000, readback 0x00000000

/dev/mem opened.

Memory mapped at address 0x40192000.

Read at address 0x48180900 (0x40192900): 0x00000102

Write at address 0x48180900 (0x40192900): 0x00000002, readback 0x00000002

/dev/mem opened.

Memory mapped at address 0x40345000.

Read at address 0x48180920 (0x40345920): 0x00040002

Write at address 0x48180920 (0x40345920): 0x00000002, readback 0x00000002

Starting Matrix GUI application.

_____                   _____           _         _  

| _ |___ ___ ___ ___   | _ |___ ___ |_|___ ___| |_

|     | _| .'| . | . | |   __| _| . | | | -_| _| _|

|__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|  

             |___|                   |___|            

Arago Project http://arago-project.org dm814x-evm ttyO0

Arago 2011.05 dm814x-evm ttyO0

dm814x-evm login:

CTRL-A Z for help |115200 8N1 | NOR | Minicom 2.4   | VT102 |     Offline                                                                                          

 

and here is report from u-boot using the printenv command:

 

TI8148_EVM#printenv                                                            

bootcmd=if mmc init; then if run loadbootscript; then run bootscript; else echo

In case ENV on MMC/SD is required; echo Please put a valid script named boot.scr

on the card; echo Refer to the User Guide on how to generate the image; fi; els

e echo Please set bootargs and bootcmd before booting the kernel; echo If that h

as already been done please ignore this message; fi                            

bootdelay=3                                                                    

baudrate=115200                                                                

autoload=yes                                                                  

verify=yes                                                                    

bootfile=uImage                                                                

ramdisk_file=ramdisk.gz                                                        

loadaddr=0x81000000                                                            

script_addr=0x80900000                                                        

loadbootscript=fatload mmc 1 ${script_addr} boot.scr                          

bootscript= echo Running bootscript from MMC/SD to set the ENV...; source ${scri

pt_addr}                                                                      

stdin=serial                                                                  

stdout=serial                                                                  

stderr=serial                                                                  

ethaddr=@_�&FR#                                                                

ethact=cpsw                                                                    

                                                                              

Environment size: 718/8188 bytes  

 


Thanks,

Ivana

 

 

  • Hi Ivana,

    user4223919 said:
    Demo examples works fine (more or less) but when I want to run "helloworld" refuses. In my opinion the problem is in NFS boot.

    To run the helloworld application (from section 2.2 Writing your own "Hello World!" application and executing it on the target from the DM814x_EZ_Software_Developers_Guide.pdf) you can use all boot modes available (MMC/SD, UART, NAND, NOR, SPI, EMAC/NFS), not only EMAC/NFS. You just neet to place the executable file in /home/root/ directory of your root filesystem.

    user4223919 said:
    Kernel command line: console=ttyO0,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=256M earlyprink notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfb.vram=0:16M,1:16M,2:6M ip

    This means you are using MMC/SD boot and root filesystem on the MMC/SD card, not NFS. What I can recommend you is to download the latest DM814x EZSDK 5.05.02.00 and run the setup.sh script on the MMC/SD card, see section 6.6 How to create an SD card. Then you should place the helloworld executable in second partition of the MMC/SD card (in /home/root/). Then you should insert the MMC/SD card in EVM and boot. After boot up, you can execute the helloworld application in the EVM.

    If you need to use NFS, then you can use MMC/SD card to load the u-boot, then interrupt the countdown to enter into the u-boot prompt and configure the boot argument for NFS (as they are for MMC/SD by default).

    Regards,
    Pavel

  • Hello Pavel,

    thanx for quick respond on my post. I have tried as you recomended, but I don't know what I did wrong. :(

    I have followed the instructions in
    - 6.6 How to create an SD card
    - U-Boot SD Support from http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_U-Boot#U-Boot_SD_.28Secured_Digital_card.29_Support

    I tried with formatting my sd card in FAT, FAT32, Ext3 formats but it does not work.

    I get this answer from my computer:

    .......
    [ 494.676277] mmc0: new high speed SDHC card at address b368
    [ 494.717658] mmcblk0: mmc0:b368 NCard 3.73 GiB
    [ 494.717773] mmcblk0: p1
    [ 510.308513] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x01270600
    ivana@ivana-laptop:~$



    ivana@ivana-laptop:~$ sudo $EZSDK/bin/mksdboot.sh --device /dev/mmcblk0 --sdk ${EZSDK}
    ************************************************************
    * THIS WILL DELETE ALL THE DATA ON /dev/mmcblk0 *
    * *
    * WARNING! Make sure your computer does not go *
    * in to idle mode while this script is *
    * running. The script will complete, *
    * but your SD card may be corrupted. *
    * *
    * Press <ENTER> to confirm.... *
    ************************************************************

    ls: cannot access /dev/mmcblk0?: No such file or directory
    1024+0 records in
    1024+0 records out
    1048576 bytes (1.0 MB) copied, 0.184765 s, 5.7 MB/s
    Disk /dev/mmcblk0 doesn't contain a valid partition table
    Checking that no-one is using this disk right now ...
    BLKRRPART: Device or resource busy

    This disk is currently in use - repartitioning is probably a bad idea.
    Umount all file systems, and swapoff all swap partitions on this disk.
    Use the --no-reread flag to suppress this check.
    Use the --force flag to overrule all checks.
    ERROR
    ivana@ivana-laptop:~$ sudo $EZSDK/bin/mksdboot.sh --device /dev/mmcblk0 --sdk ${EZSDK} --force
    ************************************************************
    * THIS WILL DELETE ALL THE DATA ON /dev/mmcblk0 *
    * *
    * WARNING! Make sure your computer does not go *
    * in to idle mode while this script is *
    * running. The script will complete, *
    * but your SD card may be corrupted. *
    * *
    * Press <ENTER> to confirm.... *
    ************************************************************

    ls: cannot access /dev/mmcblk0?: No such file or directory
    1024+0 records in
    1024+0 records out
    1048576 bytes (1.0 MB) copied, 0.295458 s, 3.5 MB/s
    Disk /dev/mmcblk0 doesn't contain a valid partition table
    Checking that no-one is using this disk right now ...
    OK

    Disk /dev/mmcblk0: 487 cylinders, 255 heads, 63 sectors/track

    sfdisk: ERROR: sector 0 does not have an msdos signature
    /dev/mmcblk0: unrecognized partition table type
    Old situation:
    No partitions found
    New situation:
    Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

    Device Boot Start End #cyls #blocks Id System
    /dev/mmcblk0p1 * 0+ 4 5- 40131 c W95 FAT32 (LBA)
    /dev/mmcblk0p2 5 114 110 883575 83 Linux
    /dev/mmcblk0p3 115 486 372 2988090 83 Linux
    /dev/mmcblk0p4 0 - 0 0 0 Empty
    Successfully wrote the new partition table

    Re-reading the partition table ...

    If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
    to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
    (See fdisk(8).)
    Formating /dev/mmcblk01 ...
    /dev/mmcblk01: No such file or directory

    ERROR: executing mkfs.vfat -F 32 -n BOOT /dev/mmcblk01


    Please help me :)

    Ivana
  • Ivana,

    user4223919 said:
    - U-Boot SD Support from http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_U-Boot#U-Boot_SD_.28Secured_Digital_card.29_Support</div></blockquote><div class="quote-footer"></div></p>

    This wiki page is old, please refer to

    user4223919 said:
    ivana@ivana-laptop:~$ sudo $EZSDK/bin/mksdboot.sh --device /dev/mmcblk0 --sdk ${EZSDK}

    No, this is not correct. You should plug your MMC/SD card into your host computer (desktop PC or laptop/notebook) through a MMC/SD card reader. You plug the MMC/SD card into the card reader and plug the card reader itself in your host computer through USB cable. The when you run the "dmesg" command (ivana@ivana-laptop:~$ dmesg) you should see your MMC/SD card detected on (in most of the cases) sdb. sda is usually your hard disk, so most of the cases you should use sdb. In rare cases in might be also sdc. You should check careful the log console when you execute "dmesg". In the example provided in the User Guide, sdb is detected for the MMC/SD:

    host $ dmesg
    [14365.272631] sd 6:0:0:1: [sdb] 3862528 512-byte logical blocks: (1.97 GB/1.84 GiB)
    [14365.310602] sd 6:0:0:1: [sdb] Assuming drive cache: write through
    [14365.325542] sd 6:0:0:1: [sdb] Assuming drive cache: write through
    [14365.325571] sdb: sdb1 sdb2

    In this example, SD card is detected on /dev/sdb.

    On my host computer (desktop PC) is the same, sdb is detected for MMC/SD:

    [1210835.819117] sd 8:0:0:0: [sdb] 7744512 512-byte logical blocks: (3.96 GB/3.69 GiB)
    [1210835.820216] sd 8:0:0:0: [sdb] Write Protect is off
    [1210835.820221] sd 8:0:0:0: [sdb] Mode Sense: 03 00 00 00
    [1210835.820224] sd 8:0:0:0: [sdb] Assuming drive cache: write through
    [1210835.822952] sd 8:0:0:0: [sdb] Assuming drive cache: write through
    [1210835.822956]  sdb: sdb1 sdb2

    Then you should run the below command (in case sdb is detected):

    ivana@ivana-laptop:~$ sudo ${EZSDK}/bin/mksdboot.sh --device /dev/sdb --sdk ${EZSDK}

    BR
    Pavel

  • Hello Pavel :)

    I did twice everything you have told me but the same problem is still here :( So, I installed CCSv5 and tried to configure CCSv5 for communicating with my EVM. It is everything ok with demo examples (I run terminal from CCSv5), but I don't know were to save and how to run some simple executive program like helloworld.

    Please help me. I don`t want to gave up until I run some basic programs :)

    BR,
    Ivana
  • Ivana,

    user4223919 said:
    I did twice everything you have told me but the same problem is still here

    May be your MMC/SD card is corrupted. I would recommend you to check with another MMC/SD card.

    user4223919 said:
    but I don't know were to save and how to run some simple executive program like helloworld.

    When you start CCSv5, you create workspace (folder in your host machine) and your project is saved there. See the below wiki page for more info (it is for AM335x device, but the things are similar for DM814x device):

    processors.wiki.ti.com/.../Code_Composer_Studio_v5_Users_Guide

    Regards,
    Pavel