Your ROOT_URL in app.ini is https://src.whiteboxsystems.nl/ but you are visiting http://src.whiteboxsystems.nl/Whitebox/u-boot/src/commit/862d9296dd11ec2901dbb1b290262eaed4d85690/board/sbc8641d You should set ROOT_URL correctly, otherwise the web may not work correctly.
upstream u-boot with additional patches for our devices/boards: https://lists.denx.de/pipermail/u-boot/2017-March/282789.html (AXP crashes) ; Gbit ethernet patch for some LIME2 revisions ; with SPI flash support
 
 
 
 
 
 
u-boot/board/sbc8641d
Paul Gortmaker ecdc3df611 sbc8641d: increase monitor size from 256k to 384k 10 years ago
..
Kconfig kconfig: remove redundant "string" type in arch and board Kconfigs 11 years ago
MAINTAINERS Add board MAINTAINERS files 11 years ago
Makefile Driver/DDR: Moving Freescale DDR driver to a common driver 12 years ago
README sbc8641d: increase monitor size from 256k to 384k 10 years ago
ddr.c Driver/DDR: Moving Freescale DDR driver to a common driver 12 years ago
law.c
sbc8641d.c fdt: Allow ft_board_setup() to report failure 11 years ago

README

Wind River SBC8641D reference board
===========================

Created 06/14/2007 Joe Hamman
Copyright 2007, Embedded Specialties, Inc.
Copyright 2007 Wind River Systems, Inc.
-----------------------------

1. Building U-Boot
------------------
The SBC8641D code is known to build using ELDK 4.1.

$ make sbc8641d_config
Configuring for sbc8641d board...

$ make


2. Switch and Jumper Settings
-----------------------------
All Jumpers & Switches are in their default positions. Please refer to
the board documentation for details. Some settings control CPU voltages
and settings may change with board revisions.

3. Known limitations
--------------------
PCI:
The PCI command may hang if no boards are present in either slot.

4. Reflashing U-Boot
--------------------
The board has two independent flash devices which can be used for dual
booting, or for u-boot backup and recovery. A two pin jumper on the
three pin JP10 determines which device is attached to /CS0 line.

Assuming one device has a functional u-boot, and the other device has
a recently installed non-functional image, to perform a recovery from
that non-functional image goes essentially as follows:

a) power down the board and jumper JP10 to select the functional image.
b) power on the board and let it get to u-boot prompt.
c) while on, using static precautions, move JP10 back to the failed image.
d) use "md fff00000" to confirm you are looking at the failed image
e) turn off write protect with "prot off all"
f) get new image, i.e. "tftp 200000 /somepath/u-boot.bin"
g) erase failed image: "erase FFF00000 FFF5FFFF"
h) copy in new image: "cp.b 200000 FFF00000 60000"
i) ensure new image is written: "md fff00000"
k) power cycle the board and confirm new image works.