Relative Content

Tag Archive for firmware

How to test the same software on all products in a product line?

In my team we have been working on a firmware for a product. The product was released some years ago but we still implement new features in the firmware and regularly provide a new firmware for our customers. Recently we have developed a new product which use the same firmware as the first one. Of course, we had to change the firmware to allow for some new capabilities (while still keeping functionality for existing product intact).

Customer ask firmware source file

Recently my company was asked by a customer to develop a control board that includes firmware and PCB layout development. After finishing development the customer will buy the control boards at certain quantity every year.

Is this theoritically possible to create a full android device simulator

I want to adjust firmware components, or to have opportunity to test something on an android device. A problem is that usually modern devices prohibit to recover a brick for free.
Theoritically it is possible to program a full device simulator, primary to handle first low level stages (like bootloaders, and possibly boot, recovery, fastboot), not necessary to even program a workable screen and therefore OS, but preferable. A one way i know how to get hardware info is look into /proc using root.
In /proc/iomem there is common device memory map,
In /proc/devtree there is list of hardware components, versions and their base address to interact with,
/proc/devices has list of some unknown devices and /proc/cpuinfo has a list of all cpus with their version. Some additional useful info how that individual device work i think may be found in product documentation.
To find base address of images may be copied a scetter file from firmware and, some additional possibly not needed addresses may be resolved by unpacking boot and recovery.