TiLDA MK4/Run Code: Difference between revisions
		
		
		
		
		
		Jump to navigation
		Jump to search
		
				
		
		
	
No edit summary  | 
				No edit summary  | 
				||
| Line 3: | Line 3: | ||
* Todo: Please write how to do that on different operating systems  | * Todo: Please write how to do that on different operating systems  | ||
* todo: how to use a REPL  | * todo: how to use a REPL  | ||
'''Important''': once connected to the serial port, you'll only see output the badge sends (usually none). Hit Ctrl+C to exit from the current process and get back the REPL.  | |||
=== Windows/WSL ===  | === Windows/WSL ===  | ||
| Line 20: | Line 22: | ||
  sudo screen /dev/ttyS{n}  |   sudo screen /dev/ttyS{n}  | ||
where {n} is the numeric part of the COM port (e.g. /dev/ttyS4 for COM4).  | where {n} is the numeric part of the COM port (e.g. /dev/ttyS4 for COM4). Use Ctrl+A, D to disconnect.  | ||
== Use the "mass storage" app ==  | == Use the "mass storage" app ==  | ||
Revision as of 21:51, 18 September 2018
Through the REPL
- Todo: Please write how to do that on different operating systems
 - todo: how to use a REPL
 
Important: once connected to the serial port, you'll only see output the badge sends (usually none). Hit Ctrl+C to exit from the current process and get back the REPL.
Windows/WSL
Firstly, identify the serial device (should be a COM port that only shows when you plug the badge in):
- Open Computer Management (compmgmt.msc)
 - Navigate to Device Manager
 - Expand Ports (COM & LPT)
 
Alternatively in PowerShell:
Get-WMIObject Win32_SerialPort | Select-Object DeviceID,Description
Then open PuTTY, enter the COM port found above, select Serial, and click Open.
Alternatively in WSL:
sudo screen /dev/ttyS{n}
where {n} is the numeric part of the COM port (e.g. /dev/ttyS4 for COM4). Use Ctrl+A, D to disconnect.
Use the "mass storage" app
- Only works on OSX at present (2nd Sept 2018)
 - easy to do
 - make sure to safely eject every time
 - has a tendency to corrupt the filesystem - link to reset instructions
 - hard to debug errors
 - todo: add more information
 
Use Mk4-Apps tilda_tools
- Probably most convenient, but a bit more involved:
 - You can use "./tilda_tools run <file.py>" to run code without copying anything, but if you want to make sure you have all your libraries updated use "./tilda_tools app my_app" instead.
 - https://badge.emfcamp.org/wiki/TiLDA_MK4/tilda-tools