Skip to main content

About the Python Environment

Python programs introduced in this blog are tested with Python 3.6. Although most of those should run with Python 2.7 with minor modification, there is not much reason to use v2.7 any more.
GUI is based on wxPython v.4 (a.k.a wxPython Phoenix).


Other frequently used packages are:

  • numpy and scpiy for mathematical data processing
  • matploltlib for data plotting
  • PIL and OpenCv for image processing
  • sounddevice, soundfile, pyserial, etc.



32bit vs. 64bit

Most of the Linux distributions include Python as a standard component, frequently both v2.7 and v3.x. And 32bit applications are quite rare these days. Thus you are not likely to have compatibility issue when installing a new package. In Windows, things are a bit more complicated. Still large percentage of programs are released in 32bit architecture. This is particularly true in engineering software. Thus it is still highly recommended to install 32bit version of Python if your have any chance to interface with those 32bit software. 

Pip(PyPI) vs. Precompiled

If available precompiled installer (or wheel) is preferred to pip . Certain packages may require special build step to fully optimize the library. Or they may have other dependencies depending on your O/S. Pip versions are not good at providing such fine tuning in general. If the package is written purely in Python, then it does not matter. In Windows, most of the prebuilt packages can be found in this site. You can instead choose to install a complete python suite such as Anaconda, Enthought Canopy, or WinPython. However they come at a cost, whether you actually pay or not. Furthermore managing packages are not as difficult as it may seem unless you have to deal with very large collection of packages. In Linux, each distribution usually provides most of the prebuilt packages, for example if your Linux supports Debian (Ubuntu) package system, you should be able to find packages like python-numpy.

wxPython

As of this writing, the most recent version of wxPython is v4.0.0b2. This pheonix version of wxPython is so much better than previous one. In Windows, you can install it with pip.  Alternatively you can install snapshot build. In Linux, you may prefer to build it from the scratch until official releases appear in major distributions.


Labels:

Comments

Post a Comment

Popular posts from this blog

A Simple STM32 Example Project

Most of the embedded projects share certain initial steps. You need to confirm the clock settings before doing anything, then you want to have debug connection via a UART channel since it is cheap  but still it can provide useful information for debugging. Let us start with CubeMX. You select a device/board of your choice, set up the pinouts for one GPIO output and one UART port. Configure the clock if necessary then create a project. Clock Checking using SysTick The sanity of the clock setting can be done by checking the SysTick interval. All Cortex-M series core have SysTick timer by default, which should fire at 1msec interval while the MCU is active. In the STM32Cube, the SysTick is initialized by HAL_Init() call, which in turn calls SysTick_Config() in CMSIS. Once the SysTick is initialized, it generates 1 msec interrupt and this interrupt is handled by SysTick_Handler() according to the Cube framework. Source file 1 /** 2 * @brief This function handles
Post a Comment
Read more

STM32 USB MSC Device with FLASH memory

USB Mass Storage Class framework implements bulk-only-transfer (BOT) with SCSI protocol. USB packets from the host eventually converted SCSI transport commands by the middleware, in which data is exchanged (read / write) in the unit of logical block, typically 512 bytes. This SCSI commands works well with SD card system where a dedicated controller does the job of managing the actual memory elements. If you want to use a FLASH chip as a memory unit instead, you need to handle read / write operation directly. Fortunately, most of flash memory support 4KB block erase. This makes the 4096 bytes as a natural choice for the size of the logical block in the file usbd_storage_if.c. In this case, 8Mbit Flash memory was used. During initial enumeration, this information is registered to the host. The middleware maintains one logical block size of buffer and handles USB transaction where each payload is only 64 bytes. It then calls SCSI requests to store / retrieve data to / from physical
Post a Comment
Read more

STM32 USB MSD with SD Card

Build a low level driver for SD card, then the glue logic for FatFs and USB MSD is pretty much the same as Flash memory case posed before. In case of SD card, sector size is 512 in most of the cases. Thus the memory requirement is much relaxed. You can even allocate a file buffer that is bigger than the sector size. FatFs site has a  dedicated page for MMC/SDC, on which you can find fairly detailed explanation about how to interface MMC/SDC via SPI bus. Implementation should be straightforward until you encounter with cheap SD cards that do not behave very well. In such cases, you either have to protect your code with redundancy or just stick with quality devices. If you choose SanDisk or Kingston brand, you will be safe. ADATA on the other hand, frequently generates timeout error at first try. Most of the SD card sockets have a pin to detect the presence of the card. This pin is usually connected to GND pin or some other pin. You can use this to generate interrupt whenever a ca
1 comment
Read more