c_meyer/pxt-calliope
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
MakeCode für den Calliope
1,933 Commits 21 Branches 718 Tags 275 MiB
TypeScript 63%
JavaScript 17.2%
C++ 14.3%
C# 2.2%
Objective-C 1.5%
Other 1.8%
277d5a721c
Go to file
Sam El-Husseini 277d5a721c rename "microbit" package to "core" #414 (#270) 
* rename "microbit" package to "core" #414

* shouldn't edit the package id.

* updating package.json

* updated the wrong version

* missed updating pxt.json of tests
2016-10-10 16:21:50 -07:00
.vscode added search / watch excludes 2016-08-26 09:31:06 -07:00
clients New electron client (#256) 2016-09-20 22:02:18 -07:00
cmds Reject promise when deploy to board fails (#267) 2016-10-03 15:26:41 -07:00
docfiles storing target id, version if available 2016-10-07 09:19:14 -07:00
docs updated tilt tempo video 2016-10-10 11:04:00 -07:00
libs rename "microbit" package to "core" #414 (#270) 2016-10-10 16:21:50 -07:00
olddocs/js docs cleanup 2016-09-01 06:49:39 -07:00
sim rename "microbit" package to "core" #414 (#270) 2016-10-10 16:21:50 -07:00
tests rename "microbit" package to "core" #414 (#270) 2016-10-10 16:21:50 -07:00
.gitattributes Add own manifest 2016-04-08 17:28:52 -07:00
.gitignore adjustments to electron app 2016-08-09 22:08:46 -07:00
.travis.yml Remove 3 converter tests with overflowing numbers 2016-10-04 08:20:30 -07:00
package.json rename "microbit" package to "core" #414 (#270) 2016-10-10 16:21:50 -07:00
ptrcheck-ignore update ignore file 2016-07-14 12:04:06 -07:00
pxtarget.json rename "microbit" package to "core" #414 (#270) 2016-10-10 16:21:50 -07:00
README.md removed uwp info 2016-09-02 16:08:49 -07:00
travis-tests.sh Remove 3 converter tests with overflowing numbers 2016-10-04 08:20:30 -07:00
tslint.json fixing various lint violations 2016-05-04 23:31:55 -07:00
webmanifest.json Add webmanifest files 2016-04-08 18:38:25 -07:00

README.md

micro:bit target for PXT

This target allow to program a BBC micro:bit using PXT (Microsoft Programming Experience Toolkit).

Build Status

Local server

The local server allows to run the editor and the documentation from your computer.

Setup

The following commands are a 1-time setup after synching the repo on your machine.

git clone https://github.com/microsoft/pxt-microbit
cd pxt-microbit
  • install the PXT command line (add sudo for Mac/Linux shells).
npm install -g pxt
  • install the dependencies
npm install

Running

Run this command to open a local web server (add sudo for Mac/Linux shells)

pxt serve

If the local server opens in the wrong browser, make sure to copy the URL containing the local token. Otherwise, the editor will not be able to load the projects.

If you need modify the .cpp files, turn on yotta compilation with the -yt flag (add sudo for Mac/Linux shells):

pxt serve -yt

Updates

To update your PXT version and make sure you're running the latest tools, run (add sudo for Mac/Linux shells)

pxt update

More instructions at https://github.com/Microsoft/pxt#running-a-target-from-localhost

Building

  • Install Visual Studio 2015 Update 2 or higher. Make sure the Windows 10 templates are installed.
  • open the win10/app.sln solution and launch the codethemicrobit project.

Testing

The build automatically runs the following:

  • make sure the built-in packages compile
  • pxt run in libs/lang-test* - this will run the test in command line runner; there is a number of asserts in both of these
  • pxt testdir in tests - this makes sure all the files compile and generates .hex files
  • run the TD->TS converter on a number of test scripts from microbit.co.uk and make sure the results compile

To test something on the device:

  • do a pxt deploy in libs/lang-test* - they should show 1 or 2 on the screen (and not unhappy face)
  • run pxt testdir in tests and deploy some of the hex files from tests/built

The lang-test0 source comes from the pxt-core package. It's also tested with pxt run there.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.