Announcement

Collapse
No announcement yet.

4dpi 32 raspberry pi model b+ No network after hat configuration

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • 4dpi 32 raspberry pi model b+ No network after hat configuration

    Hello, after installing hat on pi 3 model b+ on Raspbian strech desktop no network interfaces is shown. When I click on wireless icon task bar it says no APs found and keeps searching for APs.

    I installed Raspbian strech 3 times everything was working till I followed the lines on hardware version 2 steps from pdf and installed the hat tar and untarred it and booted. Eth0 wlan0 got disabled also no network devices found. I tried raspi-config entering network configuration manually but no success.

    Also with regular version after hat installation both hdmi and hat doesn’t work.

    It works as intended on raspi model 3 but not on 3 model b+.

    Could you help?
    Best regards,

  • #2
    Hello Gomania,

    I have tried the latest kernel version with the latest Raspbian OS on a Raspberry Pi 3 B+.
    However, I didn't encounter the issue that you have mentioned.

    Are you using the latest kernel version?
    http://www.4dsystems.com.au/download...34_v1.1.tar.gz

    Copy the file on your RaspberryPi and extract it using the command:
    Code:
    sudo tar -xzvf gen4-hats_4-14-34_v1.1.tar.gz -C /
    I hope it helps.
    Kevin

    Comment


    • #3
      Hello John,
      Thank you. Now it is working.

      There is still question in my mind, wondering, Where should I check the latest version from?

      Because I tried to follow the link from product web page (4DP-32) -> https://www.4dsystems.com.au/product/4DPi_32/

      which redirected me to: 4d-hats_4-9-35_v1.1.tar.gz on http://www.4dsystems.com.au/download...35_v1.1.tar.gz

      Then it showed me that the kernel which I was looking for is not there but has multiple choices and I follow the link from there to https://www.4dsystems.com.au/downloa...35_v1.0.tar.gz because there was no file named: 4d-hats_4-9-35_v1.1.tar.gz.

      This is also the same on product PDF version 2: https://www.4dsystems.com.au/product...heet_R_2_7.pdf
      Page 6 of 18 Item 8) $wget http://www.4dsystems.com.au/downloads/4 DPi/All/4d-hats_4-9-35_v1.0.tar.gz

      Finally I ended up with version: 4d-hats_4-9-35_v1.0.tar.gz


      Leaves me with the question: Where should I check the latest version from? If it is not the web page or product manual.

      Many thanks,

      Gokhan

      Comment


      • #4
        Hello Gomania,

        Currently we are updating the datasheets and links to put the correct kernel image package.

        For the meantime, you can check the latest kernel package through visiting the product page of our newest 4DPi displays: https://www.4dsystems.com.au/product/gen4-4DPi
        Software Packages -> 4DPi Kernel Package.

        This is also included on the datasheet.
        Documentation->gen4-4DPi Datasheet

        Best Regards
        Kevin

        Comment


        • #5
          Hello again,

          Could you suggest me a working version of 4DHats driver for RasPI B+ along with 4DP-32 Revision 1.x Hardware?

          I already tried one written on 4DPi-32 Datasheet for Revision 1.x Hardware: http://www.4dsystems.com.au/download...34_v1.1.tar.gz

          Thanks,

          Comment


          • #6
            Hi Gomania,

            Sorry for the delay in response to this, we were trying to find the REV 1.x hardware to give this a full test, as its been a few years since the last support requirement on this older hardware.

            For REV 1.x hardware, the process is basically the same as the REV 2.x hardware. The datasheet for the Revision 1.x hardware is admittingly out of date, but using the newer file name, you should get most of the way there.

            The kernel patch you linked above is correct, its the latest and matches to the latest release of Rasbian so far.

            So after installing your image, and installing the patch as per the datasheet process (subbing in the new file name), you then edit the config.txt file and uncomment the line for the 4dpi-32, as there is no EEPROM on the Revision 1.x or 2.x hardware, so it needs to be forced from the config.txt file.

            Once you have done that, you will need to edit the /etc/modules file (same process as the config.txt file) to enable the touch to work.

            On the older 1.x hardware, the touch controller is different to the 2.x hardware. By default now the kernel patch selects the later 2.x hardware, as 1.x hasn't been made for some time.
            So you just need to comment out the line for the ar1020, and uncomment the 4dpi_touch line.

            The file should look something like this:

            Code:
            # /etc/modules: kernel modules to load at boot time.
            #
            # This file contains the names of kernel modules that should be loaded
            # at boot time, one per line. Lines beginning with "#" are ignored.
            
            i2c-dev
            i2c-bcm2708
            #pwmbl
            #ar1020-i2c
            4dpi_touch
            The pwmbl line is to enable you to change the backlight brightness if you have the jumper on the board set to 'PWM'. Else you can just set it to the 'On/Off' side and it will be always enabled.

            Give that a try and come back if you have any problems.

            Regards
            James

            Comment


            • #7
              Hi James,

              Thanks for the effort. But Pi doesn't boot up with the above instructions. (stucks with red light display doesn't work)

              What I've discovered is: if i download and install this version: http://www.4dsystems.com.au/download...35_v1.0.tar.gz

              It boots OK display works but everything else gets broken (network, usb etc.)


              Could you help?

              Best regards,

              Comment


              • #8
                Hello Gomania,


                I already tried one written on 4DPi-32 Datasheet for Revision 1.x Hardware: http://www.4dsystems.com.au/download...34_v1.1.tar.gz
                Have you tried the latest kernel version? I have tried it on 4DPi-35 rev. 1.2, touch and the drivers are working fine.
                http://www.4dsystems.com.au/download...34_v1.1.tar.gz

                Copy the file on your RaspberryPi and extract it using the command:
                Code:
                sudo tar -xzvf gen4-hats_4-14-34_v1.1.tar.gz -C /
                After that you can follow what James has said:

                So after installing your image, and installing the patch as per the datasheet process (subbing in the new file name), you then edit the config.txt file and uncomment the line for the 4dpi-32, as there is no EEPROM on the Revision 1.x or 2.x hardware, so it needs to be forced from the config.txt file.

                Once you have done that, you will need to edit the /etc/modules file (same process as the config.txt file) to enable the touch to work.
                Code:
                # /etc/modules: kernel modules to load at boot time.
                #
                # This file contains the names of kernel modules that should be loaded
                # at boot time, one per line. Lines beginning with "#" are ignored.
                
                i2c-dev
                i2c-bcm2708
                #pwmbl
                #ar1020-i2c
                4dpi_touch


                I hope it helps.

                Best Regards,
                Kevin

                Comment


                • #9
                  Hi John,

                  Now it works...

                  Thanks a lot for your kind help.

                  Best regards,

                  Comment


                  • #10
                    Hi John,

                    Touch is not working...
                    edited /etc/modules like below:

                    i2c-dev
                    i2c-bcm2708
                    #pwmbl
                    #ar1020-i2c
                    4dpi_touch

                    Is there anything else to do?

                    Thanks,
                    Last edited by Gomania; 22nd February 2019, 09:39 PM.

                    Comment


                    • #11
                      nothing else to do?

                      Comment


                      • #12
                        Hello gomania,

                        I am sorry for the delayed response.

                        As I do not have any spare 4DPi-32 rev 1xx, I could not possibly point out if you have an issue on your module.

                        Supposedly, the touch on 4DPi-32 should work as it is working on 4DPi-35, which has the same touch controller.


                        Best Regards,
                        Kevin

                        Comment


                        • #13
                          Hello there,

                          I found this thread after once getting the screen to work and did apt-get update/upgrade for which there was many, then after a reboot, the screen still came on but the usb and ethernet ports do not function. Touch screen works so I was able to shutdown properly. I saw the comment above from John Kevin and uncommented dtoverlay=4dpi-32, the applied power to the Pi. I found that the screens backlight illuminates, but goes not further. The Pi shows a green light for a brief moment then nothing. HDMI, when applied only shows a perpetuated underline cursor, non-blinking.

                          I greatly appreciate any response and it's very nice to see that there are still recent responses from 4dSystems for this product. Thank you once again in advance!!

                          RPI 3 B+ using package http://www.4dsystems.com.au/download...35_v1.0.tar.gz with screen: rev 1.02.

                          Comment


                          • #14
                            Hello again,
                            Just adding another note:
                            I went back and tried a previous version: (gen4-hats_4-14-34_v1.1.tar.gz). Then after running sudo tar -xzvf gen4-hats_4-14-34_v1.1.tar.gz -C /, I uncommented dtoverlay=4dpi-32, safely powered off the Pi and attached the hat, before reapplying power and I still get the same results.. I have verified my 5v is ~5.02v which seems to be another cause of issues for the Pi in-general.

                            Once again, thank you for your assistance!

                            Comment


                            • #15
                              Doing an update/upgrade runs the risk of breaking things as if the version you are upgrading to is a higher kernel version than the patch, then the display could stop working. The Kernel patch we offer is a patch on the standard release, so it has to match the same kernel version as what your OS is running. In some cases, the changes in our patches are compatible with minor releases of the kernel, but it's a bit hit and miss, so if you are upgrading you really need to check what the kernel version is you have upgraded to, and then check what version our patch is.
                              If they are drastically different, then raise a ticket and we will try and get an updated kernel patch as soon as possible, however, we can't constantly do this for every minor release the Pi Foundation make.

                              I am not sure this will help you much, but its some background information which is quite important.
                              James

                              Comment

                              Working...
                              X