<narmstrong>
I saw the intel tentative 2y ago and I thought they stopped trying
<xdarklight>
it seems they didn't :)
warpme_ has quit [Quit: warpme_]
nemunaire has quit [Quit: quit]
nemunaire has joined #linux-amlogic
trem has joined #linux-amlogic
<ndufresne>
step one to start working my H96pro+ device, soldered some wires on the serial port
nsaenz has joined #linux-amlogic
<ndufresne>
it's quite funny that there is two USB socket on the board, for which there is no whole on the plastic case ;-P
<ndufresne>
narmstrong, what do you usually do for those random device ? there is some u-boot there, which I can stop, it loads from some internal flash, what would be a safe process to load mainline ?
<ndufresne>
(to work on loading mainline kernel, as I don't expect it to work right away)
chewitt has joined #linux-amlogic
<narmstrong>
We usually use tftp or sdcard/mmc load
<narmstrong>
But now we can use the amlogic usb protocol they use to speak to uboot with pyamlboot
<narmstrong>
If you run « update » on the u-boot prompt and you connect a type a to type a usb cable
<narmstrong>
You need to find the port connected to the OTG port...
<ndufresne>
ok, noted, I'll try around
<ndufresne>
I thought of tftp first, as that's what I use on the potato, but it didn't work
<ndufresne>
u-boot is pretty old there, U-Boot 2015.01-gbfcb9f6-dirty (Mar 09 2017 - 10:32:04)
<ndufresne>
when in linux is calls the network stmmac, but in the uboot it tries to load dwmac, would that be ?
nsaenz has quit [Ping timeout: 244 seconds]
<xdarklight>
ndufresne: which error do you get when tftp doesn't work? afair this worked for me on all Amlogic boards I had so far (even on old 32-bit Meson boards)
<narmstrong>
I won’t be surprised tftp doesn’t work on cheap tv boxes, they never use it, they use only the amlogic usb protocol to flash the device
<narmstrong>
Since gxbb we have a lot of issues with Ethernet
<narmstrong>
On amlogic u-boot
warpme_ has joined #linux-amlogic
warpme_ has quit [Client Quit]
<ndufresne>
(sorry am back)
<ndufresne>
narmstrong, i get "dwmac.c9410000: No link."
<ndufresne>
but if I boot into android, the network works
<ndufresne>
I'm new to that board, but isn't dwmac the chip on the meson8 ?
<chewitt>
that config is working fine on several S912 devices
<chewitt>
although most GXM dts are a little unloved due to the lack of usable graphics (until recently)
<ndufresne>
hehe, that's my main motivation in bootstrapping this one, panfrost driver
<ndufresne>
chewitt, the error I posted was form vendor u-boot
<chewitt>
ahh, u-boot is a mystery to me, but I have panfrost working fine
<chewitt>
(or as fine as it currently runs)
<ndufresne>
ok, at default of having a a to a usb cable, i made a bootable upgrade SDCARd from some more recent image, to flash something newer, tftp might work
<xdarklight>
ndufresne: regarding the naming: "dwmac" is the short form of "DesignWare Ethernet MAC". stmmac is the name of the Linux driver which manages the "dwmac" part (I believe the first supported SoC was a STMicro part, and later it was discovered that the driver is not STMicro specific but then the name was already set). dwmac-meson8b is driver which manages the Amlogic bits around the dwmac core (like clock generation, setting the PHY mdoe,
<xdarklight>
...)
<xdarklight>
ndufresne: narmstrong might be right with Ethernet being broken on these newer SoCs. whoever builds the u-boot needs to set the PHY mode (external RGMII PHY or internal RMII PHY) correctly, else Ethernet won't work