[beagleboard] U-boot i2c write commands

Just want to confirm that the current U-Boot, 2014.04, still has problems with the i2c nm and i2c mm commands (unable to write to the ID EEPROM on the BBB baseboard).

Or, I'm not doing something correct.

Thanks,
Ross

Did you un-write-protect the board eeprom?

Regards,

Pulled pin 7 (WP) to ground, yes. I've made the changes to U-Boot to skip the check of the ID EEPROM and I'm now, through U-Boot, trying to program the baseboard ID EEPROM with a proper signature. Linux version 3.8.13-bone35.1 starts to boot, but issues a Kernel Panic as seen here in the console output:

[ 34.944873] mmcblk0: mmc0:aaaa SU16G 14.8 GiB
[ 34.952745] mmcblk0: p1 p2 < p5 p6 >
[ 34.956681] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[ 34.963179] davinci_mdio 4a101000.mdio: no live phy, scanning all
[ 34.971286] davinci_mdio: probe of 4a101000.mdio failed with error -5
[ 34.978381] Detected MACID = c8:a0:30:a0:fc:81
[ 34.982993] Unhandled fault: external abort on non-linefetch (0x1008) at 0xe0898000
[ 34.991209] Internal error: : 1008 [#1] SMP ARM
[ 34.995953] Modules linked in:
[ 34.999158] CPU: 0 Not tainted (3.8.13-bone35.1 #6)
[ 35.004641] PC is at cpsw_probe+0x528/0xbd8
[ 35.009034] LR is at ioremap_page_range+0x120/0x17c
[ 35.014144] pc : [<c0402cac>] lr : [<c02f3b38>] psr: a0000113
[ 35.014144] sp : df053e18 ip : df04e260 fp : e0898000
[ 35.026168] r10: de26cd90 r9 : de264ca0 r8 : 00000002
[ 35.031639] r7 : 00000000 r6 : df112600 r5 : df112610 r4 : de26c800
[ 35.038475] r3 : df10b840 r2 : c0402c90 r1 : 4a100e13 r0 : e0898000
[ 35.045313] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
[ 35.052968] Control: 10c5387d Table: 80004019 DAC: 00000015
[ 35.058985] Process swapper/0 (pid: 1, stack limit = 0xdf052240)
[ 35.065276] Stack: (0xdf053e18 to 0xdf054000)
[ 35.069838] 3e00: 00000000 000000d0
[ 35.078407] 3e20: c0150558 00000007 de26ca98 c0621010 df051640 00000000 df053e4c 00000020
[ 35.086977] 3e40: 00000008 c0150888 22222222 22222222 22222222 de26bd08 de26bc88 de26bc88
[ 35.095546] 3e60: df053e90 c0150770 00000000 de26bc88 df111148 de2655c0 00000000 c01513c0
[ 35.104115] 3e80: df0484b8 c005ed84 00000000 00000003 df111148 00000000 c09b0754 df112610
[ 35.112684] 3ea0: df112644 c09b0754 c038b60c 000000f3 00000000 c0926104 00000000 c038c5e4
[ 35.121254] 3ec0: c038c5d0 c038b4c0 df112610 df112644 c09b0754 c038b674 00000000 df053ee8
[ 35.129824] 3ee0: c09b0754 c0389d0c df048478 df104280 c09b0754 c09b0754 de2655c0 c09a5e50
[ 35.138394] 3f00: 00000000 c038ac70 c080c32a df001288 c09b0754 c0932f10 c0945c24 c09cd780
[ 35.146962] 3f20: 000000f3 c038bb48 00000000 00000007 c0932f10 c0945c24 c09cd780 000000f3
[ 35.155532] 3f40: c0926104 c0008890 c0926104 0001e268 c0945c50 00000008 00000007 c0932f10
[ 35.164101] 3f60: c0945c24 c09cd780 000000f3 c0900274 c0932f18 c0900918 00000007 00000007
[ 35.172669] 3f80: c0900274 00000000 00000000 c0616114 00000000 00000000 00000000 00000000
[ 35.181237] 3fa0: 00000000 c061611c 00000000 c000d918 00000000 00000000 00000000 00000000
[ 35.189804] 3fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 35.198373] 3fe0: 00000000 00000000 00000000 00000000 00000013 00000000 cd4f4f77 e77d1deb
[ 35.206956] [<c0402cac>] (cpsw_probe+0x528/0xbd8) from [<c038c5e4>] (platform_drv_probe+0x14/0x18)
[ 35.216358] [<c038c5e4>] (platform_drv_probe+0x14/0x18) from [<c038b4c0>] (driver_probe_device+0xa0/0x1ec)
[ 35.226478] [<c038b4c0>] (driver_probe_device+0xa0/0x1ec) from [<c038b674>] (__driver_attach+0x68/0x8c)
[ 35.236325] [<c038b674>] (__driver_attach+0x68/0x8c) from [<c0389d0c>] (bus_for_each_dev+0x50/0x88)
[ 35.245807] [<c0389d0c>] (bus_for_each_dev+0x50/0x88) from [<c038ac70>] (bus_add_driver+0xcc/0x21c)
[ 35.255289] [<c038ac70>] (bus_add_driver+0xcc/0x21c) from [<c038bb48>] (driver_register+0x9c/0x12c)
[ 35.264773] [<c038bb48>] (driver_register+0x9c/0x12c) from [<c0008890>] (do_one_initcall+0x90/0x160)
[ 35.274350] [<c0008890>] (do_one_initcall+0x90/0x160) from [<c0900918>] (kernel_init_freeable+0xf8/0x1c4)
[ 35.284382] [<c0900918>] (kernel_init_freeable+0xf8/0x1c4) from [<c061611c>] (kernel_init+0x8/0xe4)
[ 35.293870] [<c061611c>] (kernel_init+0x8/0xe4) from [<c000d918>] (ret_from_fork+0x14/0x3c)
[ 35.302621] Code: e59f1660 ebfe16b5 ea00014d e584b5c0 (e59b3000)
[ 35.309007] ---[ end trace ae038e177bf1f93f ]---
[ 35.314342] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 35.314342]

This is our custom board and I'm trying to eliminate any unknowns by getting a good ID EEPROM signature setup up.

So, is U-Boot good to go, or should I get an older version from a BBW to get the EEPROM programmed?

Thanks,
Ross

Just want to confirm that the current U-Boot, 2014.04, still has problems
with the i2c nm and i2c mm commands (unable to write to the ID EEPROM on
the
BBB baseboard).

Did you un-write-protect the board eeprom?

Regards,

Pulled pin 7 (WP) to ground, yes. I've made the changes to U-Boot to skip
the check of the ID EEPROM and I'm now, through U-Boot, trying to program
the baseboard ID EEPROM with a proper signature. Linux version
3.8.13-bone35.1 starts to boot, but issues a Kernel Panic as seen here in
the console output:

Odd, it's working fine here: ( 3.8.13-bone47)

This is our custom board and I'm trying to eliminate any unknowns by getting
a good ID EEPROM signature setup up.

So, is U-Boot good to go, or should I get an older version from a BBW to get
the EEPROM programmed?

Is this a clone of the BBB? and using a 1Ghz cpu?

https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2014.04/0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch

Regards,

btw, i'm flashing the eeprom in kernel land:

https://github.com/RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh#L39

Regards,

Yes, a subset of the BBB based on the reference design from Gerald. No, we're running the 720MHz version of the AM335x, but are using the TPS65217C and the DDR3 memory like the BBB.

Looking at the http: reference above, seems that the kernel WILL boot without a proper ID EEPROM signature, so I guess I don't need to worry about that as being the Kernel Panic source. I guess I'll keep digging into our hardware.

Thanks,
Ross

Yes, a subset of the BBB based on the reference design from Gerald. No,
we're running the 720MHz version of the AM335x, but are using the TPS65217C
and the DDR3 memory like the BBB.

Ah then for reference for anyone else, you just need to take out this
one part of the patch which forces 1Ghz...
https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2014.04/0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch#L44

Looking at the http: reference above, seems that the kernel WILL boot
without a proper ID EEPROM signature, so I guess I don't need to worry about
that as being the Kernel Panic source. I guess I'll keep digging into our
hardware.

Regards,