View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001259 | UBoot | U-Boot | public | 2012-08-22 17:17 | 2014-01-28 11:31 |
| Reporter | Keller | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Product Version | armStoneA8-V1.1 | ||||
| Target Version | fss5pv210-V2.0 | Fixed in Version | fss5pv210-V2.0 | ||
| Summary | 0001259: Combine PicoCOM3 and PicoMOD6 to a common S3C64XX platform | ||||
| Description | Currently PicoCOM3 and PicoMOD6 need different U-Boot binaries. Combine them to a common fss3c64xx platform to allow a single binary image to be used on both boards. This involves dynamic configuration of some things (e.g. prompt string, RAM size, etc.) depending on the board type. Some of this information can be taken from the nboot_args structure that is passed from NBoot to U-Boot starting with NBoot V12. | ||||
| Forum Link | |||||
|
|
Collapse board/F+S/picocom3 and board/F+S/picomod6 to a new platform board/F+S/fss3c64xx. In the same spirit, combine include/configs/picocom3.h and include/configs/picomod6.h to form the new file include/configs/fss3c64xx.h. This also requires changes in boards.cfg. Change the new platform so that it behaves as similar as possible to the S5P platform. This requires at least NBoot V12, because we need the nboot_args that are not passed to U-Boot in earlier versions of NBoot. |
