element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Single-Board Computers
  • Products
  • Dev Tools
  • Single-Board Computers
  • More
  • Cancel
Single-Board Computers
Forum Failed to Fetch the source
  • Blog
  • Forum
  • Documents
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Single-Board Computers to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 19 replies
  • Subscribers 57 subscribers
  • Views 4208 views
  • Users 0 members are here
  • meta_maaxboard
  • maaxboard
Related

Failed to Fetch the source

marvintien
marvintien over 4 years ago

Fetch the source

.......................

Clone this repo

$cd sources

$ git clone http://192.168.2.149/imx8m/meta-maaxboard.git

Cloning into 'meta-maaxboard'...

fatal: unable to access 'http://192.168.2.149/imx8m/meta-maaxboard.git/': Failed to connect to 192.168.2.149 port 80: Connection timed out

 

Please tell me how to fix it? Thanks.

  • Sign in to reply
  • Cancel

Top Replies

  • jafoste4
    jafoste4 over 4 years ago +1
    Hi Marvin, This was an issue on our end where the repo pointed to out internal development location. It has now been fixed and points to : $ git clone https://github.com/Avnet/meta-maaxboard.git Let me…
Parents
  • marvintien
    marvintien over 4 years ago

    Hi Joshua,

         I download and extract 02LinuxShipmentImage_Debian.zip, get MaaXBoard-LinuxShipmentImage-Debian-V1.1.1r10.img, and boot it from microSD card, but can't enter Debian Desktop environment. I wonder why? Please kindly reply me. Thanks in advance.

    B.R.

    Marvin

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • jafoste4
    jafoste4 over 4 years ago in reply to marvintien

    Hi Marvin,

     

    The Desktop environment should work out of box. What are you utilizing as a display(HDMI or MIPI LCD)? Are you getting anything on the display?

     

    -Josh

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • jafoste4
    jafoste4 over 4 years ago in reply to marvintien

    Hi Marvin,

     

    The Desktop environment should work out of box. What are you utilizing as a display(HDMI or MIPI LCD)? Are you getting anything on the display?

     

    -Josh

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
  • marvintien
    marvintien over 4 years ago in reply to jafoste4

    Hi Joshua:

          I am using HDMI monitor to connect to Maaxboard and can't enter Debian5 Desktop.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • jafoste4
    jafoste4 over 4 years ago in reply to marvintien

    Hi Marvin,

     

    Are you getting anything on your screen? Are any of the leds on the board turning on? What SD Card are you using? What are you using as a power supply?

     

    -Josh

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • marvintien
    marvintien over 4 years ago in reply to jafoste4

    Hi Joshua:

    1. Are you getting anything on your screen? 

        HDMI monitor is always black.

    2. Are any of the leds on the board turning on?

        Yes. Debian5 can normally boot from microSD card.

    3. What SD Card are you using?

       I am using "Team micrSD 500X 16GB", it functions well.

        https://24h.pchome.com.tw/prod/DGAG1C-A900987CE 

    4. What are you using as a power supply?

       We bought this https://www.avnet.com/wps/portal/us/products/new-product-introductions/npi/avnet-maaxboard/

      The only power input is "USB Type C 5V/3A" , as describe in the  avnet-maaxboard's website.

     

    This Maaxboard probably has hardware's defect or malfunction, or poor design or poor quality....? I still don't know about it.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • marvintien
    marvintien over 4 years ago in reply to marvintien

    Hi Joshua:

         I just download 02AndroidShipmentImage.zip and burn MaaXBoard-AndroidShipmentImage-SDcard-HDMI-V1.0.2r03.img to microSD card.

    The result is the same, it also can't run to Android  desktop. Only u-boot can output a NXP image to HDMI monitor.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • marvintien
    marvintien over 4 years ago in reply to marvintien

    Hi Joshua:

         Following is the dmesg after boot, the kernel-4.14.78 drm and hdmi driver's output messages.

    Everything seems to be O.K., except for "Unable to configure VS infoframe"?  It always is black screen on the HDMI monitor.

     

    ~# dmesg|grep hdmi

    [    1.156621] [drm] hdmi-audio-codec driver bound to HDMI

    [    1.161881] imx-drm display-subsystem: bound 32c00000.hdmi (ops imx_hdp_imx_ops)

    [    1.193401] i.mx8-hdp 32c00000.hdmi: 0,ff,ff,ff,ff,ff,ff,0

    [    3.059859] i.mx8-hdp 32c00000.hdmi: 0,ff,ff,ff,ff,ff,ff,0

    [    3.486272] imx-cdnhdmi sound-hdmi: i2s-hifi <-> 30050000.sai mapping ok

    [    3.486300] imx-cdnhdmi sound-hdmi: ASoC: no DMI vendor name!

    [    3.544223]   #0: imx-audio-hdmi

    [   10.946019] i.mx8-hdp 32c00000.hdmi: 0,ff,ff,ff,ff,ff,ff,0

     

    ~# dmesg|grep drm

    [    1.055258] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).

    [    1.061906] [drm] No driver support for vblank timestamp query.

    [    1.068048] imx-drm display-subsystem: bound imx-dcss-crtc.0 (ops dcss_crtc_ops)

    [    1.075673] [drm] CDN_API_General_Test_Echo_Ext_blocking - APB(ret = 0 echo_resp = echo test)

    [    1.084216] [drm] CDN_API_General_getCurVersion - ver 13196 verlib 13062

    [    1.091032] [drm] Pixel clock frequency: 594000 KHz, character clock frequency: 594000, color depth is 8-bit.

    [    1.100965] [drm] Pixel clock frequency (594000 KHz) is supported in this color depth (8-bit). Settings found in row 27

    [    1.111818] [drm] VCO frequency is 5940000

    [    1.115933] [drm] VCO frequency (5940000 KHz) is supported. Settings found in row 14

    [    1.147585] [drm] CDN_API_General_Write_Register_blocking LANES_CONFIG ret = 0

    [    1.156621] [drm] hdmi-audio-codec driver bound to HDMI

    [    1.161881] imx-drm display-subsystem: bound 32c00000.hdmi (ops imx_hdp_imx_ops)

    [    1.205615] [drm] Link rate is too high - forcing link to lower rate

    [    1.205667] [drm] Pixel clock frequency: 148500 KHz, character clock frequency: 148500, color depth is 8-bit.

    [    1.205675] [drm] Pixel clock frequency (148500 KHz) is supported in this color depth (8-bit). Settings found in row 16

    [    1.205679] [drm] VCO frequency is 5940000

    [    1.205685] [drm] VCO frequency (5940000 KHz) is supported. Settings found in row 14

    [    1.219625] [drm] CDN_API_General_Write_Register_blocking LANES_CONFIG ret = 0

    [    1.220117] [drm] Unable to configure VS infoframe

    [    2.026648] imx-drm display-subsystem: fb0:  frame buffer device

    [    2.033260] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 0

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • marvintien
    marvintien over 4 years ago in reply to jafoste4

    Hi Joshua:

    $ git clone https://github.com/Avnet/maaxboard-debian-build

    $ cd maaxboard-debian-build

    $ sudo ./debian_build.sh -b rootfs -f ./board/maaxboard/maaxboard.ini

    (But below errors occur:)

    https://github.com/Avnet/maaxboard-debian-build

    Connecting to 192.168.2.100:80... failed: Connection timed out.

    failed: Connection timed out.

    Retrying.

     

    I still fail to build Debian5 image by myself because of the above error, is it possible to point the address of your Debian bsp repository to the external world?  

    If it is, please kindly tell me how to modify "board/maaxboard/maaxboard.ini"? Thanks in advance.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • jafoste4
    jafoste4 over 4 years ago in reply to marvintien

    Hi Marvin,

     

    We are hoping to have this issue resolved by end of the week.

     

    Apologies.

    -Josh

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • marvintien
    marvintien over 4 years ago in reply to jafoste4

    Hi Joshua:

        O.K. I'm waiting for your good news. Thanks.

    Best Regards,

    Marvin

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • jafoste4
    jafoste4 over 4 years ago in reply to marvintien

    Hi Marvin,

    This should be fixed now. Please let me know if you hit any further issues.

    Thx,

    Josh

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • marvintien
    marvintien over 4 years ago in reply to jafoste4

    Hi Joshua:

          Git clone from https://github.com/Avnet/maaxboard-debian-build and rebuild Linux kernel image are workable now.

    But it still can't run in to Debian window desktop via HDMI monitor.

    1. U-boot is calling maaxboard-dcss-hdmi.dtb as follows:

    $ cat uEnv.txt

    fdt_file=maaxboard-dcss-hdmi.dtb

    console=ttymxc0,115200 console=tty1 fbcon=rotate:0

     

    2. The following messages are hot-plugging in HDMI cable that connects HDMI monitor to maax-imx8mq board, the dmesg's output :

    [ 1117.243567] i.mx8-hdp 32c00000.hdmi: 0,ff,ff,ff,ff,ff,ff,0

    [ 1117.249903] [drm] Link rate is too high - forcing link to lower rate

    [ 1117.256695] [drm] Pixel clock frequency: 148500 KHz, character clock frequency: 148500, color depth is 8-bit.

    [ 1117.243567] i.mx8-hdp 32c00000[ 1117.267057] [drm] Pixel clock frequency (148500 KHz) is supported in this color depth (8-bit). Settings found in row 16

    .hdmi: 0,ff,ff,ff,ff,ff,ff,0

    [ 1[ 1117.280877] [drm] VCO frequency is 5940000

    117.249903] [drm] Link rate is to[ 1117.288021] [drm] VCO frequency (5940000 KHz) is supported. Settings found in row 14

    o high - forcing link to lower rate

    [ 1117.256695] [drm] Pixel clock frequency: 148500 KHz, character clock frequency: 148500, color depth is 8-bit.

    [ 1117.267[ 1117.312470] [drm] CDN_API_General_Write_Register_blocking LANES_CONFIG ret = 0

    057] [drm] Pixel clock frequency [ 1117.320479] [drm] Unable to configure VS infoframe

    (148500 KHz) is supported in this color depth (8-bit). Settings found in row 16

    [ 1117.280877] [drm] VCO frequency is 5940000

    [ 1117.288021] [drm] VCO frequency (5940000 KHz) is supported. Settings found in row 14

    [ 1117.312470] [drm] CDN_API_General_Write_Register_blocking LANES_CONFIG ret = 0

    [ 1117.320479] [drm] Unable to configure VS infoframe

    [ 1117.387623] dcss-core 32e00000.dcss: Configured video pll 2 with ref_clk 2 freq 148500000 (actual 148500000)

    [ 1117.387623] dcss-core 32e00000.dcss: Configured video pll 2 with ref_clk 2 freq 148500000 (actual 148500000)

    [ 1117.989365] [drm] HDMI/DP Cable Plug In

    [ 1117.989365] [drm] HDMI/DP Cable Plug In

     

    Best Regards,

    Marvin

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube