Changes

Jump to: navigation, search

Software Manual (Diva)

1,662 bytes added, 16:59, 23 February 2021
→‎Support service
{{Applies To Diva}}
{{InfoBoxBottom}}
 
{{WarningMessage|text=The following information are valid for <b>DIVELK</b> version up to release <b>2.2.0</b>}}
= Introduction =
== About this manual ==
This document describes how to run Linux on the DIVA/DIVAEVB-Lite/Carrier-board system and how to work with '''DIVELK version 2.0.0'''and above. For novice users who have no experience at all about embedded Linux systems, reading of [http://shop.oreilly.com/product/9780596002220.do Building Embedded Linux Systems By Karim Yaghmour] is strongly recommended. Practically speaking, the book covers all matters involved in developing software for such systems (from tool-chain organization to the most famous file systems running on top of MTD). It is not a reference guide, but it provides a complete and exhaustive overview that helps the developer save a lot of time in searching for such information on the Internet. For a brief but still exhaustive overview of the Linux and Embedded Linux world, please look at the Training and Docs sections of [http://free-electrons.com Free Electrons website].
== Support service ==
We are committed to making our products user-friendly and will help customers use our CPU modules in their systems. Technical support is delivered through email. Support requests can be sent to [mailto:support-divahelpdesk@dave.eu support-divahelpdesk@dave.eu]. Software upgrades are available in the restricted download area of '''DAVE Embedded Systems''' web sitegit server: http://www<code>git@git.dave.eu</reserved-area. code> An account is required to access this area (please contact [mailto:support-divahelpdesk@dave.eu support-divahelpdesk@dave.eu] for account requests). 
Please refer to our Web site at http://www.dave.eu/dave-cpu-module-am335x-diva.html for the latest product documents, utilities, drivers, Product Change Notices, Board Support Packages, Application Notes, mechanical drawings and additional tools and software.
[[File:Diva-400.png|300px]]
The heart of DIVA SOM is Texas Instruments "Sitara" [http://www.ti.com/lsds/ti/arm/sitara_arm_cortex_a_processor/sitara_arm_cortex_a8/am335x_arm_cortex_a8/products.page?paramCriteria=no AM335x microprocessors]. From a software point of view, Texas Instruments supports this processor family through so-called Linux EZ AM Software Development Kit (EZSDK AMSDK for short). EZSDK AMSDK releases are published on a regular basis. For more details please refer to:
* http://www.ti.com/tool/linuxezsdk-sitara
* http://processors.wiki.ti.com/index.php/Category:EZSDK
DIVA Embedded Linux Kit, in turn, is directly derived from EZSDKAMSDK. Hence DIVELK documentation often refers to EZSDK AMSDK resources.
=== Carrier boards ===
Please note that DIVELK u-boot and kernel source trees are derived from the official trees released by TI; these trees have been customized to add support for the DIVA SOM.
For further information on EZSDKAMSDK, please refer to [http://processors.wiki.ti.com/index.php/Sitara_SDK_5.06.00_Release_Notes Sitara SDK release notes].
==== DIVELK software components ====
'''DAVE Embedded Systems''' adds to the latest EZSDK AMSDK from Texas Instruments the customization required to support the DIVA platform. For this reason most of the documentation provided by TI remains valid for the DIVELK development kit. However, some customization is required, in particular at bootloader and linux kernel levels.
The following [[Diva_Embedded_Linux_Kit_(DIVELK)#DIVELK_software_components | Please refer to this table shows how DIVELK releases are related to EZSDK AMSDK releases.{| class="wikitable" !!colspan="2" | DIVELK version|-|Release number|1.0.0|2.0.0|-|Status|Released|Work in progress|-|Release date|June 2013|August 2014|-|'''Release notes'''|[[Software_Manual_(Diva)#DIVELK_1.0.0 | Ver 1.0.0]]| -|-|SOM PCB version|CS133012A|CS133012A|-|Supported carrier boards|[[DivaEVB-Lite]]<br>[[:Category:Dacu | Dacu]]|[[DivaEVB-Lite]]<br>[[:Category:Dacu | Dacu]]|-|U-Boot version|2012.10-divelk-1.0.0|2012.10-divelk-2.0.0|-|Linux version|3.2.0-divelk-1.0.0|3.12.10-divelk-2.0.0|- |Drivers|valign="top" | SPI NOR Flash (boot)<br>NAND 8 bit (boot)<br>UART0 (2-wire)<br>USB Host<br>SD/MMC1<br>GPIO<br>LCD<br>Touch screen controller<br>EMAC0 RMII (Fast Ethernet)<br>PMIC RTC (battery powered)<br>Audio (ALSA)|valign="top" | SPI NOR Flash (boot)<br>NAND 8 bit (boot)<br>UART0 (2-wire)<br>USB Host<br>SD/MMC1<br>GPIO<br>LCD<br>Touch screen controller<br>EMAC0 RMII (Fast Ethernet)<br>PMIC RTC (battery powered)<br>Audio (ALSA)<br>USB OTG<br>CAN<br>ADC|-|TI EZSDK|05.06.00.00|07.00.00.00|-|Build System| -|Yocto Dylan (1.4)|-|}
=== DIVELK Updates ===
* start a shell session
* enter the .ssh subdirectory into your home directory: <code>cd ~/.ssh/</code>
* launch the following command: <br><pre>ssh-keygen -t rsa -C "username@myhost.com"-f username@myhost.com</pre>
* this command creates the files <code>~/.ssh/username@myhost.com</code> ('''private key''') and <code>~/.ssh/username@myhost.com.pub</code> ('''public key''')
* edit your <code>~/.ssh/config</code> adding the following lines:
== Release notes ==
'''N.B.''' '''Customers who want to update from DIVELK 1.0.0 to DIVELK 2.0.0 can send an email Please refer to [mailtohttps:support-diva@dave//wiki.eu support-diva@dave.eu]'''/index. === php/Diva_Embedded_Linux_Kit_(DIVELK 2.0.0 === * Release date: October 2014* Status: Work in progress* EZSDK version: 07.00.00.00* Supported carrier boards: DIVAEVB-Lite, Dacu ==== Notes ==== * First major update* Added Yocto support* Updated kernel and u-boot versions* Bug fixes  === )#Release_notes this page] for DIVELK 1.0.0 === * Release date: June 2013* Status: released* EZSDK version: 05.06.00.00* Supported carrier boards: DIVAEVB-Lite, Dacu ==== Notes ==== * First official release
= Developing environment =
For further information on Linux for TI processors, please refer to http://processors.wiki.ti.com/index.php/Category:Linux
 
==== Linux Device Tree ====
The Flattened Device Tree (FDT) is a data structure for describing the hardware in a system (for further information, please refer to http://elinux.org/Device_Tree). Device tree source code is stored into the arch/arm/boot/dts/ directory.
=== Target root file system ===
* VirtualBox virtual machine (.OVA archive)
* Based on Ubuntu Lubuntu 12.04 LTS(64-bit version)
* Pre-installed VirtualBox Guest Additions
* Multiple LXDE desktop environment available:** Unity (Ubuntu)** LXDE (Lubuntu)* Boot disk with pre-installed Ubuntu/Lubuntu Linux 12.04.2 LTS the distro and pre-configured basic Linux services:** TFTP: with base directory /srv/tftp/(please refer to [[VirtualBox_Network_Configuration]])** NFS: configured through the /etc/exports file(please refer to [[VirtualBox_Network_Configuration]])
* Secondary disk containing source code and tools:
** Bootloader (u-boot) source tree cloned from DAVE Embedded Systems public git repository
** External pre-built toolchain
** Yocto bsp for DIVA
* Pre-installed Yocto-based root file system systems with setup scripts, makefiles, example applications, ...
* Administrator account (dvdk) with autologin. Please note that the user account credentials are provided with the development kit (you can find them into the README file contained in the sw/dvdk folder of the kit distribution)
* DIVELK root file system partition (mmcblk0p2, ext3)
DIVELK contains all the required software and documentation to start developing Linux application on the DIVA platform. In particular, DIVELK provides a Virtualbox virtual machine with two emulated disks: * Boot disk with pre-installed Ubuntu Linux 12.04.2 LTS and pre-configured basic Linux services (TFTP, NFS, ...) * Secondary disk containing source code and tools:** Bootloader (u-boot) source tree cloned from '''DAVE Embedded Systems''' public git repository ** Linux kernel source tree cloned from '''DAVE Embedded Systems''' public git repository** Toolchain
=== Importing the Virtual Machine ===
# When the boot process is completed, you can login into the Ubuntu system with the credentials provided with the development kit (you can find them into the '''README''' file contained in the '''dvdk''' folder of the kit distribution)
# Mount the sdk disk launching the sdk-mount.sh script contained into /home/dvdk directory as shown on the image below:<br><br>[[File:divelk-dvdk-sdk-mount.png|600px]]<br><br>
 
<pre>
dvdk@dvdk:~$ sh sdk-mount.sh divelk
[sudo] password for dvdk:
dvdk@dvdk:~$
</pre>
The divelk directory contains the following subdirectories:
* gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linuxyocto: the Yocto SDK installation directory (containing the cross-toolchain. GNU Compiler Collection (GCC) version is 4.7.3
* linux-am33x: the Linux source tree
* u-boot-am33x: the U-Boot source tree
<pre>
export PATH=source ~/divelk/gccyocto/sdk/diva-linaroqt5/environment-arm-linux-gnueabihfsetupexport LDFLAGS=-L${PKG_CONFIG_SYSROOT_DIR}/usr/lib/4.7-2013.03-20130313_linux/bin:$PATH3export CFLAGS=""export CPPFLAGS=""export CXXFLAGS=""export CPATH=""
export ARCH=arm
export CROSS_COMPILE=arm-linux-gnueabihf-
==== NFS Server ====
One of the most useful features important components of a bootloader during development Linux system is the capability to download root file system. A good development root file system provides the Linux kernel from developer with all the networkuseful tools that can help developers on their work. This saves Such a lot of time because developer doesnroot file system can become very big in size, so it't have s hard to program store it in flash memory. User could split the image file system in different parts, mounting them from different media (flash every time he/she modifies it, network, usb...). U-Boot implements But the most convenient thing is to mount the TFTP protocol (see whole root file system from the tftp command)network, so allowing the host system must and the target to share the same files. In this way, developers can quickly modify the root file system, even “on the fly” (meaning that the file system can be configured modified while the system is running). The most common way to enable setup a system like the one described is through NFS (Network File System). As for TFTP service. Installation , installation and configuration of a TFTP server depends on the host Linux distribution. The default DVDK tftp NFS installation has is configured for sharing <code>/srvhome/dvdk/tftpdivelk</code> as work directoryand all the subdirectories. A subdirectory dedicated to  We recommend reading the [[VirtualBox_Network_Configuration]] page for additional details on the image files associated DVDK networking configuration and on how to the DIVELK (<code>/srv/tftp/divelk</code>) is available, but developers can add their custom subdirectories when requiredenable NFS.
==== Pre-built toolchain ====
These packages can be installed with the following command:
<pre>
sudo apt-get install git curl build-essential diffstat texinfo gawk chrpath ia32-libs python-m2crypto
</pre>
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > repo
$ chmod +x repo
$ ./repo init -u git@git.dave.eu:dave/diva/diva-bsp.git -b diva-dev-dylan
$ ./repo sync
</pre>
=== Building the Yocto image ===
 
Please note that even building the basic root file system requires a few hours to complete the process on a mid-hi range desktop PC (4-6 cores, 8-12 GiB RAM), also depending on the Internet connection speed (all source are fetched from the network). Nearly 20GiB of disk space is required for the build. Moreover, building inside the DVDK adds some overhead, since the performances of a virtual machine are reduced if compared to the physical hardware. Thus, it's recommended to check the hardware capabilities of the host system and, when building with Yocto is required, developers should consider the following options:
 
* migrating the build system to a physical machine
* assuming that the host system has the required resources, extending the hardware capabilities of the default DVDK (eg: adding more cores and disk space)
Once completed the initialization phase, developers can launch the Yocto image build process with the following commands:
 
<pre>
$ cd ~/divelk/diva-bsp
* qt5-rootfs-image (root file system with Qt 5.1.1 libraries and examples)
* base-rootfs-image (minimal root file system)
 
The resulting files (kernel, device tree and u-boot binaries, plus root file system in a .tar.gz archive) will then be available inside the build/tmp/deploy/images/diva directory.
== 4.4 Building the software components outside Yocto ==
Hello world
</pre>
 
=== Build the graphics components ===
 
<strike>AM335x processors provide a PowerVR SGX530 2D/3D graphics accelerator (SGX). This subsystem accelerates 2-dimensional (2D) and 3-dimensional (3D) graphics applications. The SGX subsystem is based on the POWERVR® SGX core from Imagination Technologies. SGX is a new generation of programmable POWERVR graphic cores. The POWERVR SGX530 v1.2.5 architecture is scalable and can target all market segments from mainstream mobile devices to high-end desktop graphics.
 
[http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/gfxsdk/latest/index_FDS.html TI Linux Graphics SDK] is the development package that provides graphics drivers and OpenGLES1.1,2.0 and OpenVG libraries and demos running on all TI platforms.
 
Instruction on how to build the graphic components can be found here: http://processors.wiki.ti.com/index.php/Graphics_SDK_Quick_installation_and_user_guide</strike>
== Boot configurations ==
OOB size 64 b
Erase size 131072 b
</pre>
 
=== Default flash NOR SPI partitions ===
 
<pre>
[ 1.370563] Creating 7 MTD partitions on "spi1.0":
[ 1.375888] 0x000000000000-0x000000040000 : "MLO"
[ 1.383286] 0x000000040000-0x0000000c0000 : "u-boot"
[ 1.390594] 0x0000000c0000-0x000000100000 : "env1"
[ 1.397868] 0x000000100000-0x000000140000 : "env2"
[ 1.405253] 0x000000140000-0x000000180000 : "fdt"
[ 1.412191] 0x000000180000-0x000000780000 : "kernel"
[ 1.419714] 0x000000780000-0x000002000000 : "free"
</pre>
 
=== Default flash NAND partitions ===
 
<pre>
[ 1.971955] Creating 9 MTD partitions on "omap2-nand.0":
[ 1.977663] 0x000000000000-0x000000020000 : "SPL"
[ 1.985117] 0x000000020000-0x000000040000 : "SPL.backup1"
[ 1.993214] 0x000000040000-0x000000060000 : "SPL.backup2"
[ 2.001160] 0x000000060000-0x000000080000 : "SPL.backup3"
[ 2.009145] 0x000000080000-0x000000260000 : "u-boot"
[ 2.018198] 0x000000260000-0x000000280000 : "u-boot-env"
[ 2.026420] 0x000000280000-0x0000002a0000 : "fdt"
[ 2.033730] 0x0000002a0000-0x0000008a0000 : "kernel"
[ 2.046645] 0x0000008a0000-0x000040000000 : "rootfs"
</pre>
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.12.10-divelk-2.0.0 (amon@linuxserver2) (gcc version 4.7.3 20130226 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 - Linaro GCC 2013.03) ) #26 SMP Sat Sep 13 10:45:59 CEST 2014
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] PERCPU: Embedded 8 pages/cpu @c0d9a000 s9024 r8192 d15552 u32768
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129280
[ 0.000000] Kernel command line: root=/dev/mmcblk0p2 rw console=ttyO0,115200n8 consoleblank=0mtdparts=omap2-nand.0:128k(SPL),128k(SPL.backup1),128k(SPL.backup2),128k(SPL.backup3),1920k(u-boot),128k(u-boot-env),128k(fdt),6m(kernel),-(rootfs);spi1.0:256k(MLO),512k(u-boot),256k(env1),256k(env2),256k(fdt),6m(kernel),-(free)
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] OMAP clocksource: timer1 at 24000000 Hz
[ 0.000000] Console: colour dummy device 80x30
[ 0.000405000409] Calibrating delay loop... 479.23 BogoMIPS (lpj=2396160)
[ 0.119684] pid_max: default: 32768 minimum: 301
[ 0.119839] Security Framework initialized
[ 0.119961119964] Mount-cache hash table entries: 512[ 0.131807131811] CPU: Testing write buffer coherency: ok
[ 0.132332] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[ 0.132408] Setting up static identity map for 0xc063b648 - 0xc063b6b8
[ 0.137485137504] Brought up 1 CPUs[ 0.137511137533] SMP: Total of 1 processors activated.[ 0.137522137544] CPU: All CPU(s) started in SVC mode.[ 0.138562138587] devtmpfs: initialized[ 0.143500143587] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3[ 0.209514209601] omap_hwmod: debugss: _wait_target_disable failed[ 0.210503210581] pinctrl core: initialized pinctrl subsystem[ 0.211769211857] regulator-dummy: no parameters[ 0.214592214690] NET: Registered protocol family 16[ 0.217656217798] DMA: preallocated 256 KiB pool for atomic coherent allocations[ 0.221356221492] cpuidle: using governor ladder[ 0.221379221516] cpuidle: using governor menu[ 0.230598230756] platform mpu.1: FIXME: clock-name 'fck' DOES NOT exist in dt![ 0.232257232413] platform 49000000.edma: FIXME: clock-name 'fck' DOES NOT exist in dt![ 0.234050234218] OMAP GPIO hardware version 0.1[ 0.247603247827] omap-gpmc 50000000.gpmc: could not find pctldev for node /pinmux@44e10800/nandflash_pins_default, deferring probe[ 0.247645247871] platform 50000000.gpmc: Driver omap-gpmc requests probe deferral[ 0.248269248489] platform 56000000.sgx: FIXME: clock-name 'fck' DOES NOT exist in dt![ 0.252788253038] DSS not supported on this SoC[ 0.252816253065] No ATAGs?[ 0.252829253079] hw-breakpoint: debug architecture 0x4 unsupported.[ 0.295867295970] bio: create slab <bio-0> at 0[ 0.319063319222] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver[ 0.320906321038] vin: 5000 mV [ 0.323602323718] SCSI subsystem initialized[ 0.325575325674] usbcore: registered new interface driver usbfs[ 0.325838325939] usbcore: registered new interface driver hub[ 0.326152326254] usbcore: registered new device driver usb[ 0.327258327385] omap_i2c 44e0b000.i2c: could not find pctldev for node /pinmux@44e10800/pinmux_i2c0_pins, deferring probe[ 0.327292327421] platform 44e0b000.i2c: Driver omap_i2c requests probe deferral[ 0.327812327950] pps_core: LinuxPPS API ver. 1 registered[ 0.327827327964] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>[ 0.328025328161] PTP clock support registered[ 0.330806330978] Advanced Linux Sound Architecture Driver Initialized.[ 0.332504332716] Switched to clocksource timer1[ 0.363046363794] NET: Registered protocol family 2[ 0.363902364657] TCP established hash table entries: 4096 (order: 3, 32768 bytes)[ 0.364002364762] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)[ 0.364086364847] TCP: Hash tables configured (established 4096 bind 4096)[ 0.364165364928] TCP: reno registered[ 0.364185364948] UDP hash table entries: 256 (order: 1, 8192 bytes)[ 0.364213364976] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)[ 0.364496365256] NET: Registered protocol family 1[ 0.365004365759] RPC: Registered named UNIX socket transport module.[ 0.365020365774] RPC: Registered udp transport module.[ 0.365030365783] RPC: Registered tcp transport module.[ 0.365039365793] RPC: Registered tcp NFSv4.1 backchannel transport module.[ 0.366220367016] NetWinder Floating Point Emulator V0.97 (double precision)[ 0.367011367827] PM: Loading am335x-pm-firmware.bin[ 0.529337530548] VFS: Disk quotas dquot_6.5.2[ 0.529528530738] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)[ 0.530515531740] NFS: Registering the id_resolver key type[ 0.530615531867] Key type id_resolver registered[ 0.530627531880] Key type id_legacy registered[ 0.530999532254] NTFS driver 2.1.30 [Flags: R/W].[ 0.531052532307] jffs2: version 2.2. (NAND) (SUMMARY) © �© 2001-2006 Red Hat, Inc.[ 0.531276532535] msgmni has been set to 989[ 0.534486535449] NET: Registered protocol family 38[ 0.534558535511] io scheduler noop registered[ 0.534571535523] io scheduler deadline registered[ 0.534609535560] io scheduler cfq registered (default)[ 0.537228538175] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568[ 0.589511590593] Console: switching to colour frame buffer device 100x30[ 0.597265598277] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled[ 0.600799601816] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88, base_baud = 3000000) is a OMAP UART0[ 1.259200281209] console [ttyO0] enabled[ 1.264920286942] omap_rng 48310000.rng: OMAP Random Number Generator ver. 20[ 1.288707310673] brd: module loaded[ 1.300807323060] loop: module loaded[ 1.311398333908] mtdoops: mtd device (mtddev=name/number) must be supplied[ 1.321358343735] edma-dma-engine edma-dma-engine.0: allocated channel for 0:17[ 1.328988350969] edma-dma-engine edma-dma-engine.0: allocated channel for 0:16[ 1.337003358842] m25p80 spi1.0: s25fl256s1 (32768 Kbytes)[ 1.346095364293] CAN 7 cmdlinepart partitions found on MTD device driver interfacespi1.0[ 1.352053370563] c_can_platform 481cc000Creating 7 MTD partitions on "spi1.d_can0": c_can_platform device registered (regs=fa1cc000, irq=68)[ 1.363406375888] usbcore0x000000000000-0x000000040000 : registered new interface driver asix"MLO"[ 1.369447383286] usbcore0x000000040000-0x0000000c0000 : registered new interface driver ax88179_178a[ "u-boot"[ 1.376425390594] usbcore0x0000000c0000-0x000000100000 : registered new interface driver cdc_ether"env1"[ 1.383027397868] usbcore0x000000100000-0x000000140000 : registered new interface driver r815x"env2"[ 1.389097405253] usbcore0x000000140000-0x000000180000 : registered new interface driver smsc95xx"fdt"[ 1.395481412191] usbcore0x000000180000-0x000000780000 : registered new interface driver net1080"kernel"[ 1.401742419714] usbcore0x000000780000-0x000002000000 : registered new interface driver cdc_subset"free"[ 1.408288428475] CAN device driver interface[ 1.434708] c_can_platform 481cc000.d_can: c_can_platform device registered (regs=fa1cc000, irq=68)[ 1.446015] usbcore: registered new interface driver zaurusasix[ 1.414649452044] usbcore: registered new interface driver cdc_ncmax88179_178a[ 1.421352458930] ehci_hcdusbcore: USB 2.0 'Enhanced' Host Controller (EHCI) Driverregistered new interface driver cdc_ether[ 1.428418465550] ehci-omapusbcore: OMAP-EHCI Host Controller registered new interface driverr815x[ 1.434726471615] usbcore: registered new interface driver cdc_wdmsmsc95xx[ 1.441013477990] usbcore: registered new interface driver usb-storagenet1080[ 1.448135484283] usbcore: registered new interface driver usbserialcdc_subset[ 1.454708490779] usbcore: registered new interface driver usbserial_genericzaurus[ 1.461848] usbserial: USB Serial support registered for generic[ 1.468527497093] usbcore: registered new interface driver ftdi_siocdc_ncm[ 1.474907503937] usbserialehci_hcd: USB Serial support registered for FTDI USB Serial Device2.0 'Enhanced' Host Controller (EHCI) Driver[ 1.487326510886] musbehci-hdrc musbomap: OMAP-hdrc.0.auto: Enabled SW babble controlEHCI Host Controller driver[ 1.494094517235] musb-hdrc musb-hdrc.0.autousbcore: Falied to request rx1.registered new interface driver cdc_wdm[ 1.500314523592] musb-hdrc musb-hdrc.0.autousbcore: musb_init_controller failed with status registered new interface driver usb-517storage[ 1.508785530485] platform musb-hdrc.0.autousbcore: Driver musb-hdrc requests probe deferralregistered new interface driver usbserial[ 1.537087] usbcore: registered new interface driver usbserial_generic[ 1.518940544375] musb-hdrc musb-hdrc.1.autousbserial: Enabled SW babble controlUSB Serial support registered for generic[ 1.525693550984] musbusbcore: registered new interface driver ftdi_sio[ 1.557337] usbserial: USB Serial support registered for FTDI USB Serial Device[ 1.569745] musb-hdrc musb-hdrc.10.auto: Falied to request rx1.Enabled SW babble control[ 1.531905576609] musb-hdrc musb-hdrc.0.auto: Falied to request rx1.[ 1.583022] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517[ 1.540202591267] platform musb-hdrc.10.auto: Driver musb-hdrc requests probe deferral[ 1.569971601463] mousedevmusb-hdrc musb-hdrc.1.auto: PS/2 mouse device common for all miceEnabled SW babble control[ 1.577964608210] input: timusb-hdrc musb-tsc as /devices/ocp.2/44e0d000hdrc.tscadc/TI-am335x-tsc/input/input0[ 1.588798] i2c /dev entries driverauto: Falied to request rx1.[ 1.595735614488] omap_wdtmusb-hdrc musb-hdrc.1.auto: OMAP Watchdog Timer Rev 0x01: initial timeout 60 secmusb_init_controller failed with status -517[ 1.605305622856] edmaplatform musb-dma-engine edma-dma-enginehdrc.1.0auto: allocated channel for 0:25Driver musb-hdrc requests probe deferral[ 1.612714653327] edma-dma-engine edma-dma-engine.0: allocated channel mousedev: PS/2 mouse device common for 0:24all mice[ 1.619977660663] omap_hsmmc 48060000.mmcinput: unable to get vmmc regulator ti-517[ 1tsc as /devices/ocp.626996] edma2/44e0d000.tscadc/TI-dmaam335x-engine edma-dma-enginetsc/input/input0[ 1.0: freeing channel for 24671593] i2c /dev entries driver[ 1.634058678569] edmaomap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec[ 1.688151] edma-dma-engine edma-dma-engine.0: freeing allocated channel for 0:25[ 1.640982695572] platform 48060000edma-dma-engine edma-dma-engine.mmc0: Driver omap_hsmmc requests probe deferralallocated channel for 0:24[ 1.649450702910] ledtrig-cpuomap_hsmmc 48060000.mmc: registered unable to indicate activity on CPUsget vmmc regulator -517[ 1.656349709845] edma-dma-engine edma-dma-engine.0: allocated freeing channel for 0:3624[ 1.663701716920] omapedma-dma-sham 53100000.shamengine edma-dma-engine.0: hw accel on OMAP rev 4.3freeing channel for 25[ 1.671745723910] omap-aes 53500000platform 48060000.aesmmc: OMAP AES hw accel rev: 3.2Driver omap_hsmmc requests probe deferral[ 1.678097732299] edmaledtrig-dma-engine edma-dma-engine.0cpu: allocated channel for 0:5registered to indicate activity on CPUs[ 1.685285739174] edma-dma-engine edma-dma-engine.0: allocated channel for 0:636[ 1.694601746525] usbcoreomap-sham 53100000.sham: registered new interface driver usbhidhw accel on OMAP rev 4.3[ 1.700502754574] usbhidomap-aes 53500000.aes: OMAP AES hw accel rev: USB HID core driver3.2[ 1.708722760718] usbcore: registered new interface driver sndedma-usbdma-audioengine edma-dma-engine.0: allocated channel for 0:5[ 1.718885768028] UDA134X SoC Audio Codecedma-dma-engine edma-dma-engine.0: allocated channel for 0:6[ 1.743837777248] davinci_evm sound.4: uda134x-hifi <-> 48038000.mcasp mapping okusbcore: registered new interface driver usbhid[ 1.757053783237] oprofileusbhid: no performance countersUSB HID core driver[ 1.762324791362] oprofileusbcore: using timer interrupt.registered new interface driver snd-usb-audio[ 1.767382801674] TCP: cubic registeredUDA134X SoC Audio Codec[ 1.770893824052] Initializing XFRM netlink socketdavinci_evm sound.4: uda134x-hifi <-> 48038000.mcasp mapping ok[ 1.775561837299] NEToprofile: Registered protocol family 17no performance counters[ 1.780316842555] NEToprofile: Registered protocol family 15using timer interrupt.[ 1.785106847618] canTCP: controller area network core (rev 20120528 abi 9)cubic registered[ 1.851130] Initializing XFRM netlink socket[ 1.791873855784] NET: Registered protocol family 2917[ 1.796721860546] canNET: raw Registered protocol (rev 20120528)family 15[ 1.801239865336] can: broadcast manager protocol controller area network core (rev 20120528 tabi 9)[ 1.807373872096] 8021qNET: 802.1Q VLAN Support v1.8Registered protocol family 29[ 1.811942876881] Key type dns_resolver registeredcan: raw protocol (rev 20120528)[ 1.817320881397] cpu cpu0can: cpu0 regulator not ready, retrybroadcast manager protocol (rev 20120528 t)[ 1.822835887520] platform cpufreq-cpu0.08021q: Driver cpufreq-cpu0 requests probe deferral[ 1802.8311421Q VLAN Support v1.8[ 1.892100] PM: CM3 Firmware Version = 0x187Key type dns_resolver registered[ 1.836357897496] ThumbEE CPU extension supported.cpu cpu0: cpu0 regulator not ready, retry[ 1.843598903001] omapplatform cpufreq-gpmc 50000000cpu0.gpmc0: GPMC revision 6.0Driver cpufreq-cpu0 requests probe deferral[ 1.849053911300] gpmc_mem_initPM: disabling cs 0 mapped at 0x0-0x1000000CM3 Firmware Version = 0x187[ 1.856959916487] NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit), 1024MiB, page size: 2048, OOB size: 64ThumbEE CPU extension supported.[ 1.869691923680] omap2omap-nandgpmc 50000000.gpmc: detected x8 NAND flashGPMC revision 6.0[ 1.874446929131] nandgpmc_mem_init: using OMAP_ECC_BCH8_CODE_HW ECC scheme[ 1.880115] omap2disabling cs 0 mapped at 0x0-nand: using custom ecc layout0x1000000[ 1.896952937019] vrtcNAND device: 1800 mV Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit), 1024MiB, page size: 2048, OOB size: 64[ 1.900445949754] vrtcomap2-nand: supplied by vindetected x8 NAND flash[ 1.907593954499] vionand: 1500 <--> 3300 mV at 1500 mV using OMAP_ECC_BCH8_CODE_HW ECC scheme[ 1.912384960175] vioomap2-nand: supplied by vinusing custom ecc layout[ 1.920058965136] vdd_mpu: 600 <9 cmdlinepart partitions found on MTD device omap2--> 1500 mV at 1137 mV nand.0[ 1.925258971955] vdd_mpuCreating 9 MTD partitions on "omap2-nand.0": supplied by vin[ 1.933197977663] vdd_core0x000000000000-0x000000020000 : 600 <--> 1500 mV at 1137 mV "SPL"[ 1.938357985117] vdd_core0x000000020000-0x000000040000 : supplied by vin"SPL.backup1"[ 1.945845993214] vdd30x000000040000-0x000000060000 : 5000 mV "SPL.backup2"[ 12.952174001160] vdig10x000000060000-0x000000080000 : 1200 <--> 2700 mV at 1800 mV "SPL.backup3"[ 12.957262009145] vdig10x000000080000-0x000000260000 : supplied by vin"u-boot"[ 12.964302018198] vdig20x000000260000-0x000000280000 : 1200 <"u-boot-> 1800 mV at 1800 mV env"[ 12.969266026420] vdig20x000000280000-0x0000002a0000 : supplied by vin"fdt"[ 12.976404033730] vpll0x0000002a0000-0x0000008a0000 : 1800 <--> 2500 mV at 1800 mV "kernel"[ 12.981280046645] vpll0x0000008a0000-0x000040000000 : supplied by vin"rootfs"[ 12.988291910559] vdacvrtc: 1800 <--> 2850 mV at 1800 mV [ 12.993313914394] vdacvrtc: supplied by vin[ 2.000264921442] vaux1vio: 1800 1500 <--> 2850 3300 mV at 1800 1500 mV [ 2.005430926452] vaux1vio: supplied by vin[ 2.012475934061] vaux2vdd_mpu: 1800 600 <--> 2800 1500 mV at 3300 1137 mV [ 2.017557939149] vaux2vdd_mpu: supplied by vin[ 2.025050947000] vaux33vdd_core: 1800 600 <--> 3300 1500 mV at 3300 1137 mV [ 2.030116952150] vaux33vdd_core: supplied by vin[ 2.037272959384] vmmcvdd3: 1800 <-5000 mV [ 2.965617] vdig1: 1200 <--> 3300 2700 mV at 3300 1800 mV [ 2.042150970598] vmmcvdig1: supplied by vin[ 2.060169977702] tps65910vdig2: 1200 <-rtc tps65910-rtc: rtc core: registered tps65910-rtc as rtc0> 1800 mV at 1800 mV [ 2.069590982663] at24 0-0050vdig2: 4096 byte 24c32 EEPROM, writable, 32 bytes/writesupplied by vin[ 2.078885989856] ina2xx 0vpll: 1800 <--0041> 2500 mV at 1800 mV [ 2.994840] vpll: power monitor ina226 (Rshunt = 10000 uOhm)supplied by vin[ 23.085885001759] omap_i2c 44e0b000.i2cvdac: bus 0 rev0.11 1800 <--> 2850 mV at 100 kHz1800 mV [ 23.092282006728] musbvdac: supplied by vin[ 3.013866] vaux1: 1800 <-hdrc musb-hdrc> 2850 mV at 1800 mV [ 3.0.auto018861] vaux1: Enabled SW babble controlsupplied by vin[ 23.101130026421] musbvaux2: 1800 <-hdrc musb-hdrc> 2800 mV at 3300 mV [ 3.0.auto031390] vaux2: MUSB HDRC host driversupplied by vin[ 23.107985038485] musbvaux33: 1800 <-hdrc musb-hdrc.0.auto: new USB bus registered, assigned bus number 1> 3300 mV at 3300 mV [ 23.116715043689] usb usb1vaux33: New USB device found, idVendor=1d6b, idProduct=0002supplied by vin[ 23.123969050823] usb usb1vmmc: New USB device strings: Mfr=3, Product=2, SerialNumber=11800 <--> 3300 mV at 3300 mV [ 23.131610055802] usb usb1vmmc: Product: MUSB HDRC host driversupplied by vin[ 23.136889073949] usb usb1tps65910-rtc tps65910-rtc: Manufacturerrtc core: Linux 3.12.10registered tps65910-divelk-2.0.0 musb-hcdrtc as rtc0[ 23.143904083252] usb usb1at24 0-0050: SerialNumber: musb-hdrc.0.auto4096 byte 24c32 EEPROM, writable, 32 bytes/write[ 23.150475092440] hub 1ina2xx 0-00041:1.0: USB hub foundpower monitor ina226 (Rshunt = 10000 uOhm)[ 23.154633099442] hub 1-omap_i2c 44e0b000.i2c: bus 0:1rev0.0: 1 port detected11 at 100 kHz[ 23.160314106054] musb-hdrc musb-hdrc.10.auto: Enabled SW babble control[ 23.169104114825] musb-hdrc musb-hdrc.10.auto: MUSB HDRC host driver[ 23.175903121563] musb-hdrc musb-hdrc.10.auto: new USB bus registered, assigned bus number 21[ 23.184622130296] usb usb2usb1: New USB device found, idVendor=1d6b, idProduct=0002[ 23.191804137543] usb usb2usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1[ 23.199538145203] usb usb2usb1: Product: MUSB HDRC host driver[ 23.204843150459] usb usb2usb1: Manufacturer: Linux 3.12.10-divelk-2.0.0 musb-hcd[ 23.211835157470] usb usb2usb1: SerialNumber: musb-hdrc.10.auto[ 23.218485164033] hub 21-0:1.0: USB hub found[ 23.222656168106] hub 21-0:1.0: 1 port detected[ 23.228149173859] edmamusb-dmahdrc musb-engine edma-dma-enginehdrc.1.0auto: allocated channel for 0:25Enabled SW babble control[ 23.235556182507] edmamusb-dmahdrc musb-engine edma-dma-enginehdrc.0: allocated channel for 0:24[ 2.331112] mmc0: host does not support reading read-only switch. assuming write-enable.[ 2.341865] mmc0: new high 1.auto: MUSB HDRC host driver[ 3.189383] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 2[ 3.198116] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002[ 3.205382] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1[ 3.213083] usb usb2: Product: MUSB HDRC host driver[ 3.218342] usb usb2: Manufacturer: Linux 3.12.10-divelk-2.0.0 musb-hcd[ 3.225358] usb usb2: SerialNumber: musb-hdrc.1.auto[ 3.231979] hub 2-0:1.0: USB hub found[ 3.236124] hub 2-0:1.0: 1 port detected[ 3.241593] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25[ 3.248906] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24[ 3.341278] mmc0: host does not support reading read-only switch. assuming write-enable.[ 3.352042] mmc0: new high speed SDHC card at address 1234[ 23.348752358955] mmcblk0: mmc0:1234 SA16G 14.6 GiB [ 23.353583363802] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6[ 23.360031370249] davinci_mdio 4a101000.mdio: detected phy mask ffffffbf[ 23.368787379000] libphy: 4a101000.mdio: probed[ 23.373191383422] davinci_mdio 4a101000.mdio: phy[6]: device 4a101000.mdio:06, driver SMSC LAN8710/LAN8720[ 23.383063393289] mmcblk0: p1 p2[ 23.388144398432] Detected MACID = 00:50:c2:1e:af:e0[ 23.399693409822] tps65910-rtc tps65910-rtc: setting system clock to 2014-10-03 10:2836:25 29 UTC (14123321051412332589)[ 23.415107425312] ALSA device list:[ 23.418279428505] #0: Diva Dacu[ 23.430401440728] kjournald starting. Commit interval 5 seconds[ 23.451373461578] EXT3-fs (mmcblk0p2): using internal journal[ 23.456953467158] EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode[ 23.464341474540] VFS: Mounted root (ext3 filesystem) on device 179:2.[ 23.473728483932] devtmpfs: mounted[ 23.477436487639] Freeing unused kernel memory: 368K (c085c000 - c08b8000)
INIT: version 2.88 booting
Starting udev
[ 34.372834382357] udevd[898954]: starting version 182[ 79.828921887444] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.[ 9 10.688192144522] cryptodev: driver 1.6 loaded.
Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory
bootlogd.
ALSA: Restoring mixer settings...
Configuring network interfaces... [ 1213.886710122234] net eth0: initializing cpsw version 1.12 (0)[ 1213.894834130330] net eth0: phy found : id is : 0x7c0f1[ 1213.909136144609] 8021q: adding VLAN 0 to HW filter on device eth0
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
[ 1716.053192362961] libphy: 4a101000.mdio:06 - Link is Up - 100/Full
Sending discover...
No lease, failing
U0007
Bureaucrats, dave_user, Administrators
8,184
edits
Retrieved from "https://wiki.dave.eu/index.php/Special:MobileDiff/3209...13123"

Navigation menu