It took a while for there to be time for play...

Now running mainline u-boot and an almost mainline kernel (linux-rockchip for-next).

My power-supply looks like the limiting factor at the moment, openssl speed will happily run 2GHz @ 1.425v but to run that -multi 4 requires dropping to 1.73GHz @ 1.375v.

1.73GHz at 1.4v -multi 4 also bombs, suggesting that either the rpi powersupply or the onboard regulation just isn't beefy enough for this running full tilt.

Temps at the moment are manageble, peaking at 68C during multi4, that will of course not be the case if the speeds and voltages are bumped further. (currently using the stock heatsink and a PSU fan sat at the end of the board...)

Running headless at the moment, so sound and video not a concern. One minor niggle, especially during this crash-tastic testing is that while reboot works on Rockchip's 4.4 kernel, it doesn't seem to work with this 4.11-rc3 branch kernel.

One to dig into!

Full report once 4.12 comes out and hopefuly Stuart can add another one to his list

release flash to SDCARD

1. The bootloader of the system is written to the image
2. mainline u-boot - U-Boot 2017.09-rc2-00066-g336aee50cf-dirty (Aug 19 2017 - 11:54:21 +0300)

howto:
1. download all http://dl.fail.pp.ua/slackware/firefly-rk3288/legacy/
2. /dev/mmcblk0 - уour memory card
dd if=slack-current-miniroot_24Jul17-4.4.77-firefly_rk3288-build-20170819.img of=/dev/mmcblk0 bs=1M
dd if=slack-current-xfce_24Jul17-4.4.77-firefly_rk3288-build-20170819.img of=/dev/mmcblk0 bs=1M

1. update kernel 4.4.77
2. flash uboot to mmc: ./rkdeveloptool db rk3288_ubootloader_v1.01.06.bin
./rkdeveloptool wl 0x40 idbloader.img
./rkdeveloptool wl 0x4000 uboot.img
3. after flash uboot transfer sd -> mmc, run setup after booting

1. update kernel 4.4.93
2. update miniroot_05Nov17

slack-current-arm-miniroot_05Nov17-4.4.93-firefly_rk3288-build-20171111.img

SDcard release

1. update kernel 4.4.103
2. update miniroot_14Dec17


slack-current-arm-miniroot_14Dec17-4.4.103-firefly_rk3288-build-20171231.img.7z
slack-current-arm-xfce_14Dec17-4.4.103-firefly_rk3288-build-20171231.img.7z

SDcard release

1. update kernel 4.4.119
2. update miniroot_06Mar18


slack-current-arm-miniroot_06Mar18-4.4.119-firefly_rk3288-build-20180308.img.7z
slack-current-arm-xfce_06Mar18-4.4.119-firefly_rk3288-build-20180308.img.7z

Hey sndwvs,

I'd like to point out two things:
First: The download link of dl.fail.pp.ua/slackware/firefly-rk3288/legacy/ mentioned above is incorrect nowadays and should be dl.fail.pp.ua/slackware/images/firefly-rk3288/legacy/ instead.
Second: There is no "uboot.img" in this directory which seems to make it completely impossible to install slackware as you describe.

If you could at least fix the second issue I can happily start installing Slackware on my new Firefly board.

NoKey.

P.S. Sorry for the incomplete links but "You cannot post URLs to other sites until you have made at least 1 other post."

The download link in reply #47 does not work anymore.
And the file uboot.img is missing in the correct download directory (which I cannot post because I'm not yet allowed to post links).

the latest release is
slack-current-arm-miniroot_22May18-4.4.126-firefly_rk3288-build-20180522.img.tar.xz
slack-current-arm-xfce_22May18-4.4.126-firefly_rk3288-build-20180522.img.tar.xz

instead of uboot.img now idbloader.img


flash to mmc:
rkdeveloptool db rk3288_ubootloader_v1.01.06.bin
rkdeveloptool wl 0x40 idbloader.img
rkdeveloptool wl 0x8000 slack-current-arm-miniroot_22May18-4.4.126-firefly_rk3288-build-20180522.img
rkdeveloptool rd

flash to sdcard:
dd if=slack-current-arm-miniroot_22May18-4.4.126-firefly_rk3288-build-20180522.img of=/dev/mmcblk0 bs=10M

1 members found this post helpful.

So basically, "skip the uboot.img part in the procedure" is what you're saying?

So you're saying here is to skip the step of
in the whole procedure?

yes
so it is described on http://opensource.rock-chips.com/wiki_Boot_option

Oh, then you should really update the page you have on the Firefly rk3288 with the information you posted in reply #52.
(And now I'm cheesed that I left my firefly board @ work...)

Thank you, amended

Hmm, the (debugging) serial port remains quiet after rebooting the system (after following your install instructions).
So three questions come to mind:

1. Is there supposed to be information logged to the serial port?
2. If yes, what would be the port settings for the serial port if you do (I use 115200 8N1 no flow control)?
3. If no, what output is used for user information (VGA/HDMI/other serial port)?

(Edit: I just assured myself I didn't brick the board by reinstalling the Ubuntu image from the Firefly website with AndroidTool)

1. yes, the output to the console should be, at least uboot
2. serial port settings: 115200n8
3. i connect the monitor via hdmi, but vga outputs the same picture (the output to the monitor for the debug does not fit, you need to look through the console, it must necessarily contain information about the bootloader)

from all I put the problem in the bootloader, it or is not correct by itself, something is not written down correctly

even if the downloader loads the maps through the maskrom, you can still flash the firmware