AnsweredAssumed Answered

Automating the firmware build a couple of questions re versions and the create_fsbl_project.tcl

Question asked by G4DCP on Oct 2, 2017
Latest reply on Oct 4, 2017 by mhennerich

I am trying to setup an autobuild so  I can produce a modified firmware for the ASDALM-PLUTO.

 

Most of what I am doing seems to be working fine except for two puzzle areas.

 

1.  The VERSIONS file is being built wrongly it works in my manual builds but in the auto builds it gets a wrong hdl version (So this may be a deeper error) The firmware however works, the incorrect version as shown by the info.html is :-

 

Serial104473222a87000719002a00dc48d5b09a
Buildv0.22-2-gfcc8
LinuxLinux pluto 4.9.0-gf70f1fc93206 #1 SMP PREEMPT Sun Oct 1 21:37:30 BST 2017 armv7l GNU-Linux
U-BootU-Boot PlutoSDR v0.20-PlutoSDR-00041-g4bdff59 (May 26 2017 - 13:07:26 +0200)
FPGAdev_altera_15_1_xilinx_2015_4-636-ged12
Root FSv0.20-5352-g5d1cd
IIOLibrary version: 0.10 (git tag: v0.10)

The FPGA line is sourced out of the VERSIONS file which seems to show a very old FPGA build however the start of the binary file for the FPGA has the correct version in its header.

 

Could you let me know how and where the VERSION file gets its values?

 

2. In trying to resolve problem 1 I noticed something strange in the build logs:-

&1|21:52:44.980 vivado -mode batch -source system_project.tcl >> pluto_vivado.log 2>&1 &1|22:05:03.481 make[1]: Leaving directory '/var/lib/go-agent/pipelines/ADALM-PLUTOFW/Plutosdr-fw/hdl/projects/pluto' &1|22:05:03.546 rm -Rf build/sdk &1|22:05:03.562 bash -c "source /opt/Xilinx/Vivado/2016.2/settings64.sh && xsdk -batch -source scripts/create_fsbl_project.tcl" &1|22:05:09.982  &1|22:05:09.982 Note:: "set_workspace" command is Deprecated. Use "setws" command &1|22:05:09.983  &1|22:05:09.983 Note:: "create_hw_project" command is Deprecated. Use "createhw" command &2|22:05:10.855 No protocol specified &2|22:05:10.893 Unable to init server: Could not connect: Connection refused &1|22:05:21.662 Starting SDK. This could take few seconds... done &1|22:05:39.191 hsi::generate_target: Time (s): cpu = 00:00:13 ; elapsed = 00:00:13 . Memory (MB): peak = 376.051 ; gain = 8.164 ; free physical = 1980 ; free virtual = 12296 &2|22:05:39.542 No protocol specified &2|22:05:39.543 Unable to init server: Could not connect: Connection refused &1|22:05:39.592 Hardware platform project 'hw_0' created successfully. &1|22:05:39.594  &1|22:05:39.594 Note:: "create_app_project" command is Deprecated. Use "createapp" command &1|22:05:41.073 INFO: [Hsi 55-1698] elapsed time for repository loading 1 seconds &1|22:05:44.790 WARNING : No interface that uses file system is available  &1|22:05:44.790  &1|22:05:47.342 WARNING: [Hsi 61-9] Current Software design may not be compatible with "zynq_fsbl" app. Tool is ignoring the MSS file specified in the app directory &1|22:06:01.759 generate_target: Time (s): cpu = 00:00:14 ; elapsed = 00:00:14 . Memory (MB): peak = 400.668 ; gain = 12.852 ; free physical = 1917 ; free virtual = 12278 &1|22:06:01.781 hsi::generate_app: Time (s): cpu = 00:00:14 ; elapsed = 00:00:14 . Memory (MB): peak = 400.668 ; gain = 12.852 ; free physical = 1919 ; free virtual = 12279 &1|22:06:02.269 Application project 'fsbl' created successfully. &1|22:06:02.270  &1|22:06:02.270 Note:: "build_project" command is Deprecated. Use "projects -build" command &1|22:06:02.298 Building All Projects... &1|22:06:02.336 Building workspace &1|22:06:02.336 Building '/fsbl_bsp'

 

This looks worrying is it relevant to my first question or  is it normal? These appear to be just warnings but look a bit worrying. I am aware that a lot of noise warnings are normal in the firmware build but wonder if this area is normal.

 

Once again many thanks for the help that I have already received.


Peter D Hull (G4DCP)

Outcomes