Tool/software: Linux
Hi Team
I have used the latest SDK to flash the Beagle Bone
I have attached the logs not able to test the internal eeprom present not sure how to enable that as well KINDLY PLEASE HELP
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
please let me know the procedure to test this and how to make modification if necessary on build AND BUILDING PROCEDURE
Thank you
Deepak R