Quantcast
Channel: Processors
Viewing all articles
Browse latest Browse all 124457

Forum Post: RE: ti8147 hangs on attempt to use vpss after resume

$
0
0

Devin,

[quote user="Devin Heitmueller"]

 When you say "the LCD turns off then on with success", do you mean you actually see output/graphics on the LCD after the resume other than just the backlight turning on?

[/quote]

I mean I see output/graphics on the LCD after the resume. The touch screen works fine. I run the 3D Graphics -> Chameleon demo (OpenGL ES Demos) and 2D Graphics -> Moving Blocks demo. Both work fine.

Also the VPSS-M3 firmware seems to behave correct after the resume:

omap_gpio omap_gpio.0: completing resume
platform l3_slow.0: completing resume
platform mpu.0: completing resume
platform reg-dummy: completing resume
PM: Finishing wakeup.
Restarting tasks ... done.
root@dm814x-evm:~# cat /sys/devices/platform/vpss/display1/enabled
1
root@dm814x-evm:~#

The difference between the "core" test and the actual suspend should be something related to the VPSS-M3 firmware (/usr/share/ti/ti-media-controller-utils/dm814x_hdvpss.xem3).In the basic-pm-debugging.txt we have:

In particular, the "core" test allows you to test everything except for the actual invocation of the platform firmware in order to put the system into the sleep state.

The error that we have after resume is the same as just unload/stop the VPSS-M3 firmware, without running any suspend/resume test:

Arago 2011.09 dm814x-evm ttyO0

dm814x-evm login: root
root@dm814x-evm:~# cat /sys/devices/platform/vpss/display1/enabled
1
root@dm814x-evm:~# firmware_loader 2 /usr/share/ti/ti-media-controller-utils/dm814x_hdvpss.xem3 stop
FIRMWARE: I2cInit will be done by M3
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
===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 M3
FIRMWARE: isI2cInitRequiredOnM3: 1
FIRMWARE: Default memory configuration is used
Firmware Loader debugging not configured
Default FL_DEBUG: warning
Allowed FL_DEBUG levels: error, warning, info, debug, log
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
FIRMWARE: 2 stop Successful
root@dm814x-evm:~# cat /sys/devices/platform/vpss/display1/enabled
VPSS_FVID2: contrl event 0x1004001a timeout
VPSS_DCTRL: failed to get venc info.
VPSS_DCTRL:  Failed to get venc infor
cat: read error: Invalid argument
root@dm814x-evm:~#

I will further investigate on this.

Best regards,
Pavel


Viewing all articles
Browse latest Browse all 124457

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>