Version 2.00.2

Upgrading STB SDK to version 2.00.2 and adding default embedded portal sources.

CHANGELOG.md

@@ -1,4 +1,14 @@
 # Changelog of MAG Software Portal STB SDK
 
+#### Version 2.00.2 20 March 2019
+* Default sources of embedded portal have been added to SDK.
+* Now the SDK asks you if you want to install necessary packages.
+* Added new property `VER_UPDATE_API` which allows you to overwrite version of update API. This is recommended only when you cannot get it by default from root file system and for debugging purposes.
+* Added new directory `stbapi` to SDK with libraries to build STB API taken from Infomir website (these are C headers).
+
+#### Version 2.00.1 22 February 2019
+* Fixing bug with no possibility to upgrade SDK.
+* Fixing bug with allowing empty imageupdate.
+
 #### Version 2.00-beta 20 February 2019
 * Initial revision. For information about changes [go to post in project website](https://firmware.magboxes.xyz/2018/02/20/introducing-modified-stb-sdk).

README.md

@@ -4,11 +4,18 @@
 ![GitHub repo size in bytes](https://img.shields.io/github/repo-size/Nepose/MAG_Software_Portal.svg)
 ## Improved STB SDK for making firmware
 
-This is a toolchain to compile images for Infomir IPTV STBs - MAG and Aura HD. It is improved version of SDK done by Infomir corporation, manufacturer of set-top-boxes.
+This is a portable toolchain to compile images for Infomir IPTV STBs - MAG and Aura HD. It is improved version of SDK done by Infomir corporation, manufacturer of set-top-boxes.
 
 The toolchain is a part of **MAG Software Portal** project, which also includes ready-made custom firmware and wiki for Operators. This SDK comes with already set dependencies and some documentation from Infomir to better work with.
 
-To install toolchain, just clone this Git repo or download source code from releases card.
+## Installation
+
+There are two methods to prepare STB SDK on your PC:
+
+* Just clone or download GitHub repository. The simplest one if you know what is Git.
+* Use dedicated installer. This program works as a recovery disk for SDK with embedded functions of fixing broken files, its upgrading and of course installing.
+
+I don't favour any of those methods. If you want to set all dependencies automatically and make toolchain usable for first time, use installer.
 
 ## Functions of toolchain
 * Compile / prepare following parts of firmware:
@@ -33,6 +40,7 @@ The toolchain doesn't support MAG 424/425 STBs. The toolchain is available **onl
 * `embedded_portal` -> SDK for embedded portal, refer to *Build embedded portal* section.
 * `includes` -> directory with some libraries used by SDK, you don't have to do anything there ;)
 * `multicast_dhcp` -> directory with utilities to connect to STB with multicast or DHCP protocol.
+* `stbapi` -> libraries to build STB API for Qt.
 * `stm` -> utilities to build imageupdate for STM STBs.
 
 <cite>According to official Infomir wiki page about STB SDK:</cite>
@@ -149,6 +157,8 @@ cd includes/
 
 Nothing more to explain, it will just check and download latest version if you want. Of course you can also update by `git pull` :)
 
+The second method is to use installer, choose correct option from main menu, specify path to your SDK installation and that's all.
+
 ## Contribution
 
 Every contribution is appreciated, like in entire project. For more information go to website of MAG Software Portal https://firmware.magboxes.xyz. In case of any problems you can write in any of forums listed on page (or enter new thread in your forum, which is also very appreciated) or open Issue or Pull Request in repository of SDK.

broadcom/img_make.sh

@@ -77,19 +77,18 @@ fi
 [ "$ROOTFS_PATH" == "" ] && not_existing "Path to root file system" "ROOTFS_PATH"; export ROOTFS_PATH="$ROOTFS_PATH"
 [ "$KERNEL_PATH" == "" ] && not_existing "Path to kernel" "KERNEL_PATH"; export KERNEL_PATH="$KERNEL_PATH"
 
-# Get update API
-if [ ! -f $ROOTFS_PATH/etc/VerUpdateAPI.conf ] ; then
-    echo -e "[ ${OutputRed}ERR${OutputWhite} ] Update API version is not defined!!!\n"
-    exit 1;
-fi
-
 # Look if image output exists
 if [[ "$IMAGE_OUTPUT" == "" ]]; then
 	export IMAGE_OUTPUT="./imageupdate"
 	echo "[${OutputYellow}WARN!${OutputWhite}] The image output property was empty. Defaulting to \"./imageupdate\"..."
 fi
 
-verUpdateAPI=`cat $ROOTFS_PATH/etc/VerUpdateAPI.conf | awk '{printf  $1; exit;}'`
+# Look for update API version
+[ "$VER_UPDATE_API" != "" ] && verUpdateAPI=$VER_UPDATE_API || verUpdateAPI=`cat $ROOTFS_PATH/etc/VerUpdateAPI.conf | awk '{printf  $1; exit;}'`
+if [ ! -f $ROOTFS_PATH/etc/VerUpdateAPI.conf ] ; then
+    echo -e "[ ${OutputRed}ERR${OutputWhite} ] Update API version is not defined!!!\n"
+    exit 1;
+fi
 
 echo "[ ${OutputBlue}TRY${OutputWhite} ] Make rootfs image $ROOTFS_PATH"
 ./mk_rfs.sh $ROOTFS_PATH

embedded_portal/default_mini/index.html

@@ -0,0 +1,14 @@
+<!doctype html>
+<html>
+<head>
+	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+	<title>new MAG 200-250</title>
+
+	<script type="text/javascript">
+		window.location = 'system/pages/loader/index.html';
+	</script>
+</head>
+
+<body>
+</body>
+</html>

embedded_portal/default_mini/info.json

@@ -0,0 +1,4 @@
+{
+	"time": "Mon, 28 Jan 2019 10:32:58 GMT",
+	"hash": "2e8c7644cac92d8d990376ca9e0f292438e2f4c8"
+}