Outdated and Incomplete Documentation for WP77xx

IoT Modules WP Series
1

The following documents have processes or procedure that are either outdated or incomplete. These documents form the basis of your board support package and must be updated

  • WP77xx Firmware Release 15.1 Components - Build your custom Device Image
    • Linux Distribution: boot-yocto.cwe Your yocto recipes explicitly prevent this image, and all other images that start with boot- from being created.
    • You also provide no official guidance on how to make the Yocto environment after you download it
      • Random forum posts are not a substitute for official documentation
      • leaf does not allow for the more advanced Yocto usage (see secure boot guide below) and therefor cannot be the only tooling for these guides
  • AirPrime - WP Series - Customer Secure Boot
    • (see prior comment about boot- images being disabled)
    • The secure boot document references the boot- images so again, this need to be edited to reflect the change and a new procedure must be written (the little kernel is packaged separately in appsboot*.cwe images; how are the keys updated their as well )
    • Steps like the following are unacceptable as even the referenced file is uncommented. Package the signed images into CWE images. For details, refer to the following script in the build system output – meta-swi/meta-swi-mdm9x28/recipes-core/images/mdm9x28-image-cwe.inc.

The overall feedback is that these guides should show commands and expected outputs for all steps.

2

For building the bootloader and yocto image, you can download the yocto source and just type "make " in ubuntu 16. You can see this thread:

For secure boot, you can also see this document.

3

@jyijyi this is still not acceptable

  • Lacks lead up steps
    • How did you make the image that needed to be signed ( download the R16, extract, type make wp77xx, etc.)
  • Insecure and Improper Release channel
    • A random forum comment is not where you should have a Secure Boot document
    • Anyone can attach a docx file in this forum with wrong instructions in an attempt to subvert the security we are trying to implement.
    • Developers should not have to fish in forums to find critical information
  • Version Compatibility Updates
    • You don’t need to rewrite the guide, but you should mention somewhere that these steps work with release WP77XX R15 and WP76XX R17, especially because you jumped major revisions for the Linux kernel (4.14) and yocto environments (3.1) since the guide was released. I see a lot of commits in meta-swi regarding signing since WP76XX R16 as well.
4

Regarding the other forum post, basically the same points:

  • Forum is not an acceptable critical documentation release channel
  • If you used COTs tools, like Docker and Yocto, as they were intended (IE: inheritance mechanisms) you would have to document significantly less
  • Until then, you need to formally document all steps. You can’t bait my managers with official documentation with Sierra letterhead and then switch it out for random word documents in a forum.
5

Have you officially requested these documents through distributor?
That should be the normal path