Hi there,
we have question. We have a custom DM8148 module on top a Q7 carrier board. We set the PINMUX to the required settings
omap_mux_init_signal("vout1_g_y_yc2.hdmi_ddc_scl_mux1",
TI814X_PULL_UP | TI814X_INPUT_EN);
omap_mux_init_signal("vout1_r_cr3.hdmi_ddc_sda_mux1",
TI814X_PULL_UP | TI814X_INPUT_EN);
omap_mux_init_signal("vout1_r_cr2.hdmi_hpd_mux1",
TI814X_INPUT_EN);
After inserting all modules and loading the firmware (without i2c init): HDMI works basically (examples and own applications work), but whenever we change something (e.g. disable/enable the display) or when the HDMI driver gets loaded, we see the message I2C no ack (HDMI W1 Rev. 4.0).
SysLink version : 2.10.03.20
SysLink module created on Date:Nov 27 2012 Time:16:51:19
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mm]
===Mandatory arguments===
<Processor Id> 0: DSP, 1: Video-M3, 2: Vpss-M3
<Location of Firmware> firmware binary file
<start|stop> to start/stop the firmware
===Optional arguments===
-mmap input memory map bin file name
-i2c 0: i2c init not done by M3, 1(default): i2c init done by
FIRMWARE: isI2cInitRequiredOnM3: 0
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.2.1
FIRMWARE: Memory Configuration status : In Progress
FIRMWARE: 2 start Successful
HDMI W1 rev 4.0
I2C No Ack
The PINMUX regs are still set as specified above after loading the modules: 0x60010, 0x60010, 0x40010.
Also we had the problem that we tried it at different monitors from Dell, but some models didn't work (Dell P2411H), i.e. the output is "display timinig not supported. set to 1080p@60". Excplicitly setting it using the commands
echo 0 > /sys/devices/platform/vpss/display0/enabled
echo 1080p-60 > /sys/devices/platform/vpss/display0/mode
echo 1 > /sys/devices/platform/vpss/display0/enabled
didn't help.
Any ideas what could be the source of the problem.
Regards,
Markus
