7 7
tkaiser

NanoPC T4

Recommended Posts

On 9/19/2018 at 10:06 AM, tkaiser said:

Just tested this too and it also does not work

@tkaiser, I wished to update my NanoPC-T4 today, and I've faced your issue ...

Although the BOOT button trick worked, since I saw the u-boot build date, it was taking the one from SDCard, but it choose to run scripts/kernel from eMMC.

I had to stop u-boot at prompt, do manual "setenv devnum 1" to avoid eMMC followed by "run mmc_boot", it finally booted from SDCard.

It was definitively not like that with my previous old HJC image, so something wrong in the current u-boot scripts ...

 

Share this post


Link to post
Share on other sites

wasn't there a switch between rk3399 and rockchip64  (sources) for the T4. Rockchip64 uses u-boot from ayufan based on rockchips one whereas rk3399 uses mainline u-boot. They may have a difference in definition of 0/1 for eMMC/SD-Card?

Share this post


Link to post
Share on other sites
9 minutes ago, chwe said:

They may have a difference in definition of 0/1 for eMMC/SD-Card?

Maybe ... Unfortunately, I didn't kept the old private built image with old HJC branch, so I can't even look what was different in both u-boot.

At least, we now have a manual workaround ...

 

Share this post


Link to post
Share on other sites
On 6/17/2018 at 8:26 AM, tkaiser said:

Pros:

  • Another RK3399 board so software support is already pretty mature
  • Rich set of interfaces (2 x USB2 without shared bandwidth, 2 x USB3, triple display output and so on)
  • No powering hassles due to 12V (2A) PSU requirement
  • 16GB superfast eMMC 5.1 
  • Usable and performant Wi-Fi (dual band and dual antenna so MIMO can be used, for numbers see here)
  • All 4 PCIe lanes exposed (M.2 M key connector on the bottom, suitable for NVMe SSDs, or to attach a 4 port SATA controller or a PCIe riser card)

 

 

Has anyone tried a 2 or 4 port SATA controller in the M.2 slot? Does it work? What is the most streamlined way to run power to 3.5" drives in this setup?

Share this post


Link to post
Share on other sites
48 minutes ago, Jason Law said:

Has anyone tried a 2 or 4 port SATA controller in the M.2 slot? Does it work?

 

Nope and I don't think so. I wanted to try the same, did some research and ended up with an Amazon review from someone trying this with the Firefly RK3399 saying the Marvell 9235 adapter he had has some components on the bottom that make it impossible to use it on the board without shorting something. These things look like this:

 

201801231409528235.jpg

 

And then on NanoPC-T4 there are only mounting holes for 2280 while the SATA adapters are all 2242. So unless you get a PCIe extender somewhere the M.2 slot is 'SSD only'.

 

Are you aware that FriendlyELEC will provide the below for NanoPi M4 soon (also solving the powering problem):

IMG_1132.jpg

 

 

Share this post


Link to post
Share on other sites
3 minutes ago, Jason Law said:

how will this connect to the M4?

 

It's a HAT so you simply mount in on top of the NanoPi using 4 spacers so GPIO headers make contact. Since NanoPi M4 is one of the few SBC that have the SoC on the appropriate side of the PCB (the lower one) attaching HATs does not negatively affect heat dissipation.

 

(still hoping that the final version of the HAT will also use a 40 pin male header so the GPIOs on this header can still be used)

Share this post


Link to post
Share on other sites

New guy here.  Sorry if I'm in the wrong place.  I followed the link from the Armbian.com /nanopc-t4/ page.

 

Issue #1:

 

Lots of this in /var/log/syslog, but otherwise working fine:

 

Sep 28 21:13:18 localhost kernel: [ 2203.794730] _tdata_psh_info_pool_deq 200: Out of tdata_disc_grp
Sep 28 21:13:18 localhost kernel: [ 2203.794745] dhd_tcpdata_info_get 1092: No more free tdata_psh_info!!
Sep 28 21:13:19 localhost kernel: [ 2203.924558] _tdata_psh_info_pool_deq 200: Out of tdata_disc_grp
Sep 28 21:13:19 localhost kernel: [ 2203.924578] dhd_tcpdata_info_get 1092: No more free tdata_psh_info!!
Sep 28 21:13:19 localhost kernel: [ 2204.283677] _tdata_psh_info_pool_deq 200: Out of tdata_disc_grp
Sep 28 21:13:19 localhost kernel: [ 2204.283696] dhd_tcpdata_info_get 1092: No more free tdata_psh_info!!
 

I am on the most recent release:

 

Welcome to ARMBIAN 5.60 stable Debian GNU/Linux 9 (stretch) 4.4.156-rk3399
System load:   0.14 0.04 0.01   Up time:       1 min
Memory usage:  2 % of 3811MB    IP:            192.168.1.162
CPU temp:      51°C
Usage of /:    10% of 15G

 

Originally installed 5.59 via SD card then moved to eMMC boot using armbian-config.  5.59 had the same syslog messages.  Upgraded to 5.60 using armbian-config

 

Details at:  http://ix.io/1nO0

 

Issue #2

 

Generic Amazon mSATA M.2 2280 60GB doesn't show up.   Let me how/where I can provide any more info.

 

Thanks to the devs for all the great work.

 

 

 

 

Share this post


Link to post
Share on other sites
3 hours ago, SMburn said:

Generic Amazon mSATA M.2

 

Please be very careful with these wordings. M.2 is not mSATA. M.2 is just a mechanical connector able to transport a bunch of different protocols. In case you have no other device suited for an M.2 SATA SSD you might want to have a look at https://jeyi.aliexpress.com/store/group/USB3-0-USB3-1-Type-C-Series/710516_511630295.html for external USB3 enclosures (to get a bulky but ultra fast 'USB pendrive'). But since a 'generic' 60 GB SSD will perform crappy anyway and you talked about Amazon the best you could do is to return such a thing right now.

Share this post


Link to post
Share on other sites
19 hours ago, hjc said:

The M.2 connector on T4 does not support SATA, so you should get an NVMe SSD.

 

Thanks for schooling me on this.  My SATA stick is keyed for both M and B connectors.  My clearly wrong ASSumption was that if it fits, it works.

 

19 hours ago, tkaiser said:

In case you have no other device suited for an M.2 SATA SSD you might want to have a look at..

 

Thanks.   With that, my car audio system USB input will now get a music library source that that isn't mobile phone dependent. 

 

Returning to my other issue:

 

23 hours ago, SMburn said:

Sep 28 21:13:18 localhost kernel: [ 2203.794730] _tdata_psh_info_pool_deq 200: Out of tdata_disc_grp
Sep 28 21:13:18 localhost kernel: [ 2203.794745] dhd_tcpdata_info_get 1092: No more free tdata_psh_info!!

 

Is there any more info I can provide, or is this a known thing that's being worked on and I just need to relax?

 

Thanks again for your help.

 

 

Share this post


Link to post
Share on other sites

currently i'm trying to load a dtbo to 4.19-rc4. attachted dts works and results in loading modul adv7180.

/dts-v1/;
/plugin/;

/ {
        compatible = "friendlyelec,nanopc-t4", "rockchip,rk3399";

        fragment@0 {
//              target = <&i2c1>;
                target-path = "/i2c@ff110000";
                __overlay__ {
                        #address-cells = <1>;
                        #size-cells = <0>;

                        adv7282-m@20 {
                                status = "okay";
                                compatible = "adi,adv7282-m";
                                reg = <0x20>;
                                device_type = "v4l2-i2c-subdev";

//                              powerdown-gpios = <&gpio2 28 1>;// 92
//                              reset-gpios = <&adv_gpio2 27 1>;        // 91
                        };
                };
        };
};

i need some advices for
- referencing by phandle (like target = <&i2c1>)
- defining gpios (commented out gpios)

 

Share this post


Link to post
Share on other sites
On 9/19/2018 at 10:39 AM, tkaiser said:

 

Boot priority with Rockchip boards is AFAIK always eMMC first then SD card. So once RK3399 finds a bootloader signature on the eMMC it will boot from there even if a bootable SD card is inserted. If you want to reflash eMMC in this situation you

  • delete the bootloader on the eMMC (can be done from the running system: 'dd if=/dev/null of=/dev/mmcblk1 bs=1M count=64 ; sync')

 

This worked for me, when using the right device for the zero source

  • 'dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=64 ; sync'

Share this post


Link to post
Share on other sites
On 10/13/2018 at 3:08 PM, habeIchVergessen said:

  		fragment@0 {
                target = <&i2c1>;
...
  				adv7282-m@20 {
...
                              powerdown-gpios = <&gpio2 28 1>;// 92
                              reset-gpios = <&adv_gpio2 27 1>;        // 91

dtb files included in kernel source tree needs to be build with __symbols__ node (dtc -@ ...). just modified the dtc command in scripts/Makefile.lib.

entries in __symbols__ node are required to be able to resolve existing phandle.

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
7 7