create_uboot dependencies?

[Martin Stein]

We have a Serial-to-USB cable connected to the Serial interface of the
board and a USB port of the testing machine. Then you can catch the
output via 'picocom' for instance. The implementation of the UART driver
is [1]. It uses 1 stop bit, a baudrate of 115200, and no parity. So, the
following works for me:

sudo picocom -p n -b 115200 /dev/ttyUSB0

Even if your Genode doesn't come up you should at least see some output
from the Uboot like this:

U-Boot 2015.10-00237-g92e40f5-dirty (Dec 04 2015 - 15:37:04 +0100)
CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: Wandboard rev B1
I2C:   ready
DRAM:  2 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
No panel detected: default to HDMI
Display: HDMI (1024x768)
In:    serial
Out:   serial
Err:   serial
Net:   FEC [PRIME]
Hit any key to stop autoboot:  1
U-Boot SPL 2015.10-00237-g92e40f5-dirty (Dec 04 2015 - 15:37:04)


Did this help?

[1] base/include/drivers/uart/imx.h

Am 18.08.2017 um 18:03 schrieb Steven Harp:
> Martin:
> 
> Yes, that worked well. Happily I had the older toolchain handy,
> and it compiles uboot without error.
> 
> Unfortunately, the output is not yet working for me (no serial out).
> I'm still trying to puzzle out the recipe to get Genode images running
> on the Wand Quad.   Genode Labs perhaps has a preferred solution for 
> testing on this platform--is there a web page or README that discusses?
> Maybe tftpboot from one of the Wand linux/uboot images could work?
> 
> Any advice or examples would be much appreciated. 
> 
> Thanks,
>   Steve
> 
> 
> On 08/18/2017 07:10 AM, Martin Stein wrote:
>> Hi Steven Harp,
>>
>> Thank you for this hint!
>> It's obviously a bug in the 'create_uboot' tool. The tool uses the Genode tool
>> chain and since the last update of this tool cain I didn't test whether they're
>> still fine with each other.
>>
>> One quick work-around for you would be to download the 16.05 toolchain [1],
>> unpack it to an individual directory (no 'P' flag) [2], and adapt your
>> create_uboot to use the other tool chain [3].
>>
>> I will have a more detailed look at the problem these days and provide a
>> long-term fix as soon as possible.
>>
>> I hope this helped?
>>
>> Cheers,
>> Martin