Details on BSP 4

[AlbertT]

Hello !

In the Release Note of the BSP 4 one can read "See ResolvedDefects.html, referenced inside the file readme.html, for the list of the defects fixed in this release. Only hot fixes are listed here."

The thing is, there is no readme.html in the L3.0.35_4.0.0_130424_source.tar.gz so is it possible to get back this file please ?

Furthermore I would like to know if it's possible (and wise) to install two BSP ? I have my old one which works great and I would like to keep it. So how can I do ?

Thanks !

[LeonardoSandova]

For your second question, I can think of two options

1. BSP A on the eMMC, BSP B on the SD

2. BSP A and B on a server, prepare u-boot values to do a boot from TFTP/NFS, and have a variable to decide which to boot (e.g. setenv bootcmd 'run bootA'; setenv bootA 'setenv nfsroot=/rootfsA; setenv bootfile uImageA; run

bootargs_base bootargs_nfs;bootm'; the same logic for bootB)

Leo

[AlbertT]

Oh right. No actually I used the wrong vocabulary, I meant different versions of the BSP inside LTIB. Right now I have an install of LTIB with the old BSP and packages which is working great and I would like to keep it functional on my computer. Is it possible to have an other directory ( ltib_new) with the newer install of LTIB coming from the last BSP ? I don't know if I am clear :s

[LeonardoSandova · Accepted solution]

As you LTIB is a Linux build system, composed of packages (tarballs) and recipes (specs files) and the ltib script takes these as input and produced a rootfs. Every release, both set of files (tarballs and spec) are previously set so the building (in theory) process goes fine. So if you try to use latest specs with old packages, that wont work. My suggestion is to try always use the latest BSP, it is the most stable and has all official patches.

Leo

[AlbertT]

Ok ! I will move my modifications to the new ltib then. Thanks for your advice !