Created
August 28, 2020 22:51
-
-
Save Namburger/f700eb6b18bd1e3697638088d5995c8b to your computer and use it in GitHub Desktop.
disable-hdmi-mendel.dts
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /dts-v1/; | |
| /plugin/; | |
| / { | |
| compatible = "fsl,imx8mq-hdmi"; | |
| fragment@0 { | |
| target-path = "/hdmi@32c00000"; | |
| __overlay__ { | |
| status = "disabled"; | |
| }; | |
| }; | |
| fragment@1 { | |
| target-path = "/dcss@0x32e00000"; | |
| __overlay__ { | |
| status = "disabled"; | |
| }; | |
| }; | |
| }; |
Hi, there is no need of 27 Mhz clock. just compile and place the file at
/boot. The project page I shared about the door lock FR system, has no
clock pin associated with it.
I also found that the wifi module and TPU accelerator is on pci lines which
sometimes fails to detect the device when u try to access wifi a lot via
nmcli or connect functions. This happens due to unexpected kernal failure.
So, I recommend you to flash and rebuild your device on dev board, build
the dtc file using above code, place at boot, and transfer the SoM at ur
custom HDC.
Thanks,
Abhijeet
…On Wed, Dec 14, 2022, 12:36 AM Varun Raghavendra ***@***.***> wrote:
***@***.**** commented on this gist.
------------------------------
Hi @Namburger <https://github.com/Namburger>
Found this in the Google Coral SoM Documentation
"HDMI reference clock (27 MHz) (positive/negative). Required for bootup ,
even if you don't use HDMI. "
This is blocking me to access the EdgeTPU for any application, it
basically fails to detect the EdgeTPU with your device tree overlay, is
this usual, or are you able to use it without this clock, , is there any
way to disable this clock so that I can use the EdgeTPU properly? Thanks
—
Reply to this email directly, view it on GitHub
<https://gist.github.com/f700eb6b18bd1e3697638088d5995c8b#gistcomment-4401194>
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA63WTQOCWJQET6WVOSJEADWNCJZVBFKMF2HI4TJMJ2XIZLTSKBKK5TBNR2WLJDHNFZXJJDOMFWWLK3UNBZGKYLEL52HS4DFQKSXMYLMOVS2I5DSOVS2I3TBNVS3W5DIOJSWCZC7OBQXE5DJMNUXAYLOORPWCY3UNF3GS5DZVRZXKYTKMVRXIX3UPFYGLK2HNFZXIQ3PNVWWK3TUUZ2G64DJMNZZDAVEOR4XAZNEM5UXG5FFOZQWY5LFVEYTANJRGA2TOMRQU52HE2LHM5SXFJTDOJSWC5DF>
.
You are receiving this email because you commented on the thread.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>
.
So initially work with USB-c lan and avoid working with the WiFi. I also
discussed this here
A soln just for your future errors.
google-coral/edgetpu#589 (comment)
On Wed, Dec 14, 2022, 1:18 AM Abhijeet Borgule ***@***.***>
wrote:
… Hi, there is no need of 27 Mhz clock. just compile and place the file at
/boot. The project page I shared about the door lock FR system, has no
clock pin associated with it.
I also found that the wifi module and TPU accelerator is on pci lines
which sometimes fails to detect the device when u try to access wifi a lot
via nmcli or connect functions. This happens due to unexpected kernal
failure. So, I recommend you to flash and rebuild your device on dev board,
build the dtc file using above code, place at boot, and transfer the SoM at
ur custom HDC.
Thanks,
Abhijeet
On Wed, Dec 14, 2022, 12:36 AM Varun Raghavendra ***@***.***>
wrote:
> ***@***.**** commented on this gist.
> ------------------------------
>
> Hi @Namburger <https://github.com/Namburger>
>
> Found this in the Google Coral SoM Documentation
>
> "HDMI reference clock (27 MHz) (positive/negative). Required for bootup
> , even if you don't use HDMI. "
>
> This is blocking me to access the EdgeTPU for any application, it
> basically fails to detect the EdgeTPU with your device tree overlay, is
> this usual, or are you able to use it without this clock, , is there any
> way to disable this clock so that I can use the EdgeTPU properly? Thanks
>
> —
> Reply to this email directly, view it on GitHub
> <https://gist.github.com/f700eb6b18bd1e3697638088d5995c8b#gistcomment-4401194>
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AA63WTQOCWJQET6WVOSJEADWNCJZVBFKMF2HI4TJMJ2XIZLTSKBKK5TBNR2WLJDHNFZXJJDOMFWWLK3UNBZGKYLEL52HS4DFQKSXMYLMOVS2I5DSOVS2I3TBNVS3W5DIOJSWCZC7OBQXE5DJMNUXAYLOORPWCY3UNF3GS5DZVRZXKYTKMVRXIX3UPFYGLK2HNFZXIQ3PNVWWK3TUUZ2G64DJMNZZDAVEOR4XAZNEM5UXG5FFOZQWY5LFVEYTANJRGA2TOMRQU52HE2LHM5SXFJTDOJSWC5DF>
> .
> You are receiving this email because you commented on the thread.
>
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>
> .
>
>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@hwjalapeno it does not blocks you from accessing the EdgeTPU in any form. As I already mentioned here, your issue is that the application is trying to sync your result to a monitor which fails. There are 2 things that we suggested:
rtspand it worked for him, did you try that?