2021-07-14T05:25:38Z

Aguti:

__TOC__



<h1> STM32CubeIDE </h1>
<h2> Installation </h2>

<h3> Linux </h3>

Last release of STM32CubeIDE can be obtained here: https://www.st.com/en/development-tools/stm32cubeide.html. <br>
For Debian like distributions (e.g. ubuntu), download the STM32CubeIDE-DEB file. To download it, you will need to provide name and a valid email address.

Unzip the file (e.g. <FILE> = en.st-stm32cubeide_1.0.1_3139_20190612_1256_amd64.deb_bundle)

<pre>
unzip <FILE>.sh.zip
</pre>

It will generate a .sh file.
Give it permits for execution.

<pre>
chmod 777 <FILE>.sh
</pre>

Finally, execute the installation
<pre>
sudo ./<FILE>.sh
</pre>

You must accept all license agreements.

<h3> Windows </h3>

Last release of STM32CubeIDE can be obtained here: https://www.st.com/en/development-tools/stm32cubeide.html. <br>
For Windows like distributions, download the STM32CubeIDE-Win file. To download it, you will need to provide name and a valid email address.

Unzip the file and execute the binary. Follow all steps and accept all conditions.

<h3> MAC </h3>
Last release of STM32CubeIDE can be obtained here: https://www.st.com/en/development-tools/stm32cubeide.html. <br>
For MAC like distributions, download the STM32CubeIDE-MAC file. To download it, you will need to provide name and a valid email address.

Unzip the file and execute the binary. Follow all steps and accept all conditions.

<b> IMPORTANT </b> Some problems have been reported related to lasts versions of STM32CubeIDE-MAC, where the code generator does not include macro definitions for the peripheral of nucleo-boards. Last version correctly tested is 1.0.0.

<h2> Hello World </h2>
In this Section a Hellow World (led blinking) example will be programmed on a NUCLEO-F446RE board:

<ul>
<li> Open STM32CubeIDE </li>
<li> Select where to store the workspace. This will be the folder where different projects could be stored. </li>
<li> Select <b> Start new STM32 project </b> </li>
<li> A microcontroller or board should be selected. In our case, a NUCLEO-F446RE will be used.
Then, select <b> board selector </b> and search part number <b> Nucleo-F446RE </b>. Once chosen, press <b> Next </b> </li>
<li> Chose a Project name (e.g. ledp) and keep the rest of parameters as they are. Press <b> Finish </b></li>
<li> The STM32CubeIDE will ask if you want Initialize all peripherals with their default Mode. Answer <b> Yes </b> </li>
<li> The STM32CubeIDE will inform that yhis kind of projects is associated with the STM32CubeMx prespective and will ask if you want to open this perspective now. Answer <b> Yes </b>. <br>
Download of required libraries will start. It could take long for the first time depending on your connection settings. </li>
<li> Once the project is open, on the left side on the "Project Explorer", look for <i> Src -> main.c </i>. <br>
Inside the code, look for the <i> while(1) </i> sentence in the <i> main(void) </i> function, and fill it as follows:
<pre>
while (1)
{
HAL_GPIO_TogglePin(LD2_GPIO_Port, LD2_Pin);
HAL_Delay(100);
/* USER CODE END WHILE */

/* USER CODE BEGIN 3 */
}
/* USER CODE END 3 */

</pre> </li>

<li> In order to compile, Go to <i> Project -> Build All (Ctrl+B or Hammer) </i>. It should compile the code without errors. <br>
If any error appears, previous steps should be reviewed. </li>
<li> In order to start the debugger, Go to <i> Run -> Debug (F11 or bug) </i> <br>
Select STM32 MCU C/C++ Application and Press <b> OK </b> </li>
<li> Leave all configuration propeties as they are and Press <b> OK </b> </li>
<li> The STM32CubeIDE will ask if you want to switch to the debug perspective say <b> Switch </b> </li>
<li> In order to execute the code, Go to <i> Run -> Resume (F8 or Green Arrow) </i>. <br>
The led should be blinking at 100 ms. </li>

</ul>

<h2> Problems with STM32CUBEIDE </h2>
<h3> sprintf %f </h3>

All the information on this page is obtained from: http://www.nadler.com/embedded/newlibAndFreeRTOS.html
There is some errors on the implementation of malloc on STM32CubeMX, so if using some newlib fuctions (e.g. sprintf %f), the following steps must be implemented:

<ul>
<li> Remove heapX.c form Middlewares->Thirs_Party->FreeRTOS->Source->CMSIS_RTOS_V2->portable->MemMang->heap_X.c </li>
<li> Add this file to the Src directory: [[media:heap_useNewlib.txt | heap_useNewlib]] and rename it as heap_useNewlib.c</li>
<li> Comment _sbrk function on sysmem.c file; it is already implemented on heap_useNewlib.c </li>
<li> Include in FreeRTOSConfig.h the folowing directive: </li>
<pre>
#define configUSE_NEWLIB_REENTRANT 1
</pre>
<li> Go to Project -> Porperties -> MCU Settings -> Tool Settings and select float for printf and scanf from newlib-nano </li>
</ul>

<h3> IDE Flickering </h3>

First check the value of GTK_IM_MODULE in your environment by executing

<pre>
echo $GTK_IM_MODULE
</pre>

If the output is "xim", Eclipse expects it to be “ibus”.
So enter the following command in a terminal session to set it to the value.

<pre>
export GTK_IM_MODULE="ibus"
</pre>

Now if you launch Eclipse from the same terminal session, you should not experience any flickering issue.
If you launch eclipse from a desktop menu entry, then edit the .desktop file (e.g. /usr/share/applications/st-stm32cubeide-1.6.1.desktop) and put the following string in the beginning of the Exec command:

<pre>
env GTK_IM_MODULE=ibus
</pre>

E.g. Exec=env GTK_IM_MODULE=ibus /opt/st/stm32cubeide_1.6.1/stm32cubeide %F

LaTeX

2020-07-18T10:50:56Z

Aguti:

2020-07-18T10:47:49Z

Aguti:

<h1> Installation </h1>
<pre>
apt-get install texlive-full
</pre>

<h1> Templates </h1>

<ul>
<li> Trabajos Fin de Titulación: [[media:templateTFT_v2020.tgz | templateTFT_v2020.tgz ]]</li>
<li> Presentaciones: [[media:presentacion_export.tgz | pres_template.tgz]]</li>


</ul>

Some considerations:
<ul>
<li> You need to define in src/tft.tex if you want a double-side printing

<pre>
\documentclass[twoside,a4paper,11pt]{book}
</pre>
or a single-side printing
<pre>
\documentclass[oneside,a4paper,11pt]{book}
</pre>

<li> The template has two colors to be implemented for titles and headers: orange
<pre>
\usepackage[orange]{tft}
<pre>

or black

<pre>
\usepackage[black]{tft}
<pre>

<li> If compiling with latex (as with makefile provided), this line should be uncommented:
%%%% IMPORTANT TO READ %%%%%
<pre>
\usepackage[dvipdfm]{hyperref} % Use it if compiling with latex (default on makefile)
</pre>

on the contrary, if using pdflatex (as for example overleaf), this line shoudl be uncommented:
<pre>
\usepackage{hyperref} % Use if of compiling with with pdflatex (defaulton overleaf)
</pre>

</ul>

<h1> Bibtex </h1>

Bibliography style for the different elements to cite inside the document.
ALIAS is referred to the name of the bibtex element that you are going to cite it.

<h2> Article </h2>

<pre>
@ARTICLE{ALIAS,
author = {{AUTHOR}},
title = {{TITLE}},
journal = {{JOURNAL}},
volume = {{VOLUME}},
number = {{NUMBER}},
pages = {{PAGES}},
year = {{YEAR}},
}
</pre>

<h2> Collection of books </h2>

<pre>
@INCOLLECTION{ExIncollec01,
author = {{AUTHOR}},
title = {{TITLE}},
booktitle = {{BOOKTITLE}},
editor = {{EDITOR}},
publisher = {{PUBLISHER}},
address = {{ADRESS}},
pages = {{PAGES}},
year = {{YEAR}},
}
</pre>

<h2> Conference proceedings </h2>

<pre>
@INPROCEEDINGS{ExInpro01,
author = {{AUTHOR}},
title = {{TITLE}},
booktitle = {{BOOKTITLE}},
publisher = {{PUBLISHER}},
address = {{ADRESS}},
pages = {{PAGES}},
year = {{YEAR}},
}
</pre>

<h2> Technical Report </h2>

<pre>
@TECHREPORT{ALIAS,
author = {{AUTHOR}},
title = {{TITLE}},
institution = {{INSTITUTION}},
number = {{NUMBER}},
year = {{YEAR}},
}
</pre>

<h2> Books </h2>

<pre>
@BOOK{ALIAS,
author = {{AUTHOR}},
title = {{TITLE}},
publisher = {{PUBLISHER}},
address = {{ADRESS}},
year = {{YEAR}},
}
</pre>

<h2> PHD Thesis </h2>

<pre>
@PHDTHESIS{ALIAS,
author = {{AUTHOR}},
title = {{TITLE}},
school = {{SCHOOL}},
year = {{YEAR}},
}
</pre>

<h2> Web Links </h2>

<pre>
@MISC{ALIAS,
author = {{AUTHOR}},
title = {{TITLE}},
howpublished = {\url{LINK}},
year = {{YEAR}},
note = {[Online; accessed DATE]}
}
</pre>

<h1> TikZ </h1>

Some problems have been reported when compiling TikZ with TexLive 2009.

<h2> Compilation Problems </h2>
Whether compiling you get:

<pre>
I can't find file tikzlibrary
</pre>

Then, it is possible you have problems with TexLive and need to install new TexLive version.

Download TexLive 2011 image:

<pre>
wget http://ftp.oleane.net/pub/CTAN/systems/texlive/Images/texlive2011.iso
</pre>

Mount the .iso image as root:

<pre>
mount -o loop -t iso9660 texlive2011.iso /media/cdrom
</pre>

Install TexLive:

<pre>
./install-tl
</pre>

Choose the following options:

<pre>
Options -> Create SymLinks -> [Chose Standar Dirs]
Install
</pre>

<h2> Compilation works, but not pictures shown </h2>

Get last pgf package:

<pre>
wget http://downloads.sourceforge.net/project/pgf/pgf/version%202.10/ \
pgf_2.10.tds.zip?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fpgf%2F&ts= \
1338847489&use_mirror=netcologne
</pre>

Unzip the downloaded file.
Substitute the old pgp package by the new downloaded one:

<pre>
mv tex/generic/pgf/* /usr/share/texmf/tex/generic/pgf/*
</pre>

Execute as superuser:

<pre>
texhash
</pre>

<h2> DVI problems </h2>

dvipdfm does not completelly supports tikz options.
Modify it by dvipdfmx

<h1> Videos on Beamer </h1>

In [[media:videoLatexTemplate.tgz | videoLatexTemplate.tgz]] there is an example with two different options to include videos on beamer.

<ul>
<li> The first one inserts the video on the pdf.
There is a <i>video2image.sh</i> script that converts a video into different frames (.EPS).
It requires ffmpeg and sam2p.

Later on <i> animategraphics </i> is in charge of moving the frames:

<pre>
\animategraphics[autoplay,loop,width=6cm]{<NUM_FRAME>{mov/<VIDEO_FOLDER>}{<FIRST_FRAME>}{<LAST_FRAME>
</pre>

<li>
The second one inserts an image that one pressed launches a player.

<pre>
\movie[externalviewer]{\includegraphics[width=0.5cm]{figs/<FIG_ICON>}}{mov/<VIDEO_FILE>}
</pre>

</li>
</ul>

To compile you need to run:
<pre>
make videos
make
</pre>