nblocksWiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
<WRAP classes width :language>

</WRAP>

======nBlocksStudio1.0 Installation======

**nBlocksStudio1.0** is using mbed-cli infrastructure including GCC compiler, for the microprocessor code compilation.\\
The Graphical interface is written in Python and is accessing the n-Blocks.net server when it starts, to get the definition of the Nodes\\
 

\\
\\

====Install Python====
Both mbed-cli and nBlocksStudio are based on Python.

  * Download 32 bit windows installer for Python 2.7 (dont use 64bit Python installer, issues with pip)
  * **Configure installer for adding Python path to system path** and complete Python 2.7 installation
  * Restart Windows (otherwise pip fails)
  * Test Python  and pip from command line: <code>Python --version 
pip --version 
</code>
Both should work from any directory\\  
If pip version is later than 9.0.3 mbed-cli might not work (( [[https://github.com/ARMmbed/mbed-os/issues/6763]] )), so change to 9.0.3: <code> pip install -U pip==9.0.3 </code>


\\
\\
\\
====Install mbed-cli manually====
References: 
(( [[https://www.youtube.com/watch?v=PI1Kq9RSN_Y 3 minutes quickstart |mbed 3 minutes quickstart video]] ))
(( [[https://docs.mbed.com/docs/mbed-os-handbook/en/5.1/dev_tools/cli/ |mbed os handbook]]))
(( [[https://www.youtube.com/watch?v=cM0dFoTuU14 Learn to use Mbed CLI: |mbed-cli: How to install manually]]))
  * Install Git:
    * Download Git (([[https://git-scm.com/downloads |download GIT]]))
    * Run the .exe (for windows) to install it
  * Install Mercurial:
    * Download Mercurial (([[https://www.mercurial-scm.org/wiki/Download |download Mercurial]]))
    * Run the .exe (for windows) to install it
  * Install GCC:
    * Download GCC (([[https://developer.arm.com/open-source/gnu-toolchain/gnu-rm |download GCC from developer.arm.com]]))
    * Run installer
    * **Add Path to environment variable** and complete installation
  * Verify Installations: <code>arm-none-eabi-gcc --version
git --version
hg --version
python --version
pip --version
</code>

  * Install mbed cli from command prompt: <code> pip install mbed-cli </code> 
  * Verify mbed installation: <code> mbed --version </code>
  * 07-March-2020, install Microsoft Visual C++ Compiler for Python 2.7:  (([[ http://aka.ms/vcpython27]]))
\\
\\

====mbed tips====


===mbed online compiler how to use OS2 or OS5===
References: (([[https://os.mbed.com/questions/77437/MBED-OS-2-MBED-OS-5/ |configure mbed-online for MBED-OS-2 or MBED-OS-5]])) <code> To make sure you are using the desired library delete the mbed library from your project in the online compiler and then 
  import either the mbed-dev (if you would like to use mbed OS 2) or the mbed-os (if you prefer mbed OS 5). </code>

  

===How to import an existing program from mbed online compiler to mbed-cli and compile it===
  *From online compiler right click on the project and publish (or FORK) in to something like this: [[https://developer.mbed.org/users/chalikias/code/frequency_counter/ |frequency_counter]]
    * If the project is copy from somebody else's project, probably have to fork to your own mbed space
  * With administrative rights(???): <code> mbed import https://developer.mbed.org/users/chalikias/code/frequency_counter/ </code> 
  * for a list of supported targets: <code> mbed compile -S </code>
  * Finnaly: <code> mbed compile -m LPC1768 -t GCC_ARM </code>

===How to create new mbed-cli project for OS2 or OS5=== 
References: (([[https://github.com/ARMmbed/mbed-cli#creating-and-importing-programs|mbed-cli: creating and importing programs]] ))
  *new OS5 project:<code> mbed new project1 </code> 
  *new OS2 project:<code> mbed new project2 --mbedlib </code>
  *new OS5 project at current directory:<code> mbed new . </code>


===Alternative method to import OS2 program from mbed online compiler=== 
I had issues with the import method described above. This Alternative method works.Tested for Target LPC11U35_401 [20 May 2020] 
  * From mbed online compiler right-click on a **Program** in the **Program Workspace**: Export Program using <code> Export</code> Toolchain <code>ZIP archive (with repositories)</code>
  * Extract the ZIP file to a Temporary folder.
  * Create a new folder as new mbed OS2 project. This folder will be the project working folder: <code> mbed new project_name --mbedlib </code>
  * **From Inside** the Temporary folder copy all files and folders.
  * Paste the copied files and folders, to **project_name** folder created from  **mbed new project_name --mbedlib**
      * Just overwrite existing files when Windows asks
  * From Command line Compile: <code>mbed compile -t GCC_ARM -m LPC11U35_401</code>



===Update mbed OS to a specific version=== 
  * go to mbed-os directory inside the project forlder <code> cd mbed-os </code>
  * Check the active release: <code> mbed releases </code>
  * update to the desired release, for example: mbed-os-5.7.7 <code> update mbed-os-5.7.7 </code>
  * Check again for the active release: <code> mbed releases </code> 
\\
\\
\\






   
\\
\\
\\

====Install n-Blocks Studio====
  * Install all needed Python modules: <code>pip install panda3d
pip install pywin32
pip install pyuserinput
</code>

  * Download the studio from [[https://nimbus_it@bitbucket.org/nblocksstudio/prj_nblocksstudio |bitbucket]], using command line: <code> hg clone https://nimbus_it@bitbucket.org/nblocksstudio/prj_nblocksstudio</code> 
  * Or update an existing nBlocksStudio directory using command line, but from inside the directory <code> hg update </code> 
  * Copy **mbed_code** outside the version controlled directory, so it will not be affected by future updates of the studio
  * Go to  **the new mbed_code** folder with command line
  * Create new mbed **OS2** project inside the new folder: (preferable for now, OS5 is not tested well yet with nStudio) <code> ...\mbed_code> mbed new . --mbedlib </code>
  * Or  a  new mbed **OS5** project inside the new folder: <code> ...\mbed_code> mbed new .   </code> 
 
  * Add any missing libraries: <code> ...\mbed_code> mbed deploy </code>
\\
\\
\\


====Use n-Blocks Studio====
  * Login to your nBlocksStudio (([[https://www.n-blocks.net/studio|nBlocksStudio page]])) account and add **nodes** to your account {{:nblocks:nblocksstudio-03.jpg?1000|}}
\\
  * Start nBlocksStudio, from **Studio** folder with command line:

  ....\Studio\Launch.cmd


  * On 07.02.2019 I had to edit nworkbench.py, to change[t]kinter to [T]kinter\\ 
  * On 05.03.2020 this does not seem to be needed any more...\\ 
 <code> from tkinter import TclError</code> to <code>from Tkinter import TclError </code>
  * ...and to install missing python modules:\\ 
 <code> pip install enum </code> 
 <code> pip install pywinusb</code> 
  * ...one more March 2020:\\ 
 <code> pip install requests</code>  
 
When exporting, save into the file **main.cpp** inside folder **mbed_code**, and build with:

  C:....\mbed_code> mbed compile -t GCC_ARM -m LPC1768
Above creates a [.bin] file. (at ...\mbed_code\BUILD\LPC1768\GCC_ARM)\\
To automate the build process and use a different target n-Block/processor, call one of the **[tested]** batch files
  * LPC1768.cmd (n-Bed)
  * LPC11u35.cmd (n-DAP)
  * L432KC.cmd   (n-LP)
  * L152RE.cmd   (n-L15, n-CPU48)
\\
\\
\\


====4 bit binary counter example with n-Blocks Studio====
{{:nblocks:nblocksstudio-02.jpg?1000|}}\\
 This example diagram (a 4 bit binary counter) creates the main.cpp below:

<code c++>
/* ================================================================ *
 *       Automatically generated by n-Blocks Studio Designer        *
 *                                                                  *
 *                         www.n-blocks.net                         *
 * ================================================================ */
#include "nblocks.h"


// -*-*- List of node objects -*-*-
nBlock_Ticker                 nb_nBlockNode0_Ticker;
nBlock_FlipFlop               nb_nBlockNode13_FlipFlop;
nBlock_FlipFlop               nb_nBlockNode3_FlipFlop;
nBlock_GPO                    nb_nBlockNode12_GPO;
nBlock_FlipFlop               nb_nBlockNode14_FlipFlop;
nBlock_FlipFlop               nb_nBlockNode15_FlipFlop;

// -*-*- List of connection objects -*-*-
nBlockConnection         n_conn0(&nb_nBlockNode0_Ticker, 0, &nb_nBlockNode3_FlipFlop, 0);
nBlockConnection         n_conn1(&nb_nBlockNode3_FlipFlop, 0, &nb_nBlockNode12_GPO, 0);
nBlockConnection         n_conn2(&nb_nBlockNode3_FlipFlop, 0, &nb_nBlockNode13_FlipFlop, 0);
nBlockConnection         n_conn3(&nb_nBlockNode13_FlipFlop, 0, &nb_nBlockNode12_GPO, 1);
nBlockConnection         n_conn4(&nb_nBlockNode13_FlipFlop, 0, &nb_nBlockNode14_FlipFlop, 0);
nBlockConnection         n_conn5(&nb_nBlockNode14_FlipFlop, 0, &nb_nBlockNode12_GPO, 2);
nBlockConnection         n_conn6(&nb_nBlockNode14_FlipFlop, 0, &nb_nBlockNode15_FlipFlop, 0);
nBlockConnection         n_conn7(&nb_nBlockNode15_FlipFlop, 0, &nb_nBlockNode12_GPO, 3);


// -*-*- Main function -*-*-
int main(void) {
    SetupWorkbench();
    while(1) {
        // Your custom code here!
    }
}
</code>
\\
\\
\\

====References====
nblocksWiki

User Tools

Site Tools

Page Tools
