Re: [U-Boot] Veyron-speedy u-boot

[Simon Glass]

Hi Tomeu,

On 17 February 2017 at 03:36, Tomeu Vizoso  wrote:
> On 17 February 2017 at 10:18, Riley Baird  wrote:
>> Hi Tomeu and Simon,
>>
>> Thanks for giving me pointers on how the system works and how to get
>> u-boot onto it. I'll try and get it working over the next couple of
>> days.
>>
>> I'm very glad that it's possible to chainload and the output comes out
>> on the laptop screen, because I got a spreadsheet to work out how much
>> it would cost to build a servo, and it was much more expensive than I
>> thought! :)
>
> Depending on what you plan to do with the machine, serial output can
> be very handy, specially if you want to run automated tests to
> validate whatever you end up doing with it.
>
> Simon will know more about this, but I thought that the CPU UART lines
> are separate in the flex cable, so you may be able to find pads in the
> board that you can solder to.

Yes there are on separate lines (the servo connector) but it is a bit
tricky to solder onto. You need a special connector which is cheap,
but fine-pitched.

>
> Regards,
>
> Tomeu
>
>>
>> Thanks again,
>>
>> Riley

Regards,
Simon
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] Veyron-speedy u-boot

[Vagrant Cascadian]

> I'm very glad that it's possible to chainload and the output comes out
> on the laptop screen

Really excited to hear about your work on this!

I'd be happy to test it on a veryon-speedy system I have available;
Please feel free to CC me with updates.

live well,
  vagrant


signature.asc
Description: PGP signature
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] Veyron-speedy u-boot

[Tomeu Vizoso]

On 17 February 2017 at 10:18, Riley Baird  wrote:
> Hi Tomeu and Simon,
>
> Thanks for giving me pointers on how the system works and how to get
> u-boot onto it. I'll try and get it working over the next couple of
> days.
>
> I'm very glad that it's possible to chainload and the output comes out
> on the laptop screen, because I got a spreadsheet to work out how much
> it would cost to build a servo, and it was much more expensive than I
> thought! :)

Depending on what you plan to do with the machine, serial output can
be very handy, specially if you want to run automated tests to
validate whatever you end up doing with it.

Simon will know more about this, but I thought that the CPU UART lines
are separate in the flex cable, so you may be able to find pads in the
board that you can solder to.

Regards,

Tomeu

>
> Thanks again,
>
> Riley
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] Veyron-speedy u-boot

[Tomeu Vizoso]

Hi Riley,

On 16 February 2017 at 21:44, Simon Glass  wrote:
> Hi Riley,
>
> On 15 February 2017 at 17:31, Riley Baird  wrote:
>
>> 3. Do I just have to sign u-boot-dtb.img with vbutil_kernel before
>> dd-ing it onto a USB, or do I have to do something else to make the
>> right image?
>
> I normally start up U-Boot from scratch, but it sounds like you are
> chain-loading it.

When chainloading, depthcharge will load and execute u-boot from a
fixed address, and U-Boot needs to be told about it.

I chainloaded U-Boot on a nyan chromebook like this:

https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big=35bcb399c0d78ba6a050cc775d467ee75ed06923

The important bit is changing u-boot's CONFIG_SYS_TEXT_BASE according
to depthcharge's CONFIG_KERNEL_START.

https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/master/board/nyan_big/defconfig#11

You may need to add some padding as shown in the .its file, but I
don't remember now why CONFIG_SYS_TEXT_BASE cannot be adjusted instead
(almost 2 years have passed already).

I think you can ignore the EAE commit in that branch because that code
has been rewritten in u-boot since.

Good luck,

Tomeu
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] Veyron-speedy u-boot

[Riley Baird]

Hi Tomeu and Simon,

Thanks for giving me pointers on how the system works and how to get
u-boot onto it. I'll try and get it working over the next couple of
days.

I'm very glad that it's possible to chainload and the output comes out
on the laptop screen, because I got a spreadsheet to work out how much
it would cost to build a servo, and it was much more expensive than I
thought! :)

Thanks again,

Riley
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] Veyron-speedy u-boot

[Simon Glass]

Hi Riley,

On 15 February 2017 at 17:31, Riley Baird  wrote:
>
> Hi Simon,
>
> I've tried porting u-boot to the veyron-speedy Chromebook, based upon
> the veyron-minnie patch.
>
> I've attached a patch with my changes to this email.
>
> However, when I boot, all I get is a black screen. So, I have some
> questions:
>
> 1. Does u-boot show output to the laptop's screen, or do I have to make
> a serial console?

It should show on both if all is well.

> 2. If I have to make a serial console, where do I do this/what is the
> pin layout?

You need a servo connector on the board - see here:
https://www.chromium.org/chromium-os/servo

> 3. Do I just have to sign u-boot-dtb.img with vbutil_kernel before
> dd-ing it onto a USB, or do I have to do something else to make the
> right image?

I normally start up U-Boot from scratch, but it sounds like you are
chain-loading it.

In that case I'm not sure what to do as I have not tried it. Your
steps sound correct.

I've copied Tomeu who may know how to do this. If you figure it out it
would be great to get a patch to README.rockchip.

Regards,
Simon
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] Veyron-speedy u-boot

[Riley Baird]

Hi Simon,

I've tried porting u-boot to the veyron-speedy Chromebook, based upon
the veyron-minnie patch.

I've attached a patch with my changes to this email.

However, when I boot, all I get is a black screen. So, I have some
questions:

1. Does u-boot show output to the laptop's screen, or do I have to make
a serial console?
2. If I have to make a serial console, where do I do this/what is the
pin layout?
3. Do I just have to sign u-boot-dtb.img with vbutil_kernel before
dd-ing it onto a USB, or do I have to do something else to make the
right image?

Yours thankfully,

Riley Baird
diff --git a/arch/arm/dts/Makefile b/arch/arm/dts/Makefile
index eb68c204bb..a2b1283658 100644
--- a/arch/arm/dts/Makefile
+++ b/arch/arm/dts/Makefile
@@ -33,6 +33,7 @@ dtb-$(CONFIG_ARCH_ROCKCHIP) += \
 	rk3288-veyron-jerry.dtb \
 	rk3288-veyron-mickey.dtb \
 	rk3288-veyron-minnie.dtb \
+	rk3288-veyron-speedy.dtb \
 	rk3288-rock2-square.dtb \
 	rk3288-evb.dtb \
 	rk3288-fennec.dtb \
diff --git a/arch/arm/dts/rk3288-veyron-speedy.dts b/arch/arm/dts/rk3288-veyron-speedy.dts
new file mode 100644
index 00..666e797cf3
--- /dev/null
+++ b/arch/arm/dts/rk3288-veyron-speedy.dts
@@ -0,0 +1,190 @@
+/*
+ * Google Veyron Speedy Rev 1+ board device tree source
+ *
+ * Copyright 2015 Google, Inc
+ *
+ * This file is dual-licensed: you can use it either under the terms
+ * of the GPL or the X11 license, at your option. Note that this dual
+ * licensing only applies to this file, and not this project as a
+ * whole.
+ *
+ *  a) This file is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License as
+ * published by the Free Software Foundation; either version 2 of the
+ * License, or (at your option) any later version.
+ *
+ * This file is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ * GNU General Public License for more details.
+ *
+ *  Or, alternatively,
+ *
+ *  b) Permission is hereby granted, free of charge, to any person
+ * obtaining a copy of this software and associated documentation
+ * files (the "Software"), to deal in the Software without
+ * restriction, including without limitation the rights to use,
+ * copy, modify, merge, publish, distribute, sublicense, and/or
+ * sell copies of the Software, and to permit persons to whom the
+ * Software is furnished to do so, subject to the following
+ * conditions:
+ *
+ * The above copyright notice and this permission notice shall be
+ * included in all copies or substantial portions of the Software.
+ *
+ * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+ * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+ * OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+ * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+ * HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+ * WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+ * OTHER DEALINGS IN THE SOFTWARE.
+ */
+
+/dts-v1/;
+#include "rk3288-veyron-chromebook.dtsi"
+#include "cros-ec-sbs.dtsi"
+
+/ {
+	model = "Google Speedy";
+	compatible = "google,veyron-speedy-rev9", "google,veyron-speedy-rev8",
+		 "google,veyron-speedy-rev7", "google,veyron-speedy-rev6",
+		 "google,veyron-speedy-rev5", "google,veyron-speedy-rev4",
+		 "google,veyron-speedy-rev3", "google,veyron-speedy-rev2",
+		 "google,veyron-speedy", "google,veyron", "rockchip,rk3288";
+
+	panel_regulator: panel-regulator {
+		compatible = "regulator-fixed";
+		enable-active-high;
+		gpio = < 14 GPIO_ACTIVE_HIGH>;
+		pinctrl-names = "default";
+		pinctrl-0 = <_enable_h>;
+		regulator-name = "panel_regulator";
+		startup-delay-us = <10>;
+		vin-supply = <_sys>;
+	};
+
+	vcc18_lcd: vcc18-lcd {
+		compatible = "regulator-fixed";
+		enable-active-high;
+		gpio = < 13 GPIO_ACTIVE_HIGH>;
+		pinctrl-names = "default";
+		pinctrl-0 = <_1v8_disp_en>;
+		regulator-name = "vcc18_lcd";
+		regulator-always-on;
+		regulator-boot-on;
+		vin-supply = <_wl>;
+	};
+
+	backlight_regulator: backlight-regulator {
+		compatible = "regulator-fixed";
+		enable-active-high;
+		gpio = < 12 GPIO_ACTIVE_HIGH>;
+		pinctrl-names = "default";
+		pinctrl-0 = <_pwr_en>;
+		regulator-name = "backlight_regulator";
+		vin-supply = <_sys>;
+		startup-delay-us = <15000>;
+	};
+};
+
+ {
+	power-supply = <_regulator>;
+};
+
+_alert0 {
+	temperature = <65000>;
+};
+
+_alert1 {
+	temperature = <7>;
+};
+
+ {
+	/delete-property/pinctrl-names;
+	/delete-property/pinctrl-0;
+
+	force-hpd;
+};
+
+ {
+	power-supply= <_regulator>;
+};
+
+ {
+	pinctrl-names = "default";
+	pinctrl-0 = <_int_l>;
+};
+
+ {
+	rockchip,pctl-timing = <0x215 0xc8 0x0 0x35 0x26 0x2 0x70 0x2000d
+		0x6