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,

  • James_4DSystems
    replied
    Hello,
    The Pi4 release Kernel Pack will be coming out soon, we are just waiting for our Pi4 to arrive, then development can happen and a release will be made available.
    Please wait a few more days, and hopefully we will have something then.

    Leave a comment:


  • Gomania
    replied
    Hello, I just received RaspBerry Pi 4B which only runs on Debian Buster.

    I couldn't manage to make it work with 4d-hats_4-4-34_v1.1.tar.gz 4DPI-32-rev2 screen

    Do you think it is still working?

    On RasPi 3B+ with Debian Buster hat screen works only if both HDMI and hat is on.

    On 4B with Debian Buster hat doesn't work at all.

    Could you help?
    Last edited by Gomania; 9th July 2019, 10:55 PM.

    Leave a comment:


  • John Kevin
    replied
    Hello,

    I have managed to get a 4DPi-32 (Hardware Rev. 1.3) and have successfully boot the display. I could also confirm that the touch is working on this module.

    Here is my setup:

    4DPi Display: 4DPi-32 HW Rev. 1.3

    Raspberry Pi: Raspberry Pi 3 Model B

    4DPi Kernel Version: gen4-hats_4-14-34_v1.1.tar.gz

    Raspberry Pi Version: November 2018


    The latest 4DPi version i've seen from browsing 4DPi-32_datasheet_R_1_6.pdf where 4d-hats_4-4-34_v1.1.tar.gz is latest? Can you confirm so I can update to the most recent possible? I do see that this was written in 2017.
    We have updated the datasheet on our website, can you please check and follow again the instructions on the Software Download/Installation section.

    4DPi-32
    4DPi-35
    gen4-4DPi

    I saw the comment above from John Kevin and uncommented dtoverlay=4dpi-32
    May I ask if you are using the 4DPi-32 on your current setup?

    I have two 1.02 version 4DPi-24-HAT screens.
    You can check the datasheet for 4DPi-24-HAT. Please follow the setup procedure and post here the result.


    Let me know if that helps.

    Best Regards,
    Kevin
    Last edited by John Kevin; 24th May 2019, 02:10 PM.

    Leave a comment:


  • b3hr3ns
    replied
    Thank you James,
    I understand that it would be tedious to update for every minor release. Is there an area where we can see the latest documenation that contains the latest compatable RPI image in comparison to the latest tar.gz?
    The latest 4DPi version i've seen from browsing 4DPi-32_datasheet_R_1_6.pdf where 4d-hats_4-4-34_v1.1.tar.gz is latest? Can you confirm so I can update to the most recent possible? I do see that this was written in 2017.
    If i were to also make a ticket to request a later update for a major release (forgive me) where would be the best possible place to do so?

    Thanks once again for the prompt response and detailed info!

    Edit to add info:
    I realize from other posts that you might not have any more version 1.xx for testing. will this be a problem in getting updated documentation for the latest raspbian w/kernel 4.14? I have two 1.02 version 4DPi-24-HAT screens. And maybe if there was a possibility that the developer were able to give some basic instructions on how to build the tar.gz based on new kernels I would gladly attempt to do this myself and share it on the forums here for users who still have this great hardware, but want/need upgrades for security etc.

    HUGE Thanks!!
    Last edited by b3hr3ns; 24th May 2019, 10:27 AM.

    Leave a comment:


  • James_4DSystems
    replied
    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.

    Leave a comment:


  • b3hr3ns
    replied
    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!

    Leave a comment:


  • b3hr3ns
    replied
    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.

    Leave a comment:


  • John Kevin
    replied
    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.


    Best Regards,
    Kevin
    Last edited by John Kevin; 24th May 2019, 01:44 PM.

    Leave a comment:


  • Gomania
    replied
    nothing else to do?

    Leave a comment:


  • Gomania
    replied
    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, 08:39 PM.

    Leave a comment:


  • Gomania
    replied
    Hi John,

    Now it works...

    Thanks a lot for your kind help.

    Best regards,

    Leave a comment:


  • John Kevin
    replied
    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

    Leave a comment:


  • Gomania
    replied
    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,

    Leave a comment:


  • James_4DSystems
    replied
    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

    Leave a comment:

Working...
X