Remerciez-le!

Remerciez @Admin pour avoir partagé cet document gratuitement, de la manière la plus simple, en partageant sur les réseaux sociaux.

Porting guide 1 - Introduction -- This is a small porting guide for OMAPFlash It contains an introduction to the modi ?cations that may be necessary in order to get OMAPFlash working on a new board or with a new memory device -- Porting to a new platform

- Introduction -- This is a small porting guide for OMAPFlash It contains an introduction to the modi ?cations that may be necessary in order to get OMAPFlash working on a new board or with a new memory device -- Porting to a new platform -- The main goal when trying to get OMAPFlash to work on a new plaform is to get th e second loader ported to the platform In general this should not require the recompilation of the code or modi ?cation of the sec ond loader's code base The starting point will be to create a board con ?guration ?le for the new platform For the binary installed version of OMAPFlash board con ?guration ?les are fou nd in Targets Con ?gurations For the source code version of OMAPFlash board con ?gurations ?les are found in host Targets Con ?gurations In order to add support for a new platform it is necessary to add a new board con ?guration ?le to the con ?guration folde r Once the board con ?guration ?le has been created it will need to be added to the content of omap ash nd txt present in of the binary release or host o f the source code release This ?le allows OMAPFlash to ?nd the board con ?gur ation ?le and pairs it with a platform tag to be used with the -p option for OM APFlash When modifying the ?le simply add a new line to it -pheriphe ralbootreopen -boardcon ?g where is the platform name use a new name for the new platform is an id number provided by the OMAP device during per ?pheral boot over UART or USB along with the number speci ?es whether the OMAP detected should be a High Security 'HS' or General Purpose 'GP' type second loader ?le speci ?es the second loader to use with the combination of platform and and the is the newly added board con ?guration An example could be SDPMDDRHYNIX G GP Targets nd- Downloaders dnldstartupomap gp g nd -pheriphalbootreopen - boardcon ?g Targets Con ?gurations con ?gurationsdp hynix g txt which speci ?es that if you specify the platform SDPMDDRHYNIX G through the p option to OMAPFlash and the OMAP device detected is v GP the second lo ader to use is 'Targets nd- Downloaders dnldstartupomap gp g nd' and the bo ard con ?guration to use is 'Targets Con ?gurations con ?gurationsdp hynix g txt' Note that the binary installation currently comes with second loaders supporting memory sizes of Mb Gb Gb Gb and Gb for GP and HS devices dnldstartupomap gp m nd dnldstartupomap gp g nd dnldstartupomap gp g nd OMAP GP w Mb SDRAM - OMAP GP w Gb SDRAM - OMAP GP w Gb SDRAM Cdnldstartupomap gp g nd dnldstartupomap gp g nd dnldstartupomap hs m nd dnldstartupomap hs g nd dnldstartupomap hs g nd dnldstartupomap hs g nd dnldstartupomap hs g nd dnldstartupomap gp g nd dnldstartupomap gp g nd dnldstartupomap