Bureaucrats, dave_user, Administrators
8,154
edits
Changes
→Misc
==Handling different product models==
It is quite common to manufacture different product models on the top of the same hardware platform. In such cases, it is convenient to use a unified software for all models. DAVE Embedded Systems provides the [[ConfigID_and_UniqueID|ConfigID]] mechanism that can be exploited to achieve this goal. ConfigID can be exploited at boot loader level, at kernel level, and at application level.
= Deployment Checklist =
Here below, a list of topics that should be taken into account for Product design and deployment on the field.
This checklist tries to cover the most known project/product aspects which should be - ''at least'' - carefully understood and answered before a product is installed on the field.
== Non volatile storage ==
* Partitioning scheme
** Endurance/reliability: NOR/NAND/SD/eMMC evaluation respect to reliability, costs, write cycles, data retention, data dimension
** Redundant scheme or Recovery partition (A/B or A + recovery)
== Boot sequence ==
* boot time requirements (in terms of ''seconds'') and behaviours
* BSP boot time analisys
** u-boot, kernel, minimal rfs
** application startup
== Applications ==
* special framework required: Java, Qt, Javscript engines
== Accessibility ==
*serial console: availability (vs security)
** startup configuration: boot stop with special character
== Upgrade ==
* upgrade on the field
* Local or Remote
** with recovery or redundant partitions
*** tracking of upgrade failures for maintenance information
** On The Field: removable peripherals usage (SD, USB) and ''"non expert"'' upgrade
== Security ==
* "Security by design": take into account security requirements at the beginning of the project
* useful guideline formalized by da Microsoft for [https://azure.microsoft.com/it-it/blog/azure-sphere-is-here-public-preview-and-dev-kits-now-available Azure Sphere]
== Recovery and service ==
* complete automatic Disaster recovery
* complete - manually assisted - Disaster recovery
* partial Disaster recovery
* restore to Manufacturer configuration
* Service Mode
== Licensing==
* specific license requirements, i.e. Qt library
== Certification ==
* EMC certification
* other specific certification requests (or document requirement like MTBF, etc.)
== Various ==
* Watchdog
** in case of WDT intervention: tracking of watchdog event for software analysis
* MAC addresses handling: see [http://standards.ieee.org/develop/regauth/index.html IEEE registration authority]
* runtime automatic detection and configuration: possible usage of [ConfigID_and_UniqueID ConfigID] technique