Hi all, Is there any solution or way to use one binary supporting multiple flashes and permit users runtime configure which flash will be used? Currently, we could get a binary named redboot.bin which includes defined packages in ecos.db. In ecos.db, it seems that we are required to define only one type flash driver package in target each time. The flash.c under io folder will call flash_program, flash_read and other flash functions which implemented in corresponding flash driver. However, for reference platform, we may install multiple flashes on one platform at one time. For example, there are flash_strata and flash_toshiba. If we get a binary which includes flash_strata and flash_toshiba, how to permit users runtime configure which flash will be used? Does anybody meet same case? We thought out a way: 1. First time, boot from default flash. 2. Enter Redboot shell, run new command to configure which flash will be used? Then write this configuration information to flash. 3. Reboot. Redboot read the configuration information in flash before flash initiation. Then boot from the flash which set in configuration information. But to implement this way, we need add a new command, save configuration information to flash, read configuration information from flash and pass parameter to flash driver. All of these seem riskful. And they also change the user model of redboot. Is there any other idea or solution?
Thank you for brainstorm. Thanks. Best regards, Kylie Liang -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
