Difference between revisions of "Proj-2013-2014-Python-STM32F4"

From air
Jump to navigation Jump to search
Line 37: Line 37:
 
* STM32 develop environment
  
* STM32 develop environment
   
−
* Add USB device
 +
Add USB device
 
Create a new udev rule in /etc/udev/rules.d/45-usb-stlink-v2.rules:
 
Create a new udev rule in /etc/udev/rules.d/45-usb-stlink-v2.rules:
 
SUBSYSTEM=="usb", ATTR{idVendor}=="0483", ATTR{idProduct}=="3748", MODE="660", GROUP="plugdev"
  
SUBSYSTEM=="usb", ATTR{idVendor}=="0483", ATTR{idProduct}=="3748", MODE="660", GROUP="plugdev"
 
To reboot :
  
To reboot :
 
$ sudo service udev restart
  
$ sudo service udev restart
  +
  +
Download the GNU/ARM toolchain
  +
Download the Linux current installation tarball from
  +
https://launchpad.net/gcc-arm-embedded/+download
  +
$ tar -xvjf gcc-arm-none-eabi-xxxxxxxxxxxxxxxxxx-linux.tar.bz2
  +
Add the fallowing to your ~/.bashrc
  +
export PATH=$PATH:~/xxxxxxx/gcc-arm-none-eabi-xxxxxxxxx/bin
  +
$ source ~/.bashrc
  +
To check :
  +
$ arm-none-eabi-gcc --version
  +
If you get an error message “bash : ... file does not exist”.
  +
Maybe it is caused by the difference between 32bit and 64bit system. Try :
  +
$ sudo apt-get install ia32-libs*
  +
  +
Download and Build STLINK
  +
STLINK is for programming and debugging firmware.
  +
you'll first need to install a couple of packages:
  +
$ sudo apt-get install autoconf pkg-config libusb-1.0 git
  +
Retrieve a copy of the STLINK source:
  +
$ git clone https://github.com/texane/stlink.git
  +
Build the code following the instructions in the README, with:
  +
$ ./autogen.sh
  +
$ ./configure
  +
$ make
  +
As a sanity check, look in ~/st-link and you should see st-util, st-flash, etc...
  +
You may check if the board could be connected by execute st-util.
  +
If it does not work please confirm if the rule you added in the first step corresponds your system.
  +
   
 
* Try the official examples of ST on the cards
  
* Try the official examples of ST on the cards

Revision as of 18:05, 9 February 2014

Introduction

Python_sur_STM32F4


Team


Objectives

Points à traiter

  • Modidification des Makefile
 utilisation de arm-none-eabi-g++ et des bonnes options
  • support STL
  Voir https://github.com/andysworkshop/stm32plus
  • Lib C
Voir newlib
  • gc Garbage Collection
 Voir  tinygc http://tinygc.sourceforge.net/
  • libprce
 Voir T-Rex is a minimalistic regular expression http://tiny-rex.sourceforge.net/ http://sourceforge.net/projects/tiny-rex/


Progress

project start : 13/01/2014

Week 1 (13/01 - 19/01)

  • Project discovery
  • Research of related projects

Week 2 (20/01 - 26/01)

  • STM32 develop environment
   Add USB device
       Create a new udev rule in /etc/udev/rules.d/45-usb-stlink-v2.rules: 
       SUBSYSTEM=="usb", ATTR{idVendor}=="0483", ATTR{idProduct}=="3748", MODE="660", GROUP="plugdev"
       To reboot :
       $ sudo service udev restart

   Download the GNU/ARM toolchain
       Download the Linux current installation tarball from 
       https://launchpad.net/gcc-arm-embedded/+download
       $ tar -xvjf gcc-arm-none-eabi-xxxxxxxxxxxxxxxxxx-linux.tar.bz2
       Add the fallowing to your ~/.bashrc
       export PATH=$PATH:~/xxxxxxx/gcc-arm-none-eabi-xxxxxxxxx/bin
       $ source ~/.bashrc
       To check :
       $ arm-none-eabi-gcc --version
       If you get an error message “bash : ... file does not exist”. 
       Maybe it is caused by the difference between 32bit and 64bit system. Try :
       $ sudo apt-get install ia32-libs*

   Download and Build STLINK
       STLINK is for programming and debugging firmware.
       you'll first need to install a couple of packages:
       $ sudo apt-get install autoconf pkg-config libusb-1.0 git
       Retrieve a copy of the STLINK source:
       $ git clone https://github.com/texane/stlink.git
       Build the code following the instructions in the README, with:
       $ ./autogen.sh
       $ ./configure
       $ make
       As a sanity check, look in ~/st-link and you should see st-util, st-flash, etc... 
       You may check if the board could be connected by execute st-util. 
       If it does not work please confirm if the rule you added in the first step corresponds your system.


  • Try the official examples of ST on the cards
   To avoid using the commercial software IDE and understand better, We decided to develop on Linux for this project.
   During the tries, for certain examples, we've got different results on STM32F407 and STM32F401. 
   We choose STM32F407 as the hardware for the following developement.


Week 3 (27/01 - 02/02)

  • Test Project MicroPython
  • Test Project Shedskin
Retrieved from "https://air.imag.fr/index.php?title=Proj-2013-2014-Python-STM32F4&oldid=15210"