For some reason the post has screwed up the download hyperlink. Not hard to find/fix.
Used Ubuntu 14.04 âDisksâ tool to write image to SD card. Inserted SD card into board and powered it up. It took ~930 seconds to flash eMMC (last dmesg entry: [ 928.221073] reboot: System halted)
Good feedback through system console and on a locally connected monitor.
There were a few system messages during the flash which were related to a USB device. Something about a disconnect reconnect of keyboard or mouse. My terminal buffer history was too short to keep the actual messages. Flashed system seems to be fine, with no USB messages so far.
The system log has a few errors (no glaring problems, but FYI):
/cpus/cpu@0 missing clock-frequency property
/cpus/cpu@1 missing clock-frequency property
pci 0000:00:00.0: IOMMU is currently not supported for PCI
omap_hsmmc 4809c000.mmc: no pinctrl state for sdr104 mode
omap_hsmmc 4809c000.mmc: no pinctrl state for hs200_1_8v mode
omap_hsmmc 4809c000.mmc: no pinctrl state for ddr50 mode
omap_hsmmc 4809c000.mmc: no pinctrl state for sdr50 mode
omap_hsmmc 4809c000.mmc: no pinctrl state for sdr25 mode
omap_hsmmc 4809c000.mmc: no pinctrl state for sdr12 mode
omap_hsmmc 4809c000.mmc: no pinctrl state for ddr_1_8v mode
omap_hsmmc 480b4000.mmc: no pinctrl state for sdr104 mode
omap_hsmmc 480b4000.mmc: no pinctrl state for hs200_1_8v mode
omap_hsmmc 480b4000.mmc: no pinctrl state for ddr50 mode
omap_hsmmc 480b4000.mmc: no pinctrl state for sdr50 mode
omap_hsmmc 480b4000.mmc: no pinctrl state for sdr25 mode
omap_hsmmc 480b4000.mmc: no pinctrl state for sdr12 mode
omap_voltage_late_init: Voltage driver support not added
omapdss error: HDMI I2C timeout reading EDID
systemd[1]: Job console-setup.service/start deleted to break ordering cycle starting with basic.target/start
vgaarb: this pci device is not a vga device
And lots of remoteproc messages, which I wonât post here.
I will continue to test other applications and peripherals.
The system log has a few errors (no glaring problems, but FYI):
/cpus/cpu@0 missing clock-frequency property
/cpus/cpu@1 missing clock-frequency property
pci 0000:00:00.0: IOMMU is currently not supported for PCI
omap_hsmmc 4809c000.mmc: no pinctrl state for sdr104 mode
omap_hsmmc 4809c000.mmc: no pinctrl state for hs200_1_8v mode
omap_hsmmc 4809c000.mmc: no pinctrl state for ddr50 mode
omap_hsmmc 4809c000.mmc: no pinctrl state for sdr50 mode
omap_hsmmc 4809c000.mmc: no pinctrl state for sdr25 mode
omap_hsmmc 4809c000.mmc: no pinctrl state for sdr12 mode
omap_hsmmc 4809c000.mmc: no pinctrl state for ddr_1_8v mode
omap_hsmmc 480b4000.mmc: no pinctrl state for sdr104 mode
omap_hsmmc 480b4000.mmc: no pinctrl state for hs200_1_8v mode
omap_hsmmc 480b4000.mmc: no pinctrl state for ddr50 mode
omap_hsmmc 480b4000.mmc: no pinctrl state for sdr50 mode
omap_hsmmc 480b4000.mmc: no pinctrl state for sdr25 mode
omap_hsmmc 480b4000.mmc: no pinctrl state for sdr12 mode
^^ This we know about on v4.1 kernel, and are working to fix.
basically iodelay configuration needed.
omap_voltage_late_init: Voltage driver support not added
This appears from legacy code in arch/arm/mach-omap2/voltage.c and is
harmless - I can squash this if folks want to.. mostly because the
am57/dra7 logic is reusing omap2_common_pm_late_init
omapdss error: HDMI I2C timeout reading EDID
systemd[1]: Job console-setup.service/start deleted to break ordering
cycle starting with basic.target/start
vgaarb: this pci device is not a vga device
And lots of remoteproc messages, which I won't post here.
I will continue to test other applications and peripherals.
For some reason the post has screwed up the download hyperlink. Not hard to
find/fix.
Used Ubuntu 14.04 "Disks" tool to write image to SD card. Inserted SD card
into board and powered it up. It took ~930 seconds to flash eMMC (last dmesg
entry: [ 928.221073] reboot: System halted)
Good feedback through system console and on a locally connected monitor.
There were a few system messages during the flash which were related to a
USB device. Something about a disconnect reconnect of keyboard or mouse. My
terminal buffer history was too short to keep the actual messages. Flashed
system seems to be fine, with no USB messages so far.
The system log has a few errors (no glaring problems, but FYI):
/cpus/cpu@0 missing clock-frequency property
/cpus/cpu@1 missing clock-frequency property
I'm going to steal the pr_warn patch Nishanth pointed too. I already
do that for the ttyO0 -> ttyS0 migration..
pci 0000:00:00.0: IOMMU is currently not supported for PCI
omap_hsmmc 4809c000.mmc: no pinctrl state for sdr104 mode
omap_hsmmc 4809c000.mmc: no pinctrl state for hs200_1_8v mode
omap_hsmmc 4809c000.mmc: no pinctrl state for ddr50 mode
omap_hsmmc 4809c000.mmc: no pinctrl state for sdr50 mode
omap_hsmmc 4809c000.mmc: no pinctrl state for sdr25 mode
omap_hsmmc 4809c000.mmc: no pinctrl state for sdr12 mode
omap_hsmmc 4809c000.mmc: no pinctrl state for ddr_1_8v mode
omap_hsmmc 480b4000.mmc: no pinctrl state for sdr104 mode
omap_hsmmc 480b4000.mmc: no pinctrl state for hs200_1_8v mode
omap_hsmmc 480b4000.mmc: no pinctrl state for ddr50 mode
omap_hsmmc 480b4000.mmc: no pinctrl state for sdr50 mode
omap_hsmmc 480b4000.mmc: no pinctrl state for sdr25 mode
omap_hsmmc 480b4000.mmc: no pinctrl state for sdr12 mode
omap_voltage_late_init: Voltage driver support not added
omapdss error: HDMI I2C timeout reading EDID
odd.. i see that all the time on my omap5_uevm... did you have the
hdmi cable plugged in?
systemd[1]: Job console-setup.service/start deleted to break ordering cycle
starting with basic.target/start
vgaarb: this pci device is not a vga device
This is from the drm stack, now that pci-e is enabled, a whole lot of
options...
And lots of remoteproc messages, which I won't post here.
all those remoteproc messages are about devices looking for firmware..
It's firmware you can compile.
Itâs been 2 years and we still donât know where to put the clock-frequency
Yes I get a lot of HDMI timeouts (I only listed one for brevity), but they stop after about 60 seconds. I have an HDMI cable connected to a HDMI to DVI adapter, which is then connected to an old Dell monitor.
Iâm getting to the compile partâŚhold your horses Gotta connect my fan againâŚthat sucker gets hot after a while (compiling Qt). I didnât want to assume that it would start throttling after >70C temps, at least not until more units are available
It's been 2 years and we still don't know where to put the clock-frequency
It looks to be a "what color do we paint the barn door?" problem.
Yes I get a lot of HDMI timeouts (I only listed one for brevity), but they
stop after about 60 seconds. I have an HDMI cable connected to a HDMI to DVI
adapter, which is then connected to an old Dell monitor.
I"m doing the same thing: DELL 1707FP
I'm getting to the compile part...hold your horses Gotta connect my fan
again....that sucker gets hot after a while (compiling Qt). I didn't want to
assume that it would start throttling after >70C temps, at least not until
more units are available
Oh it'll throttle.. i think it'll even reboot if it gets too hot..
If I open up the âMonitor Settingsâ tool, I get jerky mouse movement for a few seconds and then 3 more âomapdss error: HDMI I2C timeout reading EDIDâ in the system log.
I changed a couple things (brightness and resolution) and hit apply. I get a whole string of I2C errors, system becomes very sluggish, mouse movement is severely diminished. But, everything comes back to normal, after the âKeep Settings?â message is shown and times out.
After one or more of these changes, the system menu app crashed. But, interestingly, after that, the monitor settings application is much faster to change settings and the mouse is jerky but usable.
Ok, so I performed a reboot using the command ârebootâ. No HDMI I2C errors and the display is properly detected now âHDMI-1 (HDMI-1) DELL 2007WFâ at 1680x1050 & 59.88 Hz
On another note, on that same ârebootâ there is a boot message that does not show up in the system log, but is printed to the console:
`
Starting kernel âŚ
[ 0.051587] /cpus/cpu@0 missing clock-frequency property
[ 0.051644] /cpus/cpu@1 missing clock-frequency property
[ 3.458828] pci 0000:00:00.0: IOMMU is currently not supported for PCI
[ 3.539322] omap_hsmmc 4809c000.mmc: no pinctrl state for sdr104 mode
[ 3.545820] omap_hsmmc 4809c000.mmc: no pinctrl state for hs200_1_8v mode
[ 3.552640] omap_hsmmc 4809c000.mmc: no pinctrl state for ddr50 mode
[ 3.559040] omap_hsmmc 4809c000.mmc: no pinctrl state for sdr50 mode
[ 3.565440] omap_hsmmc 4809c000.mmc: no pinctrl state for sdr25 mode
[ 3.571824] omap_hsmmc 4809c000.mmc: no pinctrl state for sdr12 mode
[ 3.578226] omap_hsmmc 4809c000.mmc: no pinctrl state for ddr_1_8v mode
[ 3.623888] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr104 mode
[ 3.631426] omap_hsmmc 480b4000.mmc: no pinctrl state for hs200_1_8v mode
[ 3.640307] omap_hsmmc 480b4000.mmc: no pinctrl state for ddr50 mode
[ 3.646766] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr50 mode
[ 3.653220] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr25 mode
[ 3.659657] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr12 mode
[ 3.723787] omap_voltage_late_init: Voltage driver support not added
Loading, please waitâŚ
fsck from util-linux 2.25.2
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p1
fsck exited with status code 8
[ 10.487702] systemd[1]: Job console-setup.service/start deleted to break ordering cycle starting with basic.target/start
[ 10.794018] systemd-fsck[194]: BOOT: clean, 118616/233856 files, 719153/933632 blocks
[ 3.458828] pci 0000:00:00.0: IOMMU is currently not supported for PCI
[ 3.539322] omap_hsmmc 4809c000.mmc: no pinctrl state for sdr104 mode
[ 3.545820] omap_hsmmc 4809c000.mmc: no pinctrl state for hs200_1_8v mode
[ 3.552640] omap_hsmmc 4809c000.mmc: no pinctrl state for ddr50 mode
[ 3.559040] omap_hsmmc 4809c000.mmc: no pinctrl state for sdr50 mode
[ 3.565440] omap_hsmmc 4809c000.mmc: no pinctrl state for sdr25 mode
[ 3.571824] omap_hsmmc 4809c000.mmc: no pinctrl state for sdr12 mode
[ 3.578226] omap_hsmmc 4809c000.mmc: no pinctrl state for ddr_1_8v mode
[ 3.623888] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr104 mode
[ 3.631426] omap_hsmmc 480b4000.mmc: no pinctrl state for hs200_1_8v mode
[ 3.640307] omap_hsmmc 480b4000.mmc: no pinctrl state for ddr50 mode
[ 3.646766] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr50 mode
[ 3.653220] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr25 mode
[ 3.659657] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr12 mode
[ 3.723787] omap_voltage_late_init: Voltage driver support not added
Loading, please wait...
fsck from util-linux 2.25.2
fsck: error 2 (No such file or directory) while executing fsck.ext4 for
I need to fix this "error 2" too.. haven't found the systemd patch
with the fix to backport yet..
debian@BeagleBoard-X15:~$ sudo apt-get install initramfs-tools --reinstall Reading package lists... Done Building dependency tree Reading state information... Done Reinstallation of initramfs-tools is not possible, it cannot be downloaded. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
I reflashed eMMC with the original image from this morning and no HDMI I2C errors. So something has been changed in the hardware to fix the I2C errors? Could it be a PMIC thing?