ESP32-S3 Bench Guide
ESP32‑S3 N16R8 벤치 가이드: 실시간 핀아웃, 강의, 시뮬레이터 및 벤치 로그
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기Microsoft MakeCode (PXT - Programming eXperience Toolkit)
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Microsoft MakeCode is based on the open source project Microsoft Programming Experience Toolkit (PXT). Microsoft MakeCode is the name in the user-facing editors, PXT is used in all the GitHub sources.
PXT is a framework for creating special-purpose programming experiences for beginners, especially focused on computer science education. PXT's underlying programming language is a subset of TypeScript (leaving out JavaScript dynamic features).
The main features of PXT are:
More info:
Examples of Editors built with MakeCode:
master is the active development branch, currently v3.* buildsv* is the servicing branch for v*.* buildsPlease follow the instructions here.
If you are modifying your own instance of PXT and want a target (such as pxt-microbit) to use your local version, cd to the directory of the target (pxt-microbit, in our example, which should be a directory sibling of pxt) and perform
pxt link ../pxt
If you have multiple checkouts of pxt, you can do the following:
npm i in pxt and the targetpxt link ..\some-other-pxt (you may need to update your CLI first by running npm install -g pxt)If you run npm i afterwards (in either the target or pxt), you might need to repeat these steps.
First, install Node: minimum version 24.
To build the PXT command line tools:
npm install
npm run build
Then install the pxt command line tool (only need to do it once):
npm install -g pxt
Then install gulp (only need to do it once):
npm install -g gulp
After this you can run pxt from anywhere within the build tree.
To start the local web server, run pxt serve from within the root
of an app target (e.g. pxt-microbit). PXT will open the editor in your default web browser.
If you are developing against pxt, you can run gulp watch from within the root of the
pxt repository to watch for changes and rebuild.
gulp watch
If you are working on the CLI exclusively,
gulp watchCli
If you don't need to build the suite of associated webapps (skillmap, multiplayer, etc.), you can skip them and speed up your build a bit:
gulp --no-webapps
There are a number of custom icons (to use in addition
to http://semantic-ui.com/elements/icon.html) in the svgicons/ directory.
These need to be 1000x1000px. Best start with an existing one. To see available icons go to
http://localhost:3232/icons.html (this file, along with icons.css containing
the generated WOFF icon font, is created during build).
If you're having trouble with display of the icon you created, try:
npm install -g svgo
svgo svgicons/myicon.svg
When adding a CSS color or other style element that will be shared across editor targets (e.g. micro:bit, Arcade) and sub-applications (a.k.a. "CRAs", like skillmap, teachertool, etc.). Declare a CSS variable for it in theme/themepacks.less:
:root pseudo-class. Choose a reasonable default value according to the guidelines in the file.theme-highcontrast is defined. Choose a value that works well for the given theme.theme/themepacks.less file (e.g. pxt-microbit, pxt-arcade).Variables declared this way will be available to CRAs at runtime, and they will be initialized with the override values defined by the target in which they're running.
In the documentation, highlighting of code snippets uses highlight.js (hljs). Currently, the following languages are included:
If you need to add other languages or update existing ones,
you can find the distribution at https://highlightjs.org/download/;
select all the languages you want to include (including the ones above!),
download and unzip,
and finally copy over highlight.min.js as webapp/public/highlight.js/highlight.pack.js.
The tests are located in the tests/ subdirectory and are a combination of node and
browser tests. To execute them, run npm run test:all in the root directory.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
MICROSOFT, the Microsoft Logo, and MAKECODE are registered trademarks of Microsoft Corporation. They can only be used for the purposes described in and in accordance with Microsoft’s Trademark and Brand guidelines published at https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general.aspx. If the use is not covered in Microsoft’s published guidelines or you are not sure, please consult your legal counsel or MakeCode team ([email protected]).