Port-arm archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: NanoPi R2S



Aye?

Well, from what I can see it doesn't seem to be seeing the xhci
controller here... Assuming I remember the spec sheet right, the
secondary NIC is attached through that?

It could be something with the compiled dtb file?  It has seemed
pretty stable otherwise, a little warm until I got sysutils/estd set
up.

arm64# usbdevs -vvv
Controller /dev/usb0:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000),
NetBSD(0x0000), rev 1.00(0x0100)
  Hub(0x09), Hub(0x00), proto 1
 port 1 powered
Controller /dev/usb1:
addr 1: full speed, self powered, config 1, OHCI root hub(0x0000),
NetBSD(0x0000), rev 1.00(0x0100)
  Hub(0x09), Hub(0x00), proto 0
 port 1 powered
arm64#

On Sun, Jun 13, 2021 at 4:36 PM Jason Mitchell <jmitchel%bigjar.com@localhost> wrote:
>
> On 6/12/21 7:58 PM, Brandon Wickelhaus wrote:
> > Hello there,
> >
> > Last year a user was trying to get a NanoPi R2S working, and well I
> > had ordered one to see about trying it for myself.
> >
> > All in all it worked just as the Port Wiki suggested, though I
> > couldn't get Jason's fancy new installboot options to work with the
> > results from pkgsrc wip/u-boot-nanopi-r2s, I decided to manually write
> > it with trial and error, and the boat fit the pattern of the other
> > rockchip boards.
> >
> > dd if=/usr/pkg/share/u-boot/u-boot-rockchip.bin of=/dev/rsd1d seek=64 conv=sync
> >
> > I did this directly to one of Jared's generic aarch46 current images.
> >
> > I then copied the dtb file which was 'somewhere' in the pkgsrc work
> > directory for the package, as it wasn't in the +CONTENTS file for the
> > package.  I placed it on the MS-DOS partition in the dtb/rockchip
> > directory.
> >
> > I attached the serial link to the board and booted it, u-boot success,
> > then it used the efi-booter and the kernel loaded fine.
> >
> > Only gripes sofar were that I had to run it for a short time without
> > the case on (It comes with a metal case) where the ttl cable can only
> > be attached once its flipped over and no longer has its heatsink
> > attached.  I got a temp warning due to that, but it seemed otherwise
> > fine in the time it took me to verify the network was up.
> >
> > Only the WAN port of the two network ports works, dmesg follows.  If
> > anyone wants me to test something in order to get the LAN port up,
> > feel free to contact me.
> >
> > I'd suggest either  moving the wip/u-boot for it over, or perhaps if
> > an update is needed doing that, and I can test it.
> >
> > ---- snip
>
> It's interesting that the second NIC doesn't show up at all. When I
> tested this (using an RK3328 image) both NIC's showed up, but the other
> NIC (ure0) was unstable and caused frequent crashes. NetBSD reported
> that it was using an unknown something (Realtek chip, maybe?). I'd be
> curious to see the output of usbdevs -vvv to see if the card is
> recognized at all.
>


Home | Main Index | Thread Index | Old Index