search

dickontoo / omxtx

OpenMAX transcoder for the Raspberry Pi
GNU General Public License v2.0
117 stars 36 forks source link

OMX_ErrorHardware on OMX_Init() failure #12

Closed timcortesi closed 9 years ago

timcortesi commented 10 years ago

I'm not sure if this is a hardware specific issue, but when I try to run omxtx, I get an error on the OMX_Init function call. When I print the error code, I get: 0x80001009. After looking this up, apparently it corresponds to the following:

OMX_ErrorHardware The hardware failed to respond as expected

I understand that this is an OpenMAX error code, and is not specifically related to omxtx, but was hoping somebody could lend some insight into this issue. The compliation process went fine, and I am running the latest version of the raspberry pi firmware ala rpi-udate. I do have my CPU overclocked to 900mhz (from 700mhz), but have not experienced any other issues.

I apologize if this is the wrong place to post this issue, but could not find a better location. If there is a more correct place, please let me know.

muuuh commented 10 years ago

I have the same problem: debian wheezy OMX_Init() failed on line 1399: 80001009

Solution: http://rpi.vypni.net/omxcore-failed-to-init-on-raspberry-pi-raspbian/ you have to change gpu_mem

R4P70R commented 9 years ago

I know it's late for this reply but for futur researches: Don't forget to call the function "bcm_host_init();" before using OMX_Init

"The Raspberry Pi requires that the bcm_host_init() function is called first before any GPU calls can be made." - http://elinux.org/Raspberry_Pi_VideoCore_APIs

dickontoo commented 9 years ago

Not really a problem in this case, though. The code is correct, and it's a misconfiguration on the Pi in question which caused this issue to be opened. I'm going to close it now.

Thanks.