Bticino F454 - Revision history

Joft: Add info about toolchains used for firmware v2.00.xx .

2016-10-04T18:42:16Z

Add info about toolchains used for firmware v2.00.xx .

Joft: Add details on the serial connector.

2016-10-03T16:53:28Z

Add details on the serial connector.

Joft: Add info about firmware v2.00.xx kernel configurations.

2016-10-03T15:41:19Z

Add info about firmware v2.00.xx kernel configurations.

Joft: Add info about firmware version 2.00.xx kernels.

2016-10-03T15:16:20Z

Add info about firmware version 2.00.xx kernels.

Joft: /* Boot loader */ RBL, fix ambiguity in various statements.

2015-03-12T08:32:12Z

Boot loader: RBL, fix ambiguity in various statements.

Joft: /* Hardware */ Add info about serial interfaces.

2015-02-28T12:18:25Z

Hardware: Add info about serial interfaces.

Joft: /* Tool Chain */ Start to fill in this section.

2015-02-28T10:28:10Z

Tool Chain: Start to fill in this section.

Joft: /* Origin */ Point to n recently published U-Boot source code, show grep version from binary.

2015-02-27T20:02:36Z

Origin: Point to n recently published U-Boot source code, show grep version from binary.

Joft: /* U-Boot */ Note on new bticino github repo, minor other changes ...

2015-02-25T21:26:41Z

U-Boot: Note on new bticino github repo, minor other changes ...

Joft: /* Origin */ Update and add further links to kernel source tree on github.

2015-02-25T20:45:45Z

Origin: Update and add further links to kernel source tree on github.

@@ Line 237: / Line 237: @@
 TI's [http://arago-project.org Arago Project] also refers to that specific tool chain version [http://arago-project.org/wiki/index.php/Getting_CodeSourcery_Toolchain] - to be used not only for kernel, but to compile everything - from bootloader to userspace applications.
-This tool chain can also be found, pre-installed, in bticino's [http://www.myopen-legrandgroup.com/devices/gateways/m/f454_-_003598/45317.aspx F454/003598 SDK]. The SDK is a Ubuntu 12.04 Live DVD, with some non-standard programs like this tool chain pre-installed.
+=== Firmware v1.00.xx ===
 == Boot loader ==

@@ Line 138: / Line 138: @@
 === Accessibility ===
-Bticino's F454 [http://www.homesystems-legrandgroup.com/technicalDocuments/type5/MQ00519-b-EN.pdf Technial Sheet] documents there is a ''Serial connector RS232'' behind the hatch of the F454's case, left of the 3 LEDs.
+Bticino's F454 [http://www.homesystems-legrandgroup.com/technicalDocuments/type5/MQ00519-b-EN.pdf Technial Sheet] documents there is a ''Serial connector RS232'' behind the hatch of the F454's case, left of the 3 LEDs. It is the connector with the white case, right below the Mini-USB connector.
-It is a 5 pin male connector of an, at least to your author, unknown type ''(TODO)''. In general it seems more than likely that this connector is going to UART0, the system console. However it remains unclear, which pins are what (3 needed at least: GND, TX, RX) and what the voltage levels are ''(TODO)''. Of course, the designation ''RS232'' is a pretty clear statement and suggests that the PCB includes a MAX232 or similar and thus it could be directly connected to a PCs serial port/USB-to-serial.
+The 5 pin male connector is of an, at least to your author, unknown type. One of the plugs tried so far is a ''TODO'', but the notches at the sides do not match. However the pin spacing and the position of the pin row relative to the bottom side do match. So, a pocket knife makes the plug fit.
-''TODO: try it out, determine pins''
+Starting at the left hand side, the first 4 pins show a voltage of 3.3V compared to the right most pin, when using simple multimeter. So, this ''Serial connector RS232'' '''CANNOT''' be a standard [https://en.wikipedia.org/wiki/RS-232 RS-232] interface. It turns out that it is a 3.3V tolerant [https://en.wikipedia.org/wiki/Universal_asynchronous_receiver/transmitter UART] interface. And that is what one would expect of such a SoC like the DM365, anyway.
 == Storage ==

@@ Line 408: / Line 408: @@
 </source>
-It turns out that all three different versions known so far do have exactly the same configuration. The only differences is the typical timestamp which is placed at the beginning of Linux kernel configuration files.
+It turns out that all four different firmware v1.00.xx kernel versions known so far do have exactly the same configuration. The configuration of the firmware v2.00.xx kernel versions are different from the v1.00.xx ones. However within the v2.00.xx ones it is again the same configuration. The only differences within one family, say between v1.00.xx and v1.00.yy is the typical timestamp which is placed at the beginning of Linux kernel configuration files.
 {| class="wikitable"
@@ Line 430: / Line 430: @@
 |Thu Sep  4 18:03:13 2014
 |3e3aaf37a4158eeb1e92417aa51bc16b
 |}
-The following list shows some of the enabled features - '''''besides the expected ones''''' (support for the Davinci SoC and it's peripherals). Features, which might be surprising to see and/or which are most likely not really used by the current firmware:
+The following list shows some of the enabled features of both, v1.00.xx and v2.00.xx kernels '''''besides the expected ones''''' (support for the Davinci SoC and it's peripherals). Features, which might be surprising to see and/or which are most likely not really used by the current firmware:
 * core
@@ Line 454: / Line 466: @@
 **  NFS v2 and v3 server (module)
 **  SMB  (module)
 On an F454 running firmware version v1.00.37, the following modules are loaded:

@@ Line 345: / Line 345: @@
 All these assumption about on what version the used kernel is based on become certain facts after finding one of bticino's public Git repositories on [http://github.com GitHub]: http://github.com/MyOpenCommunity/linux-davinci-medium . It comprises the commit with the hash [http://github.com/MyOpenCommunity/linux-davinci-medium/commit/8ed3c294c0a661d818ffab0b94c381289740d429 8ed3c294c0a661d818ffab0b94c381289740d429], which occurs in /proc/version as an amendment to the kernel version.
-Newer versions of the firmware apparently use slightly newer kernel versions/commits, which can also be found in the mentioned [http://github.com/MyOpenCommunity/linux-davinci-medium repository]. All these commits are part of a branch called [https://github.com/MyOpenCommunity/linux-davinci-medium/tree/f454_1 f454_1].
+Newer versions of the firmware apparently use slightly newer kernel versions/commits, which can also be found in the mentioned [http://github.com/MyOpenCommunity/linux-davinci-medium repository]. Commits of firmware version 1.00.xx kernels are part of a branch called [https://github.com/MyOpenCommunity/linux-davinci-medium/tree/f454_1 f454_1]. Commits of firmware version 2.00.xx kernels can be found on the [https://github.com/MyOpenCommunity/linux-davinci-medium/tree/basi basi] branch.
 {| class="wikitable"
@@ Line 372: / Line 372: @@
 |v2.6.32.17-davinci1
 |[http://github.com/MyOpenCommunity/linux-davinci-medium/commit/f56c4d42a889cb71bd92d101e9e2b0e847ca1603 f56c4d42a889cb71bd92d101e9e2b0e847ca1603]
 |}

@@ Line 220: / Line 220: @@
 === ARM ROM boot loader - RBL ===
-After power-on the DM365's ARM processor starts with executing the ARM ''ROM boot loader'' (RBL), which most likely resides in an address space starting at 0x00018000. The RBL searches for a ''user boot loader'' (UBL). In case of the F454 the current assumption is that it does so via DM365's interface SPI0 - on an attached SPI EEPROM.
+After power-on the DM365's ARM processor starts with executing the ARM ''ROM boot loader'' (RBL), which resides in an on-chip ROM mapped to 0x08000 / 0x18000 (Instruction/Data; size: 16KiB). The RBL searches for a ''user boot loader'' (UBL). In case of the F454 the current assumption is that it does so via DM365's SPI0 interface - on an attached SPI EEPROM.
-The RBL specifically searches for a certain ''magic number'' (32 bit), which is 0xa1acedxx. At this point in time it remains a little bit unclear if this number has to be at offset 0x0 of the EEPROM (most likely) or if it can reside within a certain range of bytes/pages/whatever.
+The RBL expects to find a certain ''magic number'' in the first 32 bit of the EEPROM. This number has be either ''0xa1aced00'' (24 bit addressing) or ''0xa1aced01'' (16 bit addressing).
-The magic number must be followed by 20 bytes of additional information, like UBL executable entry point, size of the UBL, start and load addresses, flags ... TI's [http://www.ti.com/lit/pdf/sprufg5 DM36x User's Guide] has all the details, chapter 11.2.5, page 188.
+The magic number must be followed by 20 bytes of additional information, like UBL executable entry point, size of the UBL, start and load addresses, flags ... TI's [http://www.ti.com/lit/pdf/sprufg5 DM36x User's Guide ARM Subsystem] has all the details, chapter 11.2.5, page 188.
-After having found this piece of information, the RBL acts accordingly: loads the UBL into the ARM's TCM RAM0 and RAM1 (2x 16 KiB, at address space offset 0x0000 and 0x4000 respectively) and jumps to the specified entry point.
+After having found this piece of information, the RBL acts accordingly: loads the UBL into the ARM's on-chip TCM RAM0 and RAM1 (2x 16 KiB, at address space offset 0x0000 and 0x4000 respectively) and jumps to the specified entry point.
 === User boot loader - UBL ===

@@ Line 86: / Line 86: @@
 ''Question: Why DM365 - why does the F454 need this 720p en/decoding capability. Wouldn't a DM355 also do it? Related to video door entry systems?''
 == Storage ==
@@ Line 148: / Line 205: @@
 ''TODO: more''
 = Software =

@@ Line 154: / Line 154: @@
 == Tool Chain ==
-''TODO''
+For its DaVinci SoCs, to compile Linux kernels, TI recommends [http://processors.wiki.ti.com/index.php/DaVinci_GIT_Linux_Kernel#Overview] CodeSourcery's ''GNU Toolchain for ARM Processors'', version ''2009q1-203'', which can be downloaded as a [http://www.codesourcery.com/sgpp/lite/arm/portal/package4573/public/arm-none-linux-gnueabi/arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 tar archive] (or a [http://www.codesourcery.com/sgpp/lite/arm/portal/package4573/public/arm-none-linux-gnueabi/arm-2009q1-203-arm-none-linux-gnueabi.bin self-extracting archive], ''bigger not recommended'').
 == Boot loader ==

@@ Line 223: / Line 223: @@
 root@basi:~# fw_printenv | grep ^ver= | sed 's#^ver=##'
 U-Boot 2010.12-rc2-3ed2d264ae41bbc05f961a8aececdd636cdb1582 (Jul 23 2012 - 11:40:09)
 </source>
 So it is obviously based on release candidate 2 for U-Boot 2010.12 . The Git commit hash, which follows ''-rc2-'' should tell us about the exact source code version.
-Unfortunately, as of this writing, your author hasn't been able to find any public source repository, which does comprise a commit with this hash. However there is the very strong assumption that the source code the F454's U-Boot binary was built from is at least based on this [https://gitorious.org/ gitorious.org] repository: [https://gitorious.org/medium_platform/u-boot/source/f319d40632e77470d06d9d758633d106079eccf9: medium_platform/u-boot] .
+bticino published the source code on their [http://github.com/MyOpenCommunity MyOpenCommunity] site on [http://github.com GitHub]. It resides in a Git repository called http://github.com/MyOpenCommunity/u-boot-davinci-medium . As of this writing it's ''master'' branch of this repository is ahead by 3 newer commits. A link to the above mentioned commit hash is: [http://github.com/MyOpenCommunity/u-boot-davinci-medium/commit/3ed2d264ae41bbc05f961a8aececdd636cdb1582 3ed2d264ae41bbc05f961a8aececdd636cdb1582].
-It turns out that this repository's ''master'' branch (commit [https://gitorious.org/medium_platform/u-boot/commits/f319d40632e77470d06d9d758633d106079eccf9 f319d40]) has been derived from:
+It turns out that this copy of U-Boot has been derived from:
 * arago-project.org [http://arago-project.org/git/projects/?p=u-boot-davinci.git;a=summary U-Boot for DaVinci], tag [http://arago-project.org/git/projects/?p=u-boot-davinci.git;a=commit;h=6ebeaa9ef432217def1213e9cc611771d6412b1c DEV.DavinviBSP.03.01.01.38] (commit [http://arago-project.org/git/projects/?p=u-boot-davinci.git;a=commit;h=6ebeaa9ef432217def1213e9cc611771d6412b1c 6ebeaa9])
@@ Line 235: / Line 239: @@
 Note that arago-project.org does also have a tag [http://arago-project.org/git/projects/?p=u-boot-davinci.git;a=commit;h=1af61f3b812b51f6f41ff37cd4a52ce6cfb21d7a DEV.DavinviBSP.03.01.01.39], which is currently equivalent to where the branch ''r39'' points to. And more interesting: this tag is just one single commit further than where tag DEV.DavinviBSP.03.01.01.38 points to.
-To avoid confusion: bticino's more recent online presence regarding Git repositories on [http://github.com GitHub], named [http://github.com/MyOpenCommunity MyOpenCommunity], has a repository called [http://github.com/MyOpenCommunity/u-boot-davinci-medium-v2 u-boot-davinci-medium-v2]. However this is newer version, based on denx.de's U-Boot (commit [http://git.denx.de/?p=u-boot.git;a=commit;h=d41b3cc16fd97da23900f79e8fefdeedeebde8f6 d41b3cc]), which is somewhere between versions [http://git.denx.de/?p=u-boot.git;a=commit;h=ebbf0d20aa85f623c49b7ed3349ebfea450c152d v2013.01-rc2] and [http://git.denx.de/?p=u-boot.git;a=commit;h=3ae7b240ad8c723d02aa79654220a07049b7ae4d v2013.01-rc1] - and thus does '''not''' represent what is running on at least the F454 under investigation.
+To avoid confusion: The [http://github.com/MyOpenCommunity MyOpenCommunity] also has a repository called [http://github.com/MyOpenCommunity/u-boot-davinci-medium-v2 u-boot-davinci-medium-v2]. This is newer version, based on denx.de's U-Boot (commit [http://git.denx.de/?p=u-boot.git;a=commit;h=d41b3cc16fd97da23900f79e8fefdeedeebde8f6 d41b3cc]) - somewhere between versions [http://git.denx.de/?p=u-boot.git;a=commit;h=ebbf0d20aa85f623c49b7ed3349ebfea450c152d v2013.01-rc2] and [http://git.denx.de/?p=u-boot.git;a=commit;h=3ae7b240ad8c723d02aa79654220a07049b7ae4d v2013.01-rc1]. So later shipped F454 devices ''might'' have a U-Boot binary installed which is based on this newer source code base.
 ==== Operation ====

@@ Line 271: / Line 271: @@
 We recognize 2 important hints within the ''Image Name'' of the uImage: ''Arago'' and the version amendment ''psp03.01.01.39''. Together with the amendment ''-davinci1'' seen within /proc/version, these 2 hints make a very strong suggestion that the used Linux kernel version is based on one managed by TI as part the [http://arago-project.org/ Arago project]: tag [http://arago-project.org/git/projects/?p=linux-davinci.git;a=commit;h=161e942bbb6e3603bccd1548865cfcce0910f1cc DEV.DaVinciPSP.03.01.01.39] within Git repository git://arago-project.org/git/projects/linux-davinci.git .
-All these assumption about on what version the used kernel is based on become certain facts after finding one of bticino's public Git repositories on [http://gitorious.org gitorious.org]: http://gitorious.org/medium_platform/linux . It comprises the commit with the hash [http://gitorious.org/medium_platform/linux/commits/8ed3c294c0a661d818ffab0b94c381289740d429 8ed3c294c0a661d818ffab0b94c381289740d429], which occurs in /proc/version as an amendment to the kernel version.
+All these assumption about on what version the used kernel is based on become certain facts after finding one of bticino's public Git repositories on [http://github.com GitHub]: http://github.com/MyOpenCommunity/linux-davinci-medium . It comprises the commit with the hash [http://github.com/MyOpenCommunity/linux-davinci-medium/commit/8ed3c294c0a661d818ffab0b94c381289740d429 8ed3c294c0a661d818ffab0b94c381289740d429], which occurs in /proc/version as an amendment to the kernel version.
-Newer versions of the firmware apparently use slightly newer kernel versions/commits. However the commit hashes of the newer versions were not yet found in any public repository.
+Newer versions of the firmware apparently use slightly newer kernel versions/commits, which can also be found in the mentioned [http://github.com/MyOpenCommunity/linux-davinci-medium repository]. All these commits are part of a branch called [https://github.com/MyOpenCommunity/linux-davinci-medium/tree/f454_1 f454_1].
 {| class="wikitable"
@@ Line 284: / Line 284: @@
 |Thu Nov 8 17:02:20 CET 2012
 |v2.6.32.17-davinci1
-|[http://gitorious.org/medium_platform/linux/commits/8ed3c294c0a661d818ffab0b94c381289740d429 8ed3c294c0a661d818ffab0b94c381289740d429]
+|[http://github.com/MyOpenCommunity/linux-davinci-medium/commit/8ed3c294c0a661d818ffab0b94c381289740d429 8ed3c294c0a661d818ffab0b94c381289740d429]
 |-
 |v1.00.37
 |Thu Nov 8 17:02:20 CET 2012
 |v2.6.32.17-davinci1
-|[http://gitorious.org/medium_platform/linux/commits/8ed3c294c0a661d818ffab0b94c381289740d429 8ed3c294c0a661d818ffab0b94c381289740d429]
+|[http://github.com/MyOpenCommunity/linux-davinci-medium/commit/8ed3c294c0a661d818ffab0b94c381289740d429 8ed3c294c0a661d818ffab0b94c381289740d429]
 |-
 |v1.00.45
 |Fri Jan 17 17:16:09 CET 2014
 |v2.6.32.17-davinci1
-|59f7438a4e85d0a2b1b985a65500a9f05366f6ce
+|[http://github.com/MyOpenCommunity/linux-davinci-medium/commit/59f7438a4e85d0a2b1b985a65500a9f05366f6ce 59f7438a4e85d0a2b1b985a65500a9f05366f6ce]
 |-
 |v1.00.51
 |Thu Sep 4 18:03:59 CEST 2014
 |v2.6.32.17-davinci1
-|f56c4d42a889cb71bd92d101e9e2b0e847ca1603
+|[http://github.com/MyOpenCommunity/linux-davinci-medium/commit/f56c4d42a889cb71bd92d101e9e2b0e847ca1603 f56c4d42a889cb71bd92d101e9e2b0e847ca1603]
 |}