Skip to contentSkip to conversation

am335x_boneblack: Enable fastboot flash support

PATCH New Sam Protsenko 3 participants 12 messages Feb 27, 2018 – Mar 14, 2018

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

cover am335x_boneblack: Enable fastboot flash support

Standard and recommended way to upgrade the firmware is DFU. But DFU has extremely low transmission speed (around 150 KiB/sec), thus it's a bad fit for flashing big images (like rootfs). Low DFU speed is mostly due to next reasons (kudos to Ruslan Bilovol for investigation):
1. DFU works only via EP0, per DFU specification [1]. But AM335x doesn't have DMA for EP0, according to AM335x TRM [2]: from section 16.2:

"The CPPI DMA can be used to service Endpoints 1 to 15 not
Endpoint 0. CPU access method is used to service Endpoint 0 transactions."

2. Max transmission packet size via EP0 is 64 bytes, whereas for other endpoints max transmission packet size is 512 bytes

fastboot specification [3], on the other hand, says nothing about which EP should be used (and I see that EP1 is used on BBB board). So let's enable fastboot flash support on BeagleBone Black board to provide a better way to flash big images via USB.

[1] www.usb.org/developers/docs/devclass_docs/DFU_1.1.pdf
[2] www.ti.com/lit/ug/spruh73p/spruh73p.pdf
[3] https://android.googlesource.com/platform/system/core/+/master/fastboot/README.md

Sam Protsenko (2):
omap: Fix AM335x build with enabled fastboot flash
configs: am335x_boneblack: Enable fastboot flash capability

 arch/arm/mach-omap2/utils.c        | 2 ++
 configs/am335x_boneblack_defconfig | 2 ++
 2 files changed, 4 insertions(+)
Signature · 1 line
2.16.1
#1 lore raw

PATCH 1/2 omap: Fix AM335x build with enabled fastboot flash

When enabling CONFIG_FASTBOOT_FLASH in am335x_boneblack_defconfig, next build errors and warnings occur:

arch/arm/mach-omap2/utils.c: In function ‘omap_set_fastboot_cpu’:
arch/arm/mach-omap2/utils.c:26:16: warning: implicit declaration of
function ‘omap_revision’ [-Wimplicit-function-declaration] u32 cpu_rev = omap_revision();
^~~~~~~~~~~~~
arch/arm/mach-omap2/utils.c:29:7: error: ‘DRA762_ES1_0’ undeclared
(first use in this function)

Include asm/omap_common.h explicitly to avoid those.

---
 arch/arm/mach-omap2/utils.c | 2 ++
 1 file changed, 2 insertions(+)
arch/arm/mach-omap2/utils.c +2 -0
index d11670c0ee..7d1ca274bf 100644
@@ -7,6 +7,8 @@
 #include <common.h>
 #include <asm/setup.h>
 #include <asm/arch/sys_proto.h>
+#include <asm/omap_common.h>
+
 static void do_cancel_out(u32 *num, u32 *den, u32 factor)
 {
 	while (1) {
Signature · 1 line
2.16.1
#2 lore raw

PATCH 1/2 omap: Fix AM335x build with enabled fastboot flash

Quoted 23 lines · On Tue, 27 Feb 2018 23:45:03 +0200 Sam Protsenko <[email protected]>…

When enabling CONFIG_FASTBOOT_FLASH in am335x_boneblack_defconfig, next build errors and warnings occur:

arch/arm/mach-omap2/utils.c: In function ‘omap_set_fastboot_cpu’:
arch/arm/mach-omap2/utils.c:26:16: warning: implicit declaration
of function ‘omap_revision’ [-Wimplicit-function-declaration]

              u32 cpu_rev = omap_revision();
                            ^~~~~~~~~~~~~
    arch/arm/mach-omap2/utils.c:29:7: error: ‘DRA762_ES1_0’ undeclared
              (first use in this function)

Include asm/omap_common.h explicitly to avoid those.

---
 arch/arm/mach-omap2/utils.c | 2 ++
 1 file changed, 2 insertions(+)
arch/arm/mach-omap2/utils.c +0 -0
index d11670c0ee..7d1ca274bf 100644

arch/arm/mach-omap2/utils.c line 14

Quoted 8 lines
arch/arm/mach-omap2/utils.c +2 -0
@@ -7,6 +7,8 @@
 #include <common.h>
 #include <asm/setup.h>
 #include <asm/arch/sys_proto.h>
+#include <asm/omap_common.h>
+
 static void do_cancel_out(u32 *num, u32 *den, u32 factor)
 {
 	while (1) {

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de -------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180227/408c5fda/attachment.sig>

#3 lore raw

PATCH 1/2 omap: Fix AM335x build with enabled fastboot flash

In reply to Sam Protsenko
Quoted 11 lines · Sam Protsenko

When enabling CONFIG_FASTBOOT_FLASH in am335x_boneblack_defconfig, next build errors and warnings occur:

arch/arm/mach-omap2/utils.c: In function ‘omap_set_fastboot_cpu’:
arch/arm/mach-omap2/utils.c:26:16: warning: implicit declaration of
function ‘omap_revision’ [-Wimplicit-function-declaration] u32 cpu_rev = omap_revision();
^~~~~~~~~~~~~
arch/arm/mach-omap2/utils.c:29:7: error: ‘DRA762_ES1_0’ undeclared
(first use in this function)

Quoted 3 lines

Include asm/omap_common.h explicitly to avoid those.

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180227/51fa2eea/attachment.sig>
#4 lore raw

PATCH 1/2 omap: Fix AM335x build with enabled fastboot flash

In reply to Sam Protsenko
Quoted 11 lines · Sam Protsenko

When enabling CONFIG_FASTBOOT_FLASH in am335x_boneblack_defconfig, next build errors and warnings occur:

arch/arm/mach-omap2/utils.c: In function ‘omap_set_fastboot_cpu’:
arch/arm/mach-omap2/utils.c:26:16: warning: implicit declaration of
function ‘omap_revision’ [-Wimplicit-function-declaration] u32 cpu_rev = omap_revision();
^~~~~~~~~~~~~
arch/arm/mach-omap2/utils.c:29:7: error: ‘DRA762_ES1_0’ undeclared
(first use in this function)

Quoted 5 lines

Include asm/omap_common.h explicitly to avoid those.

Applied to u-boot/master, thanks!

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180314/58540791/attachment.sig>
#5 lore raw

PATCH 2/2 configs: am335x_boneblack: Enable fastboot flash capability

In reply to Sam Protsenko
---
 configs/am335x_boneblack_defconfig | 2 ++
 1 file changed, 2 insertions(+)
configs/am335x_boneblack_defconfig +2 -0
index ed430e7130..f45e40956c 100644
@@ -17,6 +17,8 @@ CONFIG_AUTOBOOT_PROMPT="Press SPACE to abort autoboot in %d seconds\n"
 CONFIG_AUTOBOOT_DELAY_STR="d"
 CONFIG_AUTOBOOT_STOP_STR=" "
 CONFIG_FASTBOOT=y
+CONFIG_FASTBOOT_FLASH=y
+CONFIG_FASTBOOT_FLASH_MMC_DEV=1
 CONFIG_CMD_SPL=y
 # CONFIG_CMD_FLASH is not set
 # CONFIG_CMD_SETEXPR is not set
Signature · 1 line
2.16.1
#6 lore raw

PATCH 2/2 configs: am335x_boneblack: Enable fastboot flash capability

Quoted 13 lines · On Tue, 27 Feb 2018 23:45:04 +0200 Sam Protsenko <[email protected]>…
---
 configs/am335x_boneblack_defconfig | 2 ++
 1 file changed, 2 insertions(+)
(quoted diff) +0 -0

b/configs/am335x_boneblack_defconfig index ed430e7130..f45e40956c 100644 --- a/configs/am335x_boneblack_defconfig
+++ b/configs/am335x_boneblack_defconfig

(quoted diff) +0 -0
@@ -17,6 +17,8 @@ CONFIG_AUTOBOOT_PROMPT="Press SPACE to abort

autoboot in %d seconds\n" CONFIG_AUTOBOOT_DELAY_STR="d"
CONFIG_AUTOBOOT_STOP_STR=" " CONFIG_FASTBOOT=y

configs/am335x_boneblack_defconfig CONFIG_AUTOBOOT_PROMPT="Press SPACE to abort autoboot in %d seconds\n" · line 24

Quoted 5 lines
configs/am335x_boneblack_defconfig +2 -0
+CONFIG_FASTBOOT_FLASH=y
+CONFIG_FASTBOOT_FLASH_MMC_DEV=1
 CONFIG_CMD_SPL=y
 # CONFIG_CMD_FLASH is not set
 # CONFIG_CMD_SETEXPR is not set

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de -------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180227/4779bf4c/attachment.sig>

#7 lore raw

PATCH 2/2 configs: am335x_boneblack: Enable fastboot flash capability

In reply to Sam Protsenko
Quoted 1 line · Sam Protsenko
Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180227/34a02296/attachment.sig>
#8 lore raw

PATCH 2/2 configs: am335x_boneblack: Enable fastboot flash capability

In reply to Sam Protsenko
Quoted 3 lines · Sam Protsenko

Applied to u-boot/master, thanks!

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180314/7e1dd010/attachment.sig>
#9 lore raw

cover am335x_boneblack: Enable fastboot flash support

In reply to Sam Protsenko

Hi Sam,

Quoted 8 lines

Standard and recommended way to upgrade the firmware is DFU. But DFU has extremely low transmission speed (around 150 KiB/sec), thus it's a bad fit for flashing big images (like rootfs). Low DFU speed is mostly due to next reasons (kudos to Ruslan Bilovol for investigation): 1. DFU works only via EP0, per DFU specification [1]. But AM335x doesn't have DMA for EP0, according to AM335x TRM [2]: from
section 16.2:

Quoted 6 lines

"The CPPI DMA can be used to service Endpoints 1 to 15 not
Endpoint 0. CPU access method is used to service Endpoint 0 transactions."

2. Max transmission packet size via EP0 is 64 bytes, whereas for
other endpoints max transmission packet size is 512 bytes

DFU was (and still is) supposed to work on all devices - even those with very tiny resources (like st microcontrollers).

According to USB spec, EP0 is mandatory, so that is the reason for using it as a common denominator.

Just for the record - fastboot is one of the options here.

For BBB you may want to look at "dfu tftp" - which uses ETH's tftp protocol with dfu backend. It is supposed to be a remedy for problem described above.

More information at:
./doc/README.dfutftp

Of course I also don't mind using fastboot - it depends on your use case.

Quoted 11 lines

fastboot specification [3], on the other hand, says nothing about which EP should be used (and I see that EP1 is used on BBB board). So let's enable fastboot flash support on BeagleBone Black board to provide a better way to flash big images via USB.

[1] www.usb.org/developers/docs/devclass_docs/DFU_1.1.pdf
[2] www.ti.com/lit/ug/spruh73p/spruh73p.pdf
[3]
https://android.googlesource.com/platform/system/core/+/master/fastboot/README.md

Quoted 8 lines

Sam Protsenko (2):
omap: Fix AM335x build with enabled fastboot flash
configs: am335x_boneblack: Enable fastboot flash capability

 arch/arm/mach-omap2/utils.c        | 2 ++
 configs/am335x_boneblack_defconfig | 2 ++
 2 files changed, 4 insertions(+)

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de -------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180227/f5c573c9/attachment.sig>

#10 lore raw

cover am335x_boneblack: Enable fastboot flash support

Quoted 23 lines · Lukasz Majewski

Hi Sam,

Quoted 8 lines

Standard and recommended way to upgrade the firmware is DFU. But DFU has extremely low transmission speed (around 150 KiB/sec), thus it's a bad fit for flashing big images (like rootfs). Low DFU speed is mostly due to next reasons (kudos to Ruslan Bilovol for investigation): 1. DFU works only via EP0, per DFU specification [1]. But AM335x doesn't have DMA for EP0, according to AM335x TRM [2]: from
section 16.2:

Quoted 6 lines

"The CPPI DMA can be used to service Endpoints 1 to 15 not
Endpoint 0. CPU access method is used to service Endpoint 0 transactions."

2. Max transmission packet size via EP0 is 64 bytes, whereas for
other endpoints max transmission packet size is 512 bytes

DFU was (and still is) supposed to work on all devices - even those with very tiny resources (like st microcontrollers).

According to USB spec, EP0 is mandatory, so that is the reason for using it as a common denominator.

Quoted 9 lines

Just for the record - fastboot is one of the options here.

For BBB you may want to look at "dfu tftp" - which uses ETH's tftp protocol with dfu backend. It is supposed to be a remedy for problem described above.

More information at:
./doc/README.dfutftp

Thank you for the explanation, Lukasz! Didn't know that "dfu tftp" was designed to overcome that slow speed issue. Will try that.

Quoted 4 lines

Of course I also don't mind using fastboot - it depends on your use case.

Yes, I'm trying to make BBB board to be a good educational platform (we are working on some corporate courses). Main points are it's an open hardware, has a good support in upstream and has a good pricing. Anyway, my idea is to show people all the conventional methods for flashing the board, so I need both Ethernet and USB ways working.

Also, I noticed that Debian rootfs is recommended to be flashed to eMMC using SD card (and flashing is done from booted system, not from U-Boot). Although I understand that this may be easier for an end user (as it closely resembles PC way), still I can't say that I particularly like or approve that method (especially for development purposes). That's why I think that having functional USB link would be beneficial for BBB.

Quoted 32 lines
Quoted 11 lines

fastboot specification [3], on the other hand, says nothing about which EP should be used (and I see that EP1 is used on BBB board). So let's enable fastboot flash support on BeagleBone Black board to provide a better way to flash big images via USB.

[1] www.usb.org/developers/docs/devclass_docs/DFU_1.1.pdf
[2] www.ti.com/lit/ug/spruh73p/spruh73p.pdf
[3]
https://android.googlesource.com/platform/system/core/+/master/fastboot/README.md

Quoted 8 lines

Sam Protsenko (2):
omap: Fix AM335x build with enabled fastboot flash
configs: am335x_boneblack: Enable fastboot flash capability

 arch/arm/mach-omap2/utils.c        | 2 ++
 configs/am335x_boneblack_defconfig | 2 ++
 2 files changed, 4 insertions(+)

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de

#11 lore raw

cover am335x_boneblack: Enable fastboot flash support

Hi Sam,

Quoted 30 lines · Lukasz Majewski
Quoted 29 lines

Hi Sam,

Quoted 8 lines

Standard and recommended way to upgrade the firmware is DFU. But DFU has extremely low transmission speed (around 150 KiB/sec), thus it's a bad fit for flashing big images (like rootfs). Low DFU speed is mostly due to next reasons (kudos to Ruslan Bilovol for investigation): 1. DFU works only via EP0, per DFU specification [1]. But AM335x doesn't have DMA for EP0, according to AM335x TRM [2]: from section 16.2:

Quoted 6 lines

"The CPPI DMA can be used to service Endpoints 1 to 15 not
Endpoint 0. CPU access method is used to service Endpoint 0 transactions."

2. Max transmission packet size via EP0 is 64 bytes, whereas for
other endpoints max transmission packet size is 512 bytes

DFU was (and still is) supposed to work on all devices - even those with very tiny resources (like st microcontrollers).

According to USB spec, EP0 is mandatory, so that is the reason for using it as a common denominator.

Just for the record - fastboot is one of the options here.

For BBB you may want to look at "dfu tftp" - which uses ETH's tftp protocol with dfu backend. It is supposed to be a remedy for problem described above.

Quoted 6 lines
Quoted 3 lines

More information at:
./doc/README.dfutftp

Thank you for the explanation, Lukasz! Didn't know that "dfu tftp" was designed to overcome that slow speed issue. Will try that.

You may also want to try UMS (USB Mass Storage) - "ums".

It will export your BBB to be visible as USB Mass Storage device (like a pendrive).

From that point you can use dd to write MBR, rootfs, u-boot to it.

Another - good option for flashing is SWUpdate SW:

https://github.com/sbabic/swupdate

It allows very easy integration with OE/Yocto and Buildroot. What is even more important - it supports BBB out of the box:

https://github.com/sbabic/meta-swupdate-boards/tree/master/recipes-support/swupdate/swupdate

SWUpdate is a versatile tool with a loot of nice features - please read:
https://sbabic.github.io/swupdate/

Quoted 12 lines
Quoted 5 lines

Of course I also don't mind using fastboot - it depends on your use case.

Yes, I'm trying to make BBB board to be a good educational platform (we are working on some corporate courses). Main points are it's an open hardware, has a good support in upstream and has a good pricing. Anyway, my idea is to show people all the conventional methods for flashing the board, so I need both Ethernet and USB ways working.

Quoted 41 lines

Also, I noticed that Debian rootfs is recommended to be flashed to eMMC using SD card (and flashing is done from booted system, not from U-Boot). Although I understand that this may be easier for an end user (as it closely resembles PC way), still I can't say that I particularly like or approve that method (especially for development purposes). That's why I think that having functional USB link would be beneficial for BBB.

Quoted 33 lines
Quoted 11 lines

fastboot specification [3], on the other hand, says nothing about which EP should be used (and I see that EP1 is used on BBB board). So let's enable fastboot flash support on BeagleBone Black board to provide a better way to flash big images via USB.

[1] www.usb.org/developers/docs/devclass_docs/DFU_1.1.pdf
[2] www.ti.com/lit/ug/spruh73p/spruh73p.pdf
[3]
https://android.googlesource.com/platform/system/core/+/master/fastboot/README.md

Quoted 8 lines

Sam Protsenko (2):
omap: Fix AM335x build with enabled fastboot flash
configs: am335x_boneblack: Enable fastboot flash capability

 arch/arm/mach-omap2/utils.c        | 2 ++
 configs/am335x_boneblack_defconfig | 2 ++
 2 files changed, 4 insertions(+)

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH, Managing Director: Wolfgang
Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email:
wd at denx.de

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de -------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180228/110aac3a/attachment.sig>