Describe the bug
An error in simulator Fritizing diagram when using LIGHT function in the Adafruit Trinket M0 board.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...
   https://makecode.com/_auYiA34yD9ap
   '
2. Click on '...Edit.'
3. Click on "Simulator"
4. See error

Expected behavior
You should see 3 wires in the diagram (and you do if pins other than A1/D2 are chosen) ; there should be a wire to ground, to voltage and a third wire to the pin A1/D1 and the signal pad on the light strip.

Screenshots
Add screenshots to help explain your problem. You can copy paste the screenshot in the github report. The .gif screen recording is very useful as well.

Desktop (please complete the following information):

• OS: Microsoft

• Browser [e.g. chrome, Internet Explorer and Bing)
  

• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

• https://www.adafruit.com/product/2384 [vibration sensor]
• https://www.adafruit.com/product/393 [temperature, humidity]
• https://www.adafruit.com/product/169 [micro servo]
• https://www.adafruit.com/product/189 [motion sensor]
• https://www.adafruit.com/product/375 [reed switch]
• https://www.adafruit.com/product/165 [temperature sensor]
• https://www.adafruit.com/product/159 [Diffused RGB LED]
• https://www.adafruit.com/product/1070 [short flex sensor]
• https://www.adafruit.com/product/356 [trim potentiometer]
• https://www.adafruit.com/product/805 [SPDT slide switch]
• https://www.adafruit.com/product/157 [IR sensor]

Need both simulator and device support. Some other device drivers:

https://github.com/adafruit/Adafruit_CircuitPython_Bundle/tree/master/libraries/drivers

Describe the bug
In version beta

MakeCode Maker (Cortex class) version: 0.6.4
Microsoft MakeCode version: 5.4.7

webusb only work when device reset in mode boot and download firmware. previously pair from the menu configuration

To Reproduce
Steps to reproduce the behavior:

1. Pair device
2. Download firmware with console.log include and never ends
3. Reset device with double boton click, enter in mode boot and download firmware
4. See error

My code

forever(function () {
    console.logValue("value", input.touchA0.value())
})

Desktop (please complete the following information):

• OS: MacOS
• Browser chrome
• Version 71

Additional context
tested in mrk1300 and meow meow

Hi @mmoskal

My intention is to read the information of a device via serial, but I have noticed that the "Serial" package does not have the functions Serial.available and Serial.read

Is there any intention to add them?

Thanks

I'm getting a magenta status color on the Gemma M0 when I load a .uf2 onto it. The code runs properly, just a funny color for the status light.

Describe the bug

As sson as I use a serial function such as serial.redirect(pins.TX, pins.RX, BaudRate.BaudRate115200) the arduino zero stops working.

A clear and concise description of what the bug is.

To Reproduce

let pir = false
serial.redirect(pins.TX, pins.RX, BaudRate.BaudRate115200)
loops.forever(function () {
pause(1000)
pir = !pir //pins.D7.digitalRead()
if (pir) {
pins.RXLED.digitalWrite(true)
pins.LED.digitalWrite(true)
} else {
pins.RXLED.digitalWrite(false)
pins.LED.digitalWrite(false)
}
})

The LED's are not flashing

When I comment out the serial.redirect, it works

This returns a grey block

pins.D13.digitalWrite(true)

In the JACDAC console (on arcade), log messages aren't shown in the log from devices, only control packets are.

Is your feature request related to a problem? Please describe.
It seems to me the system is missing support for ESP8266 boards. Is anyone already working on this? is it planned?

Describe the solution you'd like
I'm willing to add support by myself if someone can point out to method / issues and confirm it is feasible.

Describe alternatives you've considered
None at the moment.

Additional context
SVG part for the Wemos D1 mini:
https://github.com/mcauser/Fritzing-Part-WeMos-D1-Mini

Describe the bug
Hello

I am trying to port the MKR1300 to MakeCode, but when trying to communicate through the SPI to the Murata module I lose the serial communication

My Sketch work with

//pins.spiFrequency(250000)
//pins.spiMode(0)
// pins.spiWrite(0x42 & 0x7F) let item: number let
// buf: Buffer pins.spiTransfer(buf, buf) item =
// pins.spiWrite(0)
forever(function () {
    serial.writeNumber(pins.A0.analogRead())
    console.log("" + pins.A0.analogRead())
    serial.writeLine("")
    pins.LED.digitalWrite(false)
    pause(500)
    pins.LED.digitalWrite(true)
    pause(500)
})

but my sketch not working with

pins.spiFrequency(250000)
//pins.spiMode(0)
// pins.spiWrite(0x42 & 0x7F) let item: number let
// buf: Buffer pins.spiTransfer(buf, buf) item =
// pins.spiWrite(0)
forever(function () {
    serial.writeNumber(pins.A0.analogRead())
    console.log("" + pins.A0.analogRead())
    serial.writeLine("")
    pins.LED.digitalWrite(false)
    pause(500)
    pins.LED.digitalWrite(true)
    pause(500)
})

HF2: Connected; msgSize 256B; flash 0kB; application mode
HF2: Board-ID: SAMD21G18A-MKR1300-v0 v2.0.0-28-g535500c-dirty fSFHWRO
HF2: recv error: could not read from HID device
hid: error  Timeout
hid: error  Cannot write to HID device

Expected behavior
A clear and concise description of what you expected to happen.

Desktop (please complete the following information):

• OS: Mac
• Browser Chrome

Additional context
I am trying to read a log via SPI of the Murata module of the MKR1300

Thanks

Hi @pelikhan

I am trying to compile a version with codal mkr1300, when trying to do it, the binary is generated, but the execution of pxt serve does not end

My log
https://makecode.com/compile/497c9a0073cb7220b49cb8fb6a541bd0fd2d4956c1c3eb93d7dbbe349c70067e.log

pxt-core: 4.1.44
pxt commons 0.24.6

Thanks

When initializing the storage system, the StandardSPIFlash crashes in the SPI stack:

Breakpoint 1, _pxt_panic::target_panic (statusCode=statusCode@entry=909) at /src/pxtapp/screen---st7735/panic.cpp:256
256     /src/pxtapp/screen---st7735/panic.cpp: No such file or directory.
(gdb) bt
#0  _pxt_panic::target_panic (statusCode=statusCode@entry=909) at /src/pxtapp/screen---st7735/panic.cpp:256
#1  0x000190bc in codal::ZSPI::startTransfer (this=0x20001468, txBuffer=0x0, txSize=0, rxBuffer=0x20007efc "", rxSize=20, doneHandler=0x0, arg=0x0)
    at /src/libraries/codal-samd/src/ZSPI.cpp:324
#2  0x00018c86 in codal::ZSPI::transfer (this=0x20001468, txBuffer=0x0, txSize=0, rxBuffer=0x20007efc "", rxSize=20)
    at /src/libraries/codal-samd/src/ZSPI.cpp:302
#3  0x00013f78 in codal::StandardSPIFlash::sendCommand (this=this@entry=0x200014b4, command=command@entry=3 '\003', addr=addr@entry=0,
    resp=resp@entry=0x20007efc, respSize=respSize@entry=20) at /src/libraries/codal-core/source/drivers/StandardSPIFlash.cpp:55
#4  0x00013fd2 in codal::StandardSPIFlash::readBytes (this=0x200014b4, addr=0, buffer=0x20007efc, len=20)
    at /src/libraries/codal-core/source/drivers/StandardSPIFlash.cpp:91
#5  0x0000b4a2 in codal::snorfs::FS::readHeaders (this=this@entry=0x200014c8) at /src/pxtapp/storage/SNORFS.cpp:344
#6  0x0000b7b0 in codal::snorfs::FS::mount (this=this@entry=0x200014c8) at /src/pxtapp/storage/SNORFS.cpp:445
#7  0x0000ba36 in mount (this=0x200014c8) at /src/pxtapp/storage/SNORFS.cpp:600
#8  codal::snorfs::FS::lock (this=this@entry=0x200014c8) at /src/pxtapp/storage/SNORFS.cpp:599
#9  0x0000ba98 in codal::snorfs::FS::tryMount (this=this@entry=0x200014c8) at /src/pxtapp/storage/SNORFS.cpp:430
#10 0x0000cdc0 in WStorage (this=0x20001468) at /src/pxtapp/storage/storage.cpp:29
#11 storage::getWStorage () at /src/pxtapp/storage/storage.cpp:32
#12 0x0000cde2 in storage::init () at /src/pxtapp/storage/storage.cpp:53
#13 0x00028f68 in ?? ()
#14 0x00028f68 in ?? ()

It crashes at
https://github.com/lancaster-university/codal-samd/blame/f0a8ea10c107df7982ffae00721a702472649053/src/ZSPI.cpp#L324

which is called from
https://github.com/lancaster-university/codal-core/blame/b7b314e44543487c7c124da1c966ed690ab6aa7d/source/drivers/StandardSPIFlash.cpp#L55

• Looks like the assert needs to be updated
• afterwards, fibers are not running anymore

Describe the bug
@pelikhan - I've wired an Adafruit Metro M4 the same way the Metro M4 in the editor window is wired. Then I and added the LCD Show String block to print out "hello world". The LCD shows nothing, though it is turned on. This may be an issue where the wiring on the site is incorrect.

To Reproduce
Steps to reproduce the behavior:

1. Go to LCD
2. Click on LCD Show String "Hello World" at line 1

Expected behavior
LCD should display Hello World.

Desktop (please complete the following information):

• OS: macOS
• Browser: Chrome

Additional context
As a side-note, the LCD should be connected to the Metro's +5V instead of +3.3V (using this standard 16x2 LCD for reference; https://www.adafruit.com/product/181)

Another board: https://www.adafruit.com/product/3727

Hi @pelikhan @mmoskal

Describe the bug
I have SPI working, but in the SERCOM4 default pins, how can I change that?

the change in config.ts does not work

How do I choose the SERCOM and PADs?.

Additional context
#60

Thanks

The pin resolution for input is not working anymore.

input.pinA0.onEvent(ButtonEvent.Click, function () {
	
})

Hi

I'm trying to run my own version on a Heroku server, does anyone know the commands needed to do it or do you have an example?

Thank you

Describe the bug
Adding an external WS2812-based LEDs from the "Light" blocks seems to not fully work on other pins when using it with the SparkFun RedBoard Turbo under MakeCode Beta site. There seems to be issues controlling LEDs after 3 or 4 pixels. There also seems to be issues setting up all the LEDs to the same color. The on-board WS2812B stays lit with the color green even when not calling it.

Maybe I am setting it up incorrectly?

To Reproduce

1. Connect external WS2812s to A1, 3.3V, and GND.
2. Drag the Light > More > set strip to create WS2812 strip on LED with 30 pixels code block into the setup.
3. Change LED to A1.
4. Change 30 pixels to 5 pixels.
5. Drag Light > More > set strip brightness 20 into the setup.
6. Change brightness 20 to 150.
7. Drag the Light > More > set strip show animation for 500ms code block into forever.
8. Adjust 500 ms to 200` ms.
9. Drag the Light > More > set strip all pixels to blue code block into forever.
10. Add a few pauses between the animation and setting all LEDs to the same color.

Expected behavior
The 5x external WS2812 LEDs should animate and then all change to the color blue.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10 (64-bit)
• Browser:
• Version: 72.0.3626.109 (Official Build) (64-bit)

Describe the bug
Issue with the servo blocks. Attaching a servo on the analog pins does not seem to work when using it with the SparkFun RedBoard Turbo under the MakeCode Beta site.

I am not sure if I am doing it correctly?

To Reproduce
Servo does not seem to move when it is connected to the analog pins A0-A5.

1. Drag and set pins > servo write pin A1 to 0 in the forever loop.
2. Drag and set loops > pause 1000 ms.
3. Drag and set pins > servo write pin A1 to 180.
4. Drag and set loops > pause 1000 ms.

Expected behavior
The servo should move between two positions every second on a PWM pin. The example works when the servo is connected to the PWM pins between D3-D13 but it does not work on A0-A5. Looking at the pinout, it does not seem like the RedBoard Turbo has any PWM pins on A0-A5?

Screenshots
https://makecode.com/_FPrd0969PMDA

Desktop (please complete the following information):

• OS: Windows 10 (64-bit)
• Browser: Chrome
• Version: 72.0.3626.109 (Official Build) (64-bit)

Clicking the "blinky" tutorial from the home page gives me this error:

The Arduino Mkr also gives me this error.

Chrome Version 63.0.3239.132 (Official Build) (64-bit)
macOS

1. The breadboard blends in with the background. I think it's more clear when there's a distinction:
   
   vs.
   

2. The +/- "zoom" buttons in the bottom right only zoom the blocks. I would have expected them to at least zoom the simulator. The breadboard especially is helpful to zoom since there's a lot of detail there (whereas with the microbit simulator, the detail isn't as small.)

Describe the bug
Error when trying to download code when running Local Dev Server but not on the website.

To Reproduce
Steps to reproduce the behavior:

1. Run "pxt serve" to start local dev server
2. Click on "New Project"
3. Select any board
4. Select "Download"

It looks like it always tries to download to the device instead of downloading the hex file when running a local instance

Expected behavior
The expectation is for the file to be downloaded and a popup window to show "Download Completed"

Screenshots

Desktop (please complete the following information):

• OS: macOS Mojave Version 10.14.3
• Browser: Chrome
• Version: 73.0.3683.103

Additional context
Maybe there is a configuration that needs to be set for running locally that I am not doing? I did not have this issue running a local instance in January. I even tried checking out an earlier commit when I know it was working and I still get the same error.

Describe the bug
serial.readString() blocks after entering a character.

Example Code:

serial.setBaudRate(BaudRate.BaudRate115200)
serial.attachToConsole()

forever(function () {
pause(300)
let data = serial.readString()
console.log(data)
serial.writeString(data)
})

Describe the bug
Issue with "Music" blocks. The buzzer does not seem to be functioning on A0 when using it with the SparkFun RedBoard Turbo under MakeCode Beta site.

To Reproduce
When attaching a piezo buzzer to the DAC on A0, it does not seem to work. "Adafruit Circuit Playground Express" seems to work on pin A0.

1. Drag the Music > play sound "ba ding"code block.
2. Insert into the forever loop.

Expected behavior
The board should make a sound when the code executes the forever loop. Specifically a coin sound effect.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10 (64-bit)
• Browser: Chrome
• Version: 72.0.3626.109 (Official Build) (64-bit)

Describe the bug
the latest stable and beta web version does not work the blink, it seems the board is broken

To Reproduce
Example blink

tested on:

• SAMD21 sparkfun
• Meow Meow
• MKR1300

Desktop (please complete the following information):

• OS: MacOS Sierra and Windows 10
• Browser Chrome
• Version 70

Describe the bug
i am work with beta version and serial for GPS, serial.readUntil not work as previous version, sentence from GPS are not complete

example:

previous version the data recieved is:

$GPRMC,222313.000,A,2151.1814,N,10218.8003,W,0.00,284.07,060119,,,D*76

and the new version is

RMC,222313.000,A,2151.1814,N,10218.8003,W,0.00,284.07,060119,,,D*76

To Reproduce
Use my code

serial.setBaudRate(BaudRate.BaudRate9600)
serial.setRxBufferSize(90)
forever(function () {
    console.log(serial.readUntil(Delimiters.NewLine))
})

Screenshots

Desktop (please complete the following information):

• OS: MacOS
• Browser chrome
• Version 71

Additional context
Tested in arduino boad MKR1300

Beads

JACDAC drivers for Color bead

• Detect R G or B for bead.

JACDAC drivers for Motion bead

• Detect shake / be able to tweak shake sensitivity.

JACDAC drivers for Proximity bead

• Complete i2c TS proximity bead driver (close / near / far)
• Translate driver into TS-jacdac driver

JACDAC drivers for Light bead

• Detect visible light level for bead.

JACDAC drivers for Motor bead

• Complete i2c TS motor bead driver (continuous rotate, pan, or tilt)
• Translate driver into TS-jacdac driver

Designer Testing Scenarios

• Brain + Motion + LED strips
• Brain + Tattoo + Motor
• Brain + Tattoo + Motor + LED strips
• Brain + Tattoo + LED Strips
• Brain + Proximity + LED Strips
• Brain + Color Sensor + LED Strips
• Brain + Light Sensor + LED Strips
• Brain + Motion + Tattoo + LED Strips

Extension

• Name a bead functionality
• Generate block based on interface planning
• Program tattoo

The Arduino-Zero build breaks at this linke.

                if (bin.packedSource) {
                    if (uf2) {
==>                        pxtc.U.userError("TODO");
                    }
                    else {

Trying to use part designer with an SVG file partially made in Illustrator gives an error.

Attaching SVG file.

Breadboard.zip

Describe the bug
After clicking on the "Open assembly instructions" only the title is displayed. This is true for multiple boards and tutorials. (I was using the trinket blinky example)

To Reproduce
Steps to reproduce the behavior:

1. Open a blinky tutorial or create a new project.
2. Click on 'Open assembly instructions'
3. window pops up, only prject name is shown.

Expected behavior
I'm expecting build instructions.

Screenshots

Desktop (please complete the following information):

• OS: windows 10
• Chrome V70
• IE 11.2551

Seems to work ok for stichkit, but not the other adafruit boards

Additional context
Add any other context about the problem here.

Trying to do this doesn't work:

I can get it to work in the javascript editor using

let item = 0
loops.forever(function () {
    keyboard.type(pins.A0.analogRead().toString())
})

Describe the bug
Compilation error when trying to download project code for both the redbear-ble-nano and the adafruit-feather-bluefruit-nrf52 which are both based on the NRF52832

To Reproduce
Steps to reproduce the behavior:

1. Go to "New Project"
2. Select the redbear-ble-nano or the adafruit-feather-bluefruit-nrf52
3. Select download
4. See error

Expected behavior
Hex file to be generated and downloaded

Screenshots

Desktop (please complete the following information):

• Device: MacBook Pro
• OS: macOS Mojave 10.14.2
• Browser: Chrome
• Version: 71.0.3578.98

Describe the bug
After upload of program to Metro M0 Express, when program does not include any mention of control of on-board neopixel (green- the one that shines when re-set button is pressed prior to flashing code) then glows very brilliant green while code is running for the duration of program.

To Reproduce

https://makecode.com/_fbCPM0Hz79E5

Do not expect to see brilliant green LED pixel during entire running of the code.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]
  Microsoft Surface; Windows 10 , Chrome Browser

Also note that simulator does not alter the string as programmed when resistance is changed ; expected the string to update message as resistance increases as in code.

Use arduino uno as target

Hi

I am testing with a sparkfun dev board

I want to try an SPI sensor, but I do not see any examples

I tried with

spiPins(mosi: DigitalPin, miso: DigitalPin, sck: DigitalPin)

but it does not look like a valid command

Thanks

Describe the bug
There seems to be no internal pull-up resistor for a button press leaving any button floating as shown in the simulator. I'm not sure if we would need to include an image of a pull-up resistor in the simulator just like the LED's current limiting resistor for those that happen to use a button/switch?

To Reproduce
When attaching a momentary push button on any I/O pin, the pin is floating.

1. Drag the logic > if then code block in to the forever.
2. Drag and set button D8 is pressed into the if's condition statement.
3. Drag and set pin > digital write pin LED to HIGH as the result.
4. Drag and set pin > digital write pin LED to LOW under the else's result.

This can be fixed with a physical pull-up resistor to the 3.3V pin or setting the pin as an internal pull-up code block (i.e. set pull pin ____ to up). That might be more work than necessary since it depends on the setup. It will probably just need an example for documentation instead of having it in the simulator?

Expected behavior
Pushing a button should turn on the built-in LED on pin 13. When the button is not pressed, the LED should remain off.

Screenshots
https://makecode.com/_FiU3hK5AADCW

Desktop (please complete the following information):

• OS: Windows 10 (64-bit)
• Browser: Chrome
• Version: 72.0.3626.109 (Official Build) (64-bit)

This just redirects me to: https://makecode.com/

Hi

Describe the bug

Sometimes it does not load the page correctly and the following errors appear in the console

Screenshots

Desktop (please complete the following information):

• OS: Mac OS Sierra
• Browser Chrome
• Version 70

Additional context
In oficial page and local server

Thanks

Hi

The function serial write, read or select pin TX and TX or port 2, available?

I would like to use the serial port 2 of my board

Thanks

• connect device, start webusb HF2 download
• unplug in the middle of the download

For the log, setting the device name for the console service doesn't set the name and isn't reflected in the log as well.

Trying out the music blocks on a Gemma M0 -- works well w a speaker on A0, wonder if there could be an option to configure for PWM when using a piezo?

Describe the bug
Potential issue with UTF8 encoding through serial.

To Reproduce

Run

let i = 0;
serial.attachToConsole()
forever(function () {
    pins.LED.digitalWrite(!!(i % 2))
    console.log(`test â, ê, î, ô, û ${i++}`)
    //console.log(`test ${i++}`)
    pause(500)
})

and read the stream in terraterm. Output:

test â, ê, î, ô, û 543
test â, ê, î, ô, û 544
test â, ê, î, ô, û 545
test â, ê, î, ô, û 546
test â, ê, î, ô, û 547
test â, ê, î, ô, û 548
test â, ê, î, ô, û 549
test â, ê, î, ô, û 550
test â, ê, î, ô, û 551
test â, ê, î, ô, û 552

Is your feature request related to a problem? Please describe.

This feature request is supposed to initiate a discussion regarding adding support for Beaglebone boards in the pxt-maker target, I have been working on a separate Makecode target, starting from the pxt-maker sources to include support for the Beaglebone boards and was successful(live simulator) in implementing basic support for the Beaglebone Boards.

I would like to work on integrating my solution with the pxt-maker repository and bring in Beaglebone Boards support directly through the Makecode Maker target rather than creating a separate target for the same.

Describe the solution you'd like

I would like to have the Beaglebone Boards support delivered directly through Makecode Maker target rather than creating a separate target for the same. I am willing to work on the integration and would like to hear your valuable feedback on the same.

Describe alternatives you've considered

I have tried to create a new PXT target starting from the pxt-maker sources for providing the Beaglebone Support and was successful in implementing basic support for the same. I believe that it would be better to have the Beaglebone support served through the Makecode Maker target and would like to work on integrating the existing solution with the pxt-maker codebase.

Additional context

I have uploaded some quick test videos for the pxt-beaglebone target which you can find here :

• https://www.youtube.com/watch?v=niSkdlEI5UE
• https://www.youtube.com/watch?v=n2EkLOWMtDc
• https://www.youtube.com/watch?v=5YAto5vOWnA

Please let me know if you require any other details from me, Thank you.

A lot of duplicate going on right now.

clicking the slide switch for the first time results in confusing UI

the bottom mouse button block is how it appears on first click of the slide swtich. It straightens itself out after clicking it two more times and looks like the top mouse button block

using Chrome on windows 10