I'm fairly new to the Rock64 boards and recently decided it would be fun to play around with one. I bought the 2GB RAM version plus 16GB eMMC and power adapter. I used Etcher to flash ayufan's minimal artful arm64 image which worked great! It booted and I plugged in the network and was able to shell in just fine. I ran into problems, however, when I attempted to attach this GPS board to it: https://store.uputronics.com/index.php?r...duct_id=81. After plugging it all in I can see that the GPS board powers up just fine and even acquires a GPS signal and starts the TIMEPULSE LED going...BUT the main board doesn't boot. The white power LED is on and the red standby LED is solid with the green LED on the left side of the ethernet jack on but it doesn't appear to actually boot at all. Any suggestions?
Note: my first thought was that the expansion board could be drawing too much power but I looked at the spec sheet for the ublox MAX-8Q and it only draws up to a max of 65mA. The power supply supposedly outputs up to 3000mA which I can only imagine should be sufficient. The expansion board is designed for any of the Raspberry Pi+ models and when I look at the traces from the ublox chip to the header on the GPS board it seems that the pins do match up where they should.
I have configured u-boot on my rock64 to load boot scripts over tftp and it works well.
What I'm missing is a little understanding how to setup kernel boot over tftp.
I've got kernel image compiled using ayufan-rock64/linux-build repo.
It's there linux-build/kernel/arch/arm64/boot/Image
System.map shows that these addresses:
Quote:ffffff8008080000 t _head
ffffff8008080000 T _text
ffffff8008080800 T __exception_text_start
ffffff8008080800 T _stext
ffffff8008080800 T do_undefinstr
I'm not sure whether they are physical but u-boot doesn't use MMU
Can I use this kernel for booting over tftp or I have to use another configuration for this.
If yes then what load address and entry point should I use for mkinage:
Quote:mkimage -A arm64 -T kernel -O linux -C none -n 'Kernel Image' -a $load addres -e $entry point -d boot-image linux-build/kernel/arch/arm64/boot/Image
What memory layout does rock64 have?
To be more specific, what is RAM start address?
Does it matter where I load kernel image in u-boot:
1st of all I must admit the board looks EXTREMELY beautiful. Great work. Thank you.
The only thing I didn't see on the PCB is screw holes for cooling.
Currently I'm using Odroids and VIMs. But your solution looks far better.
And basic software questions prior buying: 0) Do you have x11 Mali driver for your board for normal hardware acceleration?
1) Do you release Mainline Kernel linux (Ubuntu/Arch linux) software for your board?
2) Do you have a github kernel repo if I need a custom build and do you work on it constantly?
I've been playing with my A64+ for the last few days.... for some reason, whenever I leave my A64 "alone" for a few hours, it reboots (this is just an educated guess) and enters some kind of maintenance mode: if I connect it to a monitor, it shows the "usual" spinning gears. However, it never gets out of it (or at least, it doesn't in 32 hours). Power cycling does not help - the next boot is always to spinning gears, unless (of course) I re-flash the SD-Card.
I've tried 3 times with two different cards - same thing. Examining the SD, I've seen that in fact widows did resize the data partition to reclaim the unused space at the end of the card. Tonight I'm going to give it another spin, but this time I've expanded the partition on my PC right after re-flashing the ffu. I'm using IoT Dashboard to do the flashing (in case it matters).
What I'd like to know is..... Is this an expected behavior? Did any of you experience the same thing?
Are there any news about black Pinebook with 1080p screen? (https://forum.pine64.org/showthread.php?tid=5614)
Probably, there is already some information about the approximate price or the release date? Will the hardware be updated too? Is it worth waiting for more RAM or a new processor? (Rockchip?)
In my opinion, the black case looks very wonderful.
I'm interested in connecting more than a single PCIe device to the RockPro64.
I know that it woud be possible to use a card which includes a PCIe switch chip to connect multiple PCI Express devices to the RockPro64, but that would be expensive (as well as adding latency and power usage), so I wondered if there was a simpler solution, using a simple breakout card (or custom add-in card), along with a suitable firmware config e.g. device tree overlay, to reconfigure the PCIe x4 slot as four logical PCIe x1 ports?
A custom PCIe card (or breakout card) could then be used to connect multiple PCIe x1 devices to the slot. The application I had in mind was connecting four Asmedia ASM1061 SATA AHCI host adaptors to give 8 SATA ports for a NAS setup.
I know that various Intel chipsets support this sort of flexible PCIe configuration, but didn't know if the RK3399 did? Any ideas?
There is already published some PDF with a sketch of the measurements in mm of the [url=https://forum.pine64.org/forumdisplay.php?fid=99][/url] ROCKPRO64 SBC board and
the location of the connectors.
it's 2D better, I still work in 2D and 3D files do not work for me ..
Hey has anyone tried working with tensorflow? I've tried installing it on armbian but keep getting stuck or it throws errors that seem to be unreasonable at me, albeit I'm a noob to armbian and most of Linux.
If it actually is completely impossible to install tensorflow at the moment on this platform, what inexpensive microcomputer can run an operating system that is supported by tensorflow? Thanks in advance!