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.
Tool/software: Linux
Hi yordan
The links for latest SDK are not working and finds error
I mean regarding compilation procedure and building
Kindly Please help help on the procedure to boot beagle bone boot booting with latest SDK and guide to build and deploy to sd card and check
Thank you
Deepak r
Hi Deepak,
Could you please clarify what device exactly you are using, is it BeagleBone or BeagleBoneBlack?
www.ti.com/.../beaglebn
www.ti.com/.../beaglebk
Note that only BeagleBoneBlack support the latest AM335x TI PSDK v04.00
BeagleBone is supported with AM335x SDK8:
http://software-dl.ti.com/sitara_linux/esd/AM335xSDK/08_00_00_00/index_FDS.html
Regards,
Pavel
Hi Yordan
Thanks for the reply!
1)Firstly I am using Beagle Bone black
2)I am using the get software link in the beagle bone black
I have attached the images
and I find the building also fails with the error
sdk source taken and tool chain
Even if I download bin folder also I don't find this script in SDK
I tried building the source code as well to check that I can copy the bin files to SD card But this building takes long time and also this building is not succesfull
Kindly please help on building and booting procedure of Beagle bone with latest SDK
THANK YOU
DEEPAK R
Hi pavel
Thanks for your response I installed the SDK latest
I am testing the i2c but i find the following error an you please help on this
Welcome to minicom 2.7
OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 22:42:33
Press CTRL-A Z for help on special keys
U-Boot SPL 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06)
U-Boot 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06), Build: jenkins-github_Bootloader-Builder-105
Watchdog enabled
I2C: ready
DRAM: 512 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment
Net: <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot: 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
** Invalid partition 3 **
** Invalid partition 4 **
** Invalid partition 5 **
** Invalid partition 6 **
** Invalid partition 7 **
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
switch to partitions #0, OK
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
gpio: pin 55 (gpio 55) value is 1
818 bytes read in 28 ms (28.3 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt...
gpio: pin 56 (gpio 56) value is 1
Running uname_boot ...
loading /boot/vmlinuz-3.8.13-bone70 ...
5617184 bytes read in 343 ms (15.6 MiB/s)
loading /boot/dtbs/3.8.13-bone70/am335x-boneblack.dtb ...
26098 bytes read in 37 ms (688.5 KiB/s)
loading /boot/initrd.img-3.8.13-bone70 ...
2867606 bytes read in 190 ms (14.4 MiB/s)
debug: [console=ttyO0,115200n8 root=UUID=9014ebde-a021-4f54-9a15-c13084d61e2f ro rootfstype=ext4 rootwait fixrtc quiet init=/lib/syst.
debug: [bootz 0x82000000 0x88080000:2bc196 0x88000000] ...
Kernel image @ 0x82000000 [ 0x000000 - 0x55b620 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8fd43000, end 8ffff196 ... OK
Loading Device Tree to 8fd39000, end 8fd425f1 ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.372928] omap2_mbox_probe: platform not supported
[ 0.527844] tps65217-bl tps65217-bl: no platform data provided
[ 0.591214] bone-capemgr bone_capemgr.9: slot #0: No cape found
[ 0.628322] bone-capemgr bone_capemgr.9: slot #1: No cape found
[ 0.665430] bone-capemgr bone_capemgr.9: slot #2: No cape found
[ 0.702539] bone-capemgr bone_capemgr.9: slot #3: No cape found
[ 0.718269] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)
[ 0.727843] bone-capemgr bone_capemgr.9: slot #6: Failed verification
debian@beaglebone:/dev$ i2cdetect -l
i2c-0 i2c OMAP I2C adapter I2C adapter
i2c-1 i2c OMAP I2C adapter I2C adapter
debian@beaglebone:/dev$ i2cdetect -r 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0 using read byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: UU -- -- -- -- -- -- --
debian@beaglebone:/dev$ i2cset -y 2 0x77 0xf4 0x34
Error: Could not open file `/dev/i2c-2' or `/dev/i2c/2': No such file or directory
debian@beaglebone:/dev$ i2cset -y 1 0x77 0xf4 0x34
Error: Write failed
debian@beaglebone:/dev$ i2cset -y 2 0x77 0xf4 0x34
Error: Could not open file `/dev/i2c-2' or `/dev/i2c/2': No such file or directory
debian@beaglebone:/dev$ i2cdump -y 2 0x77
No size specified (using byte-data access)
Error: Could not open file `/dev/i2c-2' or `/dev/i2c/2': No such file or directory
debian@beaglebone:/dev$ i2cdump -y 1 0x77
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
80: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
90: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
a0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
b0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
c0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
d0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
e0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
f0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
debian@beaglebone:/dev$
debian@beaglebone:/dev$ i2cset -y 0 0x77
Usage: i2cset [-f] [-y] [-m MASK] I2CBUS CHIP-ADDRESS DATA-ADDRESS [VALUE] ... [MODE]
I2CBUS is an integer or an I2C bus name
ADDRESS is an integer (0x03 - 0x77)
MODE is one of:
c (byte, no value)
b (byte data, default)
w (word data)
i (I2C block data)
s (SMBus block data)
Append p for SMBus PEC
debian@beaglebone:/dev$
debian@beaglebone:/dev$
debian@beaglebone:/dev$ i2cset -y 0 0x77 0xf4 0x34
Error: Write failed
debian@beaglebone:/dev$ i2cset -y 1 0x77 0xf4 0x34
Error: Write failed
debian@beaglebone:/dev$ i2cdetect -r 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1 using read byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
debian@beaglebone:/dev$
debian@beaglebone:/dev$ i2cdetect -r 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0 using read byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: UU -- -- -- -- -- -- --
debian@beaglebone:/dev$ i2cset -y 0 0x70 0xf4 0x34
Error: Could not set address to 0x70: Device or resource busy
debian@beaglebone:/dev$ i2cset -y 0 0x50 0xf4 0x34
Error: Could not set address to 0x50: Device or resource busy
debian@beaglebone:/dev$ i2cset -y 0 0x54 0xf4 0x34
Error: Write failed
debian@beaglebone:/dev$ i2cset -y 0 0x24 0xf4 0x34
Error: Could not set address to 0x24: Device or resource busy
debian@beaglebone:/dev$
debian@beaglebone:/dev$ i2cset -y 0 0x30 0xf4 0x34
Error: Write failed
debian@beaglebone:/dev$ i2cset -y 0 0x34 0xf4 0x34
Error: Could not set address to 0x34: Device or resource busy
debian@beaglebone:/dev$ i2cset -y 1 0x54 0xf4 0x34
Error: Could not set address to 0x54: Device or resource busy
debian@beaglebone:/dev$ i2cset -y 1 0x55 0xf4 0x34
Error: Could not set address to 0x55: Device or resource busy
debian@beaglebone:/dev$ i2cset -y 1 0x56 0xf4 0x34
Error: Could not set address to 0x56: Device or resource busy
debian@beaglebone:/dev$ i2cset -y 1 0x57 0xf4 0x34
Error: Could not set address to 0x57: Device or resource busy
debian@beaglebone:/dev$ i2cset -y 1 0x58 0xf4 0x34
Error: Write failed
Can you please help on this i want to test the eeprom which is present internally
Thank you
Deepak R
Deepak,
deepak r said:I installed the SDK latest
deepak r said:U-Boot SPL 2015.01
deepak r said:loading /boot/vmlinuz-3.8.13-bone70
deepak r said:debian@beaglebone
The latest TI SDK is based on Arago linux (not Debian), and comes with u-boot 2017.01 (not 2015.01) and kernel 4.9.28 (not 3.8.13).
From the log you shared, it seems that you are not using TI SDK but some Debian software. Debian software is available at beaglebone community site and is supported by beaglebone community support page.
If you need help here in TI forum, you should use TI SDK.
Regards,
Pavel
Are you trying to boot the SDK from an SD Card? If so, you need to hold down the user button (S2) before applying power. Or erase Debian from the eMMC.
Steve K.
Hi Pavel
I tried doing it ITS BOOTING but iam not able to write to eeprom present internally I have attached the logs
let me know if anything to be modified If so please mention the steps with building and compiling
KIndly please help on this Let me know Need your support
1.538476] tilcdc 4830e000.lcdc: No connectors reported connected with modes
[ 1.545706] [drm] Cannot find any crtc or sizes - going 1024x768
[ 1.559728] Console: switching to colour frame buffer device 128x48
[ 1.570871] tilcdc 4830e000.lcdc: fb0: frame buffer device
[ 1.602643] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
[ 1.722866] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 100 kHz
[ 1.730582] hctosys: unable to open rtc device (rtc0)
[ 1.736265] ALSA device list:
[ 1.739255] No soundcards found.
[ 1.746522] mmc1: new high speed MMC card at address 0001
[ 1.753435] mmcblk1: mmc1:0001 MMC04G 3.66 GiB
[ 1.758234] mmcblk1boot0: mmc1:0001 MMC04G partition 1 1.00 MiB
[ 1.765170] mmcblk1boot1: mmc1:0001 MMC04G partition 2 1.00 MiB
[ 1.774352] mmcblk1: p1 p2
[ 3.543436] EXT4-fs (mmcblk0p2): recovery complete
[ 3.556358] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 3.564702] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 3.581142] devtmpfs: mounted
[ 3.588326] Freeing unused kernel memory: 1024K (c0b00000 - c0c00000)
[ 3.892685] systemd[1]: System time before build time, advancing clock.
[ 3.980464] systemd[1]: systemd 230 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTS)
[ 3.999498] systemd[1]: Detected architecture arm.
Welcome to Arago 2017.05!
[ 4.033289] systemd[1]: Set hostname to <am335x-evm>.
[ 4.350983] systemd[1]: [/lib/systemd/system/gadget-init.service:15] Unknown lvalue 'ExecStopPre' in section 'Service'
[ 4.624956] systemd[1]: sockets.target: Found ordering cycle on sockets.target/start
[ 4.632929] systemd[1]: sockets.target: Found dependency on avahi-daemon.socket/start
[ 4.640823] systemd[1]: sockets.target: Found dependency on sysinit.target/start
[ 4.648418] systemd[1]: sockets.target: Found dependency on alignment.service/start
[ 4.656153] systemd[1]: sockets.target: Found dependency on basic.target/start
[ 4.663438] systemd[1]: sockets.target: Found dependency on sockets.target/start
[ SKIP ] Ordering cycle found, skipping Avah...S/DNS-SD Stack Activation Socket
[ SKIP ] Ordering cycle found, skipping alignment.service
[ OK ] Started Forward Password Requests to Wall Directory Watch.
[ OK ] Created slice System Slice.
[ OK ] Started Dispatch Password Requests to Console Directory Watch.
[ OK ] Listening on Journal Socket.
[ OK ] Listening on udev Kernel Socket.
Mounting POSIX Message Queue File System...
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
Starting Create Static Device Nodes in /dev...
Starting Setup Virtual Console...
Mounting Debug File System...
[ OK ] Reached target Remote File Systems.
[ OK ] Listening on udev Control Socket.
[ OK ] Listening on Syslog Socket.
[ OK ] Listening on Journal Socket (/dev/log).
[ OK ] Created slice system-getty.slice.
Starting Load Kernel Modules...
[ 5.210860] cryptodev: loading out-of-tree module taints kernel.
[ 5.221112] cryptodev: driver 1.8 loaded.
Starting Journal Service...
[ OK ] Created slice system-serial\x2dgetty.slice.
[ OK ] Reached target Swap.
Mounting Temporary Directory...
[ OK ] Listening on Network Service Netlink Socket.
[ OK ] Reached target Paths.
Starting Remount Root and Kernel File Systems...
[ OK ] Created slice User and Session Slice.
[ OK ] Reached target Slices.
[ 5.509040] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ OK ] Mounted Debug File System.
[ OK ] Mounted POSIX Message Queue File System.
[ OK ] Mounted Temporary Directory.
[ OK ] Started Journal Service.
[ OK ] Started Create Static Device Nodes in /dev.
[ OK ] Started Setup Virtual Console.
[ OK ] Started Load Kernel Modules.
[ OK ] Started Remount Root and Kernel File Systems.
Starting udev Coldplug all Devices...
Starting Apply Kernel Variables...
Mounting Configuration File System...
Starting udev Kernel Device Manager...
[ OK ] Reached target Local File Systems (Pre).
Mounting /media/ram...
Mounting /var/volatile...
Starting Flush Journal to Persistent Storage...
[ OK ] Mounted Configuration File System.
[ OK ] Mounted /var/volatile.
[ OK ] Mounted /media/ram.
[ OK ] Started Apply Kernel Variables.
[ OK ] Started udev Kernel Device Manager.
[ 6.432693] systemd-journald[101]: Received request to flush runtime journal from PID 1
[ OK ] Started Flush Journal to Persistent Storage.
[ OK ] Reached target Local File Systems.
Starting Create Volatile Files and Directories...
Starting Load/Save Random Seed...
[ OK ] Started Load/Save Random Seed.
[ OK ] Started Create Volatile Files and Directories.
Starting Network Time Synchronization...
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Started Network Time Synchronization.
[ OK ] Reached target System Time Synchronized.
Starting Synchronize System and HW clocks...
[FAILED] Failed to start Synchronize System and HW clocks.
See 'systemctl status sync-clocks.service' for details.
[ 7.752641] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[ 7.916198] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[ OK ] Started udev Coldplug all Devices.
[ OK ] Found device /dev/ttyS0.
[ OK ] Reached target System Initialization.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Listening on dropbear.socket.
[ OK ] Listening on RPCbind Server Activation Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting Login Service...
[ OK ] Started D-Bus System Message Bus.
[ 8.778737] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[ 8.880092] omap-aes 53500000.aes: will run requests pump with realtime priority
[ 8.957656] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[ 9.040593] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 9.109811] [drm] Initialized pvr 1.14.3699939 20110701 on minor 1
[ 9.163279] remoteproc remoteproc0: wkup_m3 is available
[ 9.285204] PM: Cannot get wkup_m3_ipc handle
[ 9.291000] remoteproc remoteproc0: powering up wkup_m3
[ 9.341186] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 224344
[ 9.341451] remoteproc remoteproc0: remote processor wkup_m3 is now up
[ 9.341480] wkup_m3_ipc 44e11324.wkup_m3_ipc: CM3 Firmware Version = 0x192
Starting Network Service...
[ 9.721118] PM: bootloader does not support rtc-only!
Starting uim-sysfs.service...
[ 9.796577] asoc-simple-card sound: hdmi-hifi.0 <-> 48038000.mcasp mapping ok
Starting Telephony service...
[ OK ] Started Kernel Logging Service.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Reached target Timers.
[ OK ] Started System Logging Service.
[ 10.195678] net eth0: initializing cpsw version 1.12 (0)
[ 10.201044] net eth0: initialized cpsw ale version 1.4
Starting Print notice about GPLv3 packages...
[ 10.352167] net eth0: ALE Table size 1024
[ OK ] Started Network Service.
[ 10.522740] SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, )
[ 10.646161] Bluetooth: Core ver 2.22
[ 10.646248] NET: Registered protocol family 31
[ 10.646252] Bluetooth: HCI device and connection manager initialized
[ 10.646272] Bluetooth: HCI socket layer initialized
[ 10.646281] Bluetooth: L2CAP socket layer initialized
[ 10.646311] Bluetooth: SCO socket layer initialized
[ OK ] Found device /dev/ttyS3.
[ 11.406611] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 11.680104] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 12.018659] EXT4-fs (mmcblk1p2): recovery complete
[ 12.059971] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
[ 12.257907] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ OK ] Started Telephony service.
[ OK ] Started Login Service.
[ OK ] Found device /dev/mmcblk0p1.
Starting Start USB gadget...
[ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[ OK ] Reached target Network.
Starting Enable and configure wl18xx bluetooth stack...
Starting Lightning Fast Webserver With Light System Requirements...
Starting Simple Network Management Protocol (SNMP) Daemon....
Starting Permit User Sessions...
[ OK ] Started strongSwan IPsec IKEv1/IKEv2 daemon using ipsec.conf.
Starting Network Name Resolution...
[ OK ] Started Lightning Fast Webserver With Light System Requirements.
[ OK ] Started Permit User Sessions.
[ OK ] Started Network Name Resolution.
[ OK ] Started Enable and configure wl18xx bluetooth stack.
[ 14.986574] udc-core: couldn't find an available UDC - added [g_multi] to list of pending drivers
[ OK ] Started Serial Getty on ttyS0.
[ OK ] Started Getty on tty1.
[ OK ] Started Serial Getty on ttyS3.
[ 15.409759] NET: Registered protocol family 15
[FAILED] Failed to start Start USB gadget.
See 'systemctl status gadget-init.service' for details.
[ 16.369407] Initializing XFRM netlink socket
[ OK ] Started Simple Network Management Protocol (SNMP) Daemon..
[ 16.761904] random: crng init done
[ 17.935310] 47401300.usb-phy supply vcc not found, using dummy regulator
[ 18.004169] usbcore: registered new interface driver usbfs
[ 18.004233] usbcore: registered new interface driver hub
[ 18.004357] usbcore: registered new device driver usb
[ 18.312973] 47401b00.usb-phy supply vcc not found, using dummy regulator
[ 18.570069] using random self ethernet address
[ 18.596853] using random host ethernet address
[ 18.601351] using host ethernet address: 78:A5:04:FD:E2:D2[ 18.695540] using random self ethernet address
[ 18.700032] using random host ethernet address
[ 18.772194] using host ethernet address: 78:A5:04:FD:E2:D2[ 18.834574] usb0: HOST MAC 78:a5:04:fd:e2:d2
[ 18.878166] usb0: MAC de:68:a3:b8:25:74
[ 18.973277] ti-pruss 4a300000.pruss: creating PRU cores and other child platform devices
[ 18.974771] irq: no irq domain found for /ocp/pruss_soc_bus@4a326000/pruss@4a300000/intc@4a320000 !
[ 18.975306] irq: no irq domain found for /ocp/pruss_soc_bus@4a326000/pruss@4a300000/intc@4a320000 !
[ 19.199241] Mass Storage Function, version: 2009/09/11
[ 19.231209] LUN: removable file: (no medium)
[ 19.293009] LUN: removable read only file: /dev/mmcblk0p1
[ 19.368714] Number of LUNs=1
[ 19.394827] g_multi gadget: Multifunction Composite Gadget
[ 19.476075] g_multi gadget: g_multi ready
[ 19.586591] musb-hdrc musb-hdrc.1: MUSB HDRC host driver
[ 19.594077] remoteproc remoteproc1: 4a334000.pru0 is available
[ 19.594151] pru-rproc 4a334000.pru0: PRU rproc node /ocp/pruss_soc_bus@4a326000/pruss@4a300000/pru@4a334000 probed successfully
[ 19.630479] remoteproc remoteproc2: 4a338000.pru1 is available
[ 19.630571] pru-rproc 4a338000.pru1: PRU rproc node /ocp/pruss_soc_bus@4a326000/pruss@4a300000/pru@4a338000 probed successfully
[ 19.905734] g_multi gadget: high-speed config #2: Multifunction with CDC ECM
[ 19.953624] musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 1
[ 20.029304] hub 1-0:1.0: USB hub found
[ 20.051532] hub 1-0:1.0: 1 port detected
_____ _____ _ _
| _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_
| | _| .'| . | . | | __| _| . | | | -_| _| _|
|__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|
|___| |___|
Arago Project http://arago-project.org am335x-evm ttyS0
Arago 2017.05 am335x-evm ttyS0
am335x-evm login: ***************************************************************
***************************************************************
NOTICE: This file system contains the following GPLv3 packages:
autoconf
binutils
cpp-symlinks
cpp
dosfstools
g++-symlinks
g++
gawk-dev
gawk
gcc-symlinks
gcc
gdb
gdbserver
gstreamer1.0-libav
hidapi
libcairo-perf-utils
libgmp10
libidn11
libmpc3
libmpfr4
libreadline-dev
libreadline6
m4-dev
m4
make
nettle
swig-dev
swig
If you do not wish to distribute GPLv3 components please remove
the above packages prior to distribution. This can be done using
the opkg remove command. i.e.:
opkg remove <package>
Where <package> is the name printed in the list above
NOTE: If the package is a dependency of another package you
will be notified of the dependent packages. You should
use the --force-removal-of-dependent-packages option to
also remove the dependent packages as well
***************************************************************
***************************************************************
[ 22.588760] PVR_K: UM DDK-(3699939) and KM DDK-(3699939) match. [ OK ]
_____ _____ _ _
| _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_
| | _| .'| . | . | | __| _| . | | | -_| _| _|
|__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|
|___| |___|
root@am335x-evm:/dev# ls
autofs ptyr6 tty16 ttyq9
bc_example ptyr7 tty17 ttyqa
block ptyr8 tty18 ttyqb
bus ptyr9 tty19 ttyqc
char ptyra tty2 ttyqd
console ptyrb tty20 ttyqe
cpu_dma_latency ptyrc tty21 ttyqf
crypto ptyrd tty22 ttyr0
disk ptyre tty23 ttyr1
dri ptyrf tty24 ttyr2
fb ptys0 tty25 ttyr3
fb0 ptys1 tty26 ttyr4
fd ptys2 tty27 ttyr5
full ptys3 tty28 ttyr6
gpiochip0 ptys4 tty29 ttyr7
gpiochip1 ptys5 tty3 ttyr8
gpiochip2 ptys6 tty30 ttyr9
gpiochip3 ptys7 tty31 ttyra
hwrng ptys8 tty32 ttyrb
i2c-0 ptys9 tty33 ttyrc
i2c-2 ptysa tty34 ttyrd
initctl ptysb tty35 ttyre
input ptysc tty36 ttyrf
kmem ptysd tty37 ttys0
kmsg ptyse tty38 ttys1
log ptysf tty39 ttys2
loop-control ptyt0 tty4 ttys3
loop0 ptyt1 tty40 ttys4
loop1 ptyt2 tty41 ttys5
loop2 ptyt3 tty42 ttys6
loop3 ptyt4 tty43 ttys7
loop4 ptyt5 tty44 ttys8
loop5 ptyt6 tty45 ttys9
loop6 ptyt7 tty46 ttysa
loop7 ptyt8 tty47 ttysb
mem ptyt9 tty48 ttysc
memory_bandwidth ptyta tty49 ttysd
mmcblk0 ptytb tty5 ttyse
mmcblk0p1 ptytc tty50 ttysf
mmcblk0p2 ptytd tty51 ttyt0
mmcblk1 ptyte tty52 ttyt1
mmcblk1boot0 ptytf tty53 ttyt2
mmcblk1boot1 ptyu0 tty54 ttyt3
mmcblk1p1 ptyu1 tty55 ttyt4
mmcblk1p2 ptyu2 tty56 ttyt5
mqueue ptyu3 tty57 ttyt6
network_latency ptyu4 tty58 ttyt7
network_throughput ptyu5 tty59 ttyt8
null ptyu6 tty6 ttyt9
port ptyu7 tty60 ttyta
psaux ptyu8 tty61 ttytb
ptmx ptyu9 tty62 ttytc
ptp0 ptyua tty63 ttytd
pts ptyub tty7 ttyte
ptya0 ptyuc tty8 ttytf
ptya1 ptyud tty9 ttyu0
ptya2 ptyue ttyGS0 ttyu1
ptya3 ptyuf ttyS0 ttyu2
ptya4 ptyv0 ttyS1 ttyu3
ptya5 ptyv1 ttyS2 ttyu4
ptya6 ptyv2 ttyS3 ttyu5
ptya7 ptyv3 ttyS4 ttyu6
ptya8 ptyv4 ttyS5 ttyu7
ptya9 ptyv5 ttyS6 ttyu8
ptyaa ptyv6 ttyS7 ttyu9
ptyab ptyv7 ttyS8 ttyua
ptyac ptyv8 ttyS9 ttyub
ptyad ptyv9 ttya0 ttyuc
ptyae ptyva ttya1 ttyud
ptyaf ptyvb ttya2 ttyue
ptyb0 ptyvc ttya3 ttyuf
ptyb1 ptyvd ttya4 ttyv0
ptyb2 ptyve ttya5 ttyv1
ptyb3 ptyvf ttya6 ttyv2
ptyb4 ptyw0 ttya7 ttyv3
ptyb5 ptyw1 ttya8 ttyv4
ptyb6 ptyw2 ttya9 ttyv5
ptyb7 ptyw3 ttyaa ttyv6
ptyb8 ptyw4 ttyab ttyv7
ptyb9 ptyw5 ttyac ttyv8
ptyba ptyw6 ttyad ttyv9
ptybb ptyw7 ttyae ttyva
ptybc ptyw8 ttyaf ttyvb
ptybd ptyw9 ttyb0 ttyvc
ptybe ptywa ttyb1 ttyvd
ptybf ptywb ttyb2 ttyve
ptyc0 ptywc ttyb3 ttyvf
ptyc1 ptywd ttyb4 ttyw0
ptyc2 ptywe ttyb5 ttyw1
ptyc3 ptywf ttyb6 ttyw2
ptyc4 ptyx0 ttyb7 ttyw3
ptyc5 ptyx1 ttyb8 ttyw4
ptyc6 ptyx2 ttyb9 ttyw5
ptyc7 ptyx3 ttyba ttyw6
ptyc8 ptyx4 ttybb ttyw7
ptyc9 ptyx5 ttybc ttyw8
ptyca ptyx6 ttybd ttyw9
ptycb ptyx7 ttybe ttywa
ptycc ptyx8 ttybf ttywb
ptycd ptyx9 ttyc0 ttywc
ptyce ptyxa ttyc1 ttywd
ptycf ptyxb ttyc2 ttywe
ptyd0 ptyxc ttyc3 ttywf
ptyd1 ptyxd ttyc4 ttyx0
ptyd2 ptyxe ttyc5 ttyx1
ptyd3 ptyxf ttyc6 ttyx2
ptyd4 ptyy0 ttyc7 ttyx3
ptyd5 ptyy1 ttyc8 ttyx4
ptyd6 ptyy2 ttyc9 ttyx5
ptyd7 ptyy3 ttyca ttyx6
ptyd8 ptyy4 ttycb ttyx7
ptyd9 ptyy5 ttycc ttyx8
ptyda ptyy6 ttycd ttyx9
ptydb ptyy7 ttyce ttyxa
ptydc ptyy8 ttycf ttyxb
ptydd ptyy9 ttyd0 ttyxc
ptyde ptyya ttyd1 ttyxd
ptydf ptyyb ttyd2 ttyxe
ptye0 ptyyc ttyd3 ttyxf
ptye1 ptyyd ttyd4 ttyy0
ptye2 ptyye ttyd5 ttyy1
ptye3 ptyyf ttyd6 ttyy2
ptye4 ptyz0 ttyd7 ttyy3
ptye5 ptyz1 ttyd8 ttyy4
ptye6 ptyz2 ttyd9 ttyy5
ptye7 ptyz3 ttyda ttyy6
ptye8 ptyz4 ttydb ttyy7
ptye9 ptyz5 ttydc ttyy8
ptyea ptyz6 ttydd ttyy9
ptyeb ptyz7 ttyde ttyya
ptyec ptyz8 ttydf ttyyb
ptyed ptyz9 ttye0 ttyyc
ptyee ptyza ttye1 ttyyd
ptyef ptyzb ttye2 ttyye
ptyp0 ptyzc ttye3 ttyyf
ptyp1 ptyzd ttye4 ttyz0
ptyp2 ptyze ttye5 ttyz1
ptyp3 ptyzf ttye6 ttyz2
ptyp4 ram0 ttye7 ttyz3
ptyp5 ram1 ttye8 ttyz4
ptyp6 ram10 ttye9 ttyz5
ptyp7 ram11 ttyea ttyz6
ptyp8 ram12 ttyeb ttyz7
root@am335x-evm:/dev#
root@am335x-evm:/dev#
root@am335x-evm:/dev#
root@am335x-evm:/dev# i2cdetect -l
i2c-2 i2c OMAP I2C adapter I2C adapter
i2c-0 i2c OMAP I2C adapter I2C adapter
root@am335x-evm:/dev# i2cdetect -r 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0 using read byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: UU -- -- -- -- -- -- --
root@am335x-evm:/dev# i2cset -y 2 0x77 0xf4 0x34
Error: Write failed
root@am335x-evm:/dev#
root@am335x-evm:/dev# i2cdump -y 2 0x77
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
80: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
90: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
a0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
b0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
c0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
d0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
e0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
f0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
root@am335x-evm:/dev# i2cset -y 2 0x77 0xf4 0x34
Error: Write failed
root@am335x-evm:/dev#
root@am335x-evm:/dev#
root@am335x-evm:/dev# i2cdetect -r 2
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-2 using read byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@am335x-evm:/dev#
root@am335x-evm:/dev#
root@am335x-evm:/dev#
root@am335x-evm:/dev# i2cdetect -r 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0 using read byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: UU -- -- -- -- -- -- --
root@am335x-evm:/dev#
root@am335x-evm:/dev#
root@am335x-evm:/dev# i2cset -y 0 0x77 0xf4 0x34
Error: Write failed
root@am335x-evm:/dev# i2cset -y 0 0x50 0xf4 0x34
Error: Could not set address to 0x50: Device or resource busy
root@am335x-evm:/dev#
root@am335x-evm:/dev# i2cset -y 0 0x24 0xf4 0x34
Error: Could not set address to 0x24: Device or resource busy
root@am335x-evm:/dev# i2cset -y 0 0x34 0xf4 0x34
Error: Could not set address to 0x34: Device or resource busy
root@am335x-evm:/dev#
root@am335x-evm:/dev#
root@am335x-evm:/dev# i2cset -y 0 0x50 0xf4 0x34
Error: Could not set address to 0x50: Device or resource busy
root@am335x-evm:/dev#
root@am335x-evm:/dev#
root@am335x-evm:/dev# i2cdetect -l
i2c-2 i2c OMAP I2C adapter I2C adapter
i2c-0 i2c OMAP I2C adapter I2C adapter
root@am335x-evm:/dev#
WAiting for the solution to test internal eeprom pls support using i2c tools his helps me on my further work