===Introduction===NaonEVB-Mid is a carrier board designed to evaluate the functionalities of [[:Category:Naon|NAON]].  [[File:Naonevb-mid-dvi-01.png|600px|frameless|border]]  The following picture shows block diagram of NaonEVB-Mid board.[[File:Naonevb-mid-block diagram.png|thumbnail|center|300px|NaonEVB-Mid block diagram]] The following images show top and bottom side of NaonEVB-Mid carrier board respectively. Peripherals and interfaces external to Naon SOM are highlighted. [[File:Naonevb-mid_top.jpg|thumbnail|center|300px|NaonEVB-Mid top view]][[File:Naon-evb-mid_bottom.png|thumbnail|center|300px|NaonEVB-Mid bottom view]] ===Quick start (NELK)=== This section describes how to quick start NaonEVB-Mid-based system, provided that it is programmed according to NELK configuration. # connect the serial cable provided with the board to J17 connector# connect this cable to PC COM port through a NULL-modem cable (not provided)# start your favourite terminal software on PC; communication parameters are:#* baud rate: 115200 Bps#* data bits: 8#* stop bits: 1#* parity: none # (optional) to connect the system to Ethernet LAN, please plug cable on connector J11# (optional) to connect the system to HDMI TV/LCD, please plug cable on connector J6# connect a 12Vcc power supply to J14 as shown in the following picture: [[File:Naonevb-mid-power-connector.jpg|thumb|none|border|300px]] Once power has been applied, U-Boot bootloader will be executed and the following messages will be printed on serial console (please note that messages may vary due different U-Boot releases): <pre class="board-terminal">U-Boot 2010.06-00011-gd371eb4 (Apr 22 2013 - 12:17:17) [nelk-4.0.0-Naon-min] TI8148-GP rev 2.1 ARM clk: 600MHzDDR clk: 400MHzL3 clk: 200MHzDSS clk: 200MHzIVA clk: 266MHzISS clk: 400MHzDSP clk: 500MHz DRAM: 512 MiBUsing default environment Hit any key to stop autoboot: 0 8192 KiB AT45DB642D at 0:0 is now current device## Starting application at 0x81000000 ...  U-Boot 2010.06-00011-gd371eb4 (Apr 22 2013 - 12:17:53) [nelk-4.0.0-Naon] TI8148-GP rev 2.1 ARM clk: 600MHzDDR clk: 400MHzL3 clk: 200MHzDSS clk: 200MHzIVA clk: 266MHzISS clk: 400MHzDSP clk: 500MHz I2C: readyDRAM: 512 MiBNAND: HW ECC BCH8 Selected1024 MiBMMC: OMAP SD/MMC: 0MUX: configuring for evb_midNet: Detected MACID:00:50:C2:1E:AF:E3cpswNAON#</pre> These messages are printed by [[:Category:U-Boot|U-Boot]], which has a serial console that allow basic interaction with the system. Please find more information in the [[:Category:U-Boot|U-Boot]] category page. At the end of its boot sequence, U-Boot prints <code style="board-terminal">NAON#</code> prompt and waits for user commands. The default u-boot environment can be printed using the <code style="board-terminal">print</code> command: <pre class="board-terminal">bootdelay=3baudrate=115200autoload=yesverify=yesbootfile=naon/uImageramdisk_file=ramdisk.gzloadaddr=0x81000000spi_load_1st=tftp ${loadaddr} naon/MLOnand_load_1st=mw.b ${loadaddr} 0xFF 0x20000; tftp ${loadaddr} naon/MLOspi_update_1st=sf probe 0:0; sf erase 0x0 0x20000; sf write ${loadaddr} 0x0 0x20000nand_update_1st=nand erase 0x0 0x20000; nandecc hw 2; nand write.i ${loadaddr} 0x0 0x20000load=mw.b ${loadaddr} 0xFF 0x40000; tftp ${loadaddr} naon/u-boot.binspi_update=sf probe 0:0; sf erase 0x20000 0x40000; sf write ${loadaddr} 0x20000 0x40000nand_update=nand erase 0x20000 0x40000; nandecc hw 2; nand write.i ${loadaddr} 0x20000 0x40000loadk=mw.b ${loadaddr} 0xFF 0x400000; tftp ${WorkInProgressloadaddr}${bootfile}spi_updatek=sf probe 0:0; sf erase 0x80000 0x400000; sf write ${loadaddr} 0x80000 0x400000nand_updatek=nand erase 0xA0000 0x400000; nandecc hw 2; nand write.i ${loadaddr} 0xA0000 0x400000console=ttyO0addcons=setenv bootargs ${bootargs} console=${console},115200n8 earlyprintkaddmem=setenv bootargs ${bootargs} mem=${mem} vram=${vram} notifyk.vpssm3_sva=${notify_mem}addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gateway}:${netmask}:${hostname}:${ethdev}nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath} panic=5 rootdelay=5net_nfs=run loadk nfsargs addip addcons addmem; bootm ${buf}nandargs=setenv bootargs root=/dev/mtdblock12 rw rootfstype=jffs2spi_nand=run nandargs addip addcons addmem; sf probe 0:0; sf read ${loadaddr} 0x80000 0x400000; bootm ${loadaddr}nand_nand=run nandargs addip addcons addmem; nandecc hw 2; nand read ${loadaddr} 0xA0000 0x400000; bootm $(loadaddr}mmcargs=setenv bootargs root=/dev/mmcblk0p1 rwspi_mmc=run mmcargs addip addcons addmem; sf probe 0:0; sf read ${loadaddr} 0x80000 0x400000; bootm ${loadaddr}ipaddr=192.168.0.77serverip=192.168.0.23netmask=255.255.255.0gateway=192.168.0.254hostname=naonrootpath=/home/shared/devel/dave/naon-DAA/sw/linux/sdk/rfs/nelkethdev=eth1mem=176Mvram=46Mnotify_mem=0xBF900000ethaddr=00:17:EB:52:6A:8Aethact=cpswnaon_host=evb_midstdin=serialstdout=serialstderr=serial </pre> ==== Booting from SD/MMC ====

If you have the bootable SD/MMC provided with the development kit and it contains the boot.scr script file, the following command is automatically executed by U-Boot: <pre class="board-terminal">echo trying to boot from NELK MMC; mmc rescan 0; fatload mmc 0 80900000 boot.scr; source 80900000; run net_nfs</pre> If the boot.scr script file is not available, you can manually boot the system from SD using the following commands: <pre class="board-terminal">mmc rescan 0fatload mmc 0 81000000 uImagesetenv mmcargs 'setenv bootargs root=Introduction/dev/mmcblk0p2 rw'run mmcargs addip addcons addmembootm 81000000</pre>  If a Linux kernel image has been preliminary programmed on the SPI NOR flash, you can run the following command: <pre class="board-terminal">run spi_mmc</pre> To start Linux (from on-board SPI NOR flash) and mount the development root file system (over SD/MMC). ==== Booting from network ==== If you have installed the [[:Category:DVDK|'''DAVE Embedded Systems''' Virtual Development Kit]], you can start the Virtual Machine and start Linux loading the kernel through tftp and mounting the NFS root file system with the following command: <pre class="board-terminal">run net_nfs</pre> Please note that you need to modify some u-boot environment variables before running the net_nfs configuration. For further information, please refer to [[Booting_Linux_Kernel#Configuration_net_nfs | Configuration net_nfs]]. ===Hardware information=== ====Bootstrap settings==== Please refer to [[Bootstrap settings (NaonEVB-Mid is )]] ====JTAG interfaces==== Please refer to [[JTAG interfaces (NaonEVB-Mid)]]. ====Video interfaces====NaonEVB-Mid provides a carrier board designed rich set of video input/output interfaces. Please refer to evaluate the functionalities of [[Naon SOMVideo input/output interfaces (NaonEVB-Mid)|this page]]for more details.==Schematics=={{ImportantMessage|text=Please note that Orcad CIS is required to get all the information about BOM variants included in .dsn files.  PDF files show the view of the default BOM variant used to manufacture the board. Also it can be viewed Components that are not populated are denoted as reference design "Do Not Stuff".}}* Orcad: http://www.dave.eu/system/files/area-riservata/naonevb-mid-1.0.6.zip* PDF: http://www.dave.eu/system/files/area-riservata/naonevb-mid-NADP_S-NADP0000C0R_1.0.6.pdf == PinMux == * File .dat for the [http://www.ti.com/tool/pinmuxtool PinMux utility] containing the cpu pin configuration for multimedia applications built upon Naon modulethe NaonEVB-Mid carrier board : http://www.dave.eu/system/files/area-riservata/naon-evbs-pinmux.zip ==BOM==* http://www.dave.eu/system/files/area-riservata/naonevb-mid-BOM_S.NADP0000C0R.1.0.6.zip==Layout==* http://www.dave.eu/system/files/area-riservata/naonevb-mid-CS064311A_component_view.pdf==Mechanical==* DXF: http://www.dave.eu/system/files/area-riservata/naonevb-mid-CS064311A.zip* IDF (3D): http://www.dave.eu/system/files/area-riservata/naonevb-mid-CS064311-3D.zip