I have ordered several apalis imx6 modules. I established a process to flash those modules and during this process I modify the u-boot variable after booting via NFS. But, as you mentioned in release notes, since the 2.5 BSP, u-boot variable location has been moved to the end of the eMMC boot area before the config block in/dev/mmcblk0boot0. So I have to know if you could provide u-boot / BSP version information according to the apalis module SN or if I have to write a snippet script to detect this by software.
I am not exactly sure what you are asking for. You mean you would like to get a list from us as to what serial number has what exact BSP version factory pre-installed? While we do of course have all production test log files I don’t quite see why that would be that much useful for a customer to know beforehand. One can just fire up the module and sees what version is installed, not?
Platform Manager Embedded Linux
You definitely understand what I’m asking for. The flash process is done by a person without software skills. So, I can’t ask to this person to launch a terminal etc … It will be easier to proceed like : this SN is delivered with this BSP / uboot version so in the script I set correctly the fw_env.config in the nfs rootfs. Could you please provide those log files ?
To check BSP version of your board use command
cat /etc/issue .
You get V… something that is your BSP version.
Below information says BSP version is V2.6
root@apalis-imx6:/sys/class# cat /etc/issue
| | .-. o o
| | |-----.-----.-----.| | .----…-----.-----.
| | | __ | —’| ‘–.| .-’| | |
| | | | | |— || --’| | | ’ | | | |
‘—’—’–’–’–. |-----’’----’’–’ ‘-----’-’-’-’
The Angstrom Distribution \n \l
Angstrom v2015.12 - Kernel \r
You definitely understand what I’m asking for.
No, sorry. What exactly is it that you are really trying to achieve?
The flash process is done by a person without software skills. So, I can’t ask to this person to launch a terminal etc … It will be easier to proceed like : this SN is delivered with this BSP / uboot version so in the script I set correctly the fw_env.config in the nfs rootfs.
But the pre-installed BSP version should really be irrelevant as the customer anyway will have to load his desired BSP with potential customisation, not?
Production programming can either be done as per legacy procedure described in the following article on our developer website independent on the pre-installed firmware version. Alternatively starting with V1.1B modules they come pre-installed with the Toradex Easy Installer which in addition to the legacy procedure also allows unattended production deployment via Ethernet, SD card or USB memory stick.
What else could you be asking for?
Could you please provide those log files ?
As we produce hundreds of thousands of modules we don’t really plan to make any of this production data universally available for our customers, sorry.