Hello! I have an issue with adding a new category. Looks like I do all following tutorial https://makecode.com/defining-blocks. But got error Build failed: target build failed: Exit code: 1
Please check added file
brainpad.txt

DOn't capitalize file paths

Documentation images should be under /docs/static. Please keep gifs under 5Mb and in general, avoid screenshots of code or UI.

sorry, I had to use PR request instead of master branch.

• support in CODAL for sensor
• test and validate reading ranges, axis orientation (C++ CODAL)
• test gesture recognition (C++ CODAL)
• integrate changes in pxt-brainpad
• test simulator support
• test hardware support (MakeCode)

Follow up from the call: It's important to make the bootloader interactions as simple as possible. This is what happens with Adafruit:

• when a MakeCode program is flashed, a particular flash location is set so that the bootloader knows that it is in "MakeCode" mode
• in MakeCode mode, pressing reset once flips between bootloader and user mode when connected to USB
• when not connected to USB (i.e., it fails to connect to the computer in 2 seconds or so), it flips back to user mode, which effectively turns it into a reset button
• when connecting the device to USB, it automatically goes into bootloader mode.
• the green LED glows (in case that matters).

After clicking download, the download complete window appears with the instructions on how to load the project to the BrainPad, there is another button on that window clicking on it downloads the file a second time. Do we need the download button again since it's already downloaded on the first click? Everyone that has tested so far ends up downloading the project twice.

• write CODAL sample that validates light sensor values (C++)
• integrate CODAL modification to MakeCode package
• test simulator: validate light sensor range (0..255) (MakeCode)
• test simulator: validate that light sensor events trigger (MakeCode)
• test hardware: validate light sensor range (0..255) (MakeCode)
• test hardware: validate that light sensor events trigger (MakeCode)

We need a monochromatic logo (svg) to be used for the loading dialogs. This is the waiting loading dialog that shows up when you create a new project etc...
Just attach the file here.

I somehow managed to loose my brainpad board. Please try out the screen rendering on the latest build.

let y = 0
let x = 0
forever(function () {
    x = Math.randomRange(0, screen.width - 1)
    y = Math.randomRange(0, screen.height - 1)
    screen.fillRect(x, y, 4, 4, 1)
})

lancaster-university/codal-core#26

We're getting this error when trying to add parameters to the "set light bulb to" block.

The new pixel format in images should be now exactly what you guys expect. I think you just need to do the following, but please test.

CC @pelikhan

diff --git a/source/BrainPadDisplay.cpp b/source/BrainPadDisplay.cpp
index ea28e88..c8fb835 100644
--- a/source/BrainPadDisplay.cpp
+++ b/source/BrainPadDisplay.cpp
@@ -69,14 +69,6 @@ void BrainPadDisplay::flush() {
 }

 void BrainPadDisplay::writeScreenBuffer(uint8_t* buffer) {
-    for (int x = 0; x < 128; x++) {
-        for (int y = 0; y < 64; y++) {
-            int offset = y * 16 + x / 8;
-            int mask = 0x80 >> (x & 7);
-
-            drawNativePixel(x, y, (buffer[offset] & mask) > 0);
-        }
-    }
-
+    memcpy(vram + 1, buffer, vramSize - 1);
     flush();
 }

When dragging the "set light bulb to" block into the staging area, it works fine when switching between Blocks and Javascript. After dragging "setColor()" on the JavaScript side, I get an error when trying to switch back into the Block editor.

The block code side creates this function when switching to Javascript
lightbulb.setColor(0xFF0000)

The Javascript side creates this function when dragging in.
lightbulb.setColor(Colors.Red)

Neither of these functions seem to work correctly when trying to use them inline in Markdown examples.

We typically do not link to HTTP pages. Could you add a certificate to https://www.brainpad.com/.

A set of images to be painted on the screen. 16 minimum.

• create images
• add block in MakeCode

Tested components on simulator:

• accelerometer
• temperature sensor
• light sensor
• buttons
• display
• servo motors
• light bulb
• Buzzer

Tested components on physical BrainPad:

• accelerometer
• temperature sensor
• light sensor
• buttons
• display
• servo motors
• light bulb
• Buzzer

When running this code, it doesn't work in the Simulator, but does work when deployed to the BrainPad.

forever(function () {
    if (input.buttonU.isPressed()) {
        lightbulb.setColor(0xff0000)
    } else {
        lightbulb.setColor(0x00ff00)
    }
})
``

Has the I2C issue been resolved concerning the screen? I would like to work on a Display tutorial, but we would also like to get the BrainPad to a known state? Our engineers don't want to flood the site with issues from our end with things that are only temporarily down or changing.

There are several places where users can enter parameters. Such as the "set brightness" block, and the "Colors: red, green, and blue parameter" block. Are the we going to be using the values of '0 - 255' or '0 - 100%' going forward?

We ask this question for two reasons, we want to get our supplemental documentation correct, and we've come across this issue several times in the past. We've had this issue when trying to explain to students, that are new to programming, what these values actually mean. In particular when we refer to things like 'set brightness'. They always assume 0 - 100%. We've found 255 means nothing to new programmers and often can be confusing to them.

You should really try to avoid any kind of block screenshot as they are not localiable and tend to grow stale.
This commit added a bunch of them.
090df8c

The gif images are too large. You should try to crop and shrink the gifs to the absolute minimum and under 1Mb. Also, all documentations assets should go under /docs/static/... , nothing should go under /sim.

We need the hero image for the editor. It goes here:

You can just attach it to this issue. We'll take it from here.

and use versioned build instead of pointing to master.

We've updated our the our codal-brainpad and bumped the version to v0.0.9. It now contains the updated dispaly to support PXT bitmap formatting

https://github.com/ghi-electronics/codal-brainpad/releases

We've updated our the our codal-brainpad and bumped the version to v0.0.8. It now contains the driver for the display.

https://github.com/ghi-electronics/codal-brainpad/releases

We've got the latest code up at https://github.com/ghi-electronics/codal-brainpad/releases/tag/v0.0.11

Adds what should be properly scaled light, temperature, and accelerometer along with light and temperature being abstracted into their own classes.

It seems that the screen is not clearer when reseting the device. Is this something the bootloader can do?

Predefined images added to the on start block don't show in the simulator, even when adding a pause. If I also add an image to the forever loop, then I briefly see the first image in the on start block. Show string block also only visible in the forever block.

• turn LED to green when bootloader mode
• press reset once goes to bootloader mode when connected to computer
• go to bootloader mode automatically when connected to computer
• auto-restart once flashing is done.

A curriculum for teacher to use the brainpad in the classroom. Does not need to be finished but roadmap needed.

We need a cute avatar svg that will be used in the tutorial bubble. .If you try the Adafruit step by step tutorials, you can see the avatar in the instructions.

Building failing due to assembly error

Build:
https://ci2.dot.net/job/Private/job/pxt_project_blue/job/master/job/pxt-brainpad_Push/6/console

Error:
12:35:10 main.ts(1,1): error TS9200: -> Line 65 (' bl pxtrt::getGlobalsPtr’), error: assembly error
12:35:10 Maybe: bl LABEL (jump out of range at ‘pxtrt::getGlobalsPtr’)
12:35:10 Maybe: bls LABEL (opcode name doesn’t match at ‘’)

getGlobalsPtr is implemented in pxt-common-packages/base, and base is inherited in full in pxt-brainpad

Here is the a newest version of the BrainPad.svg. This is the our newest BrainPad, with the larger boot-loader button and our newest surface mounted display. (New display works exactly the same as older version)

BrainPadSVG.zip

Clone repo, npm install, pxt serve.

Uncaught TypeError: Cannot read property 'pxtCrowdinBranch' of undefined
    at http://localhost:3232/blb/main.js:2215:123
    at <anonymous>
From previous event:
    at HTMLDocument.<anonymous> (http://localhost:3232/blb/main.

Here are 3 images for the download section. Also the verbage should read something similar to this.

1. Take the USB cable you connected to your computer. Plug it into your BrainPad.

2. Press and HOLD the RESET button until the LIGHTBULB turns GREEN. This will open a new folder.

3. Click and drag the file you downloaded into the newly opened BrainPad folder.

• CODAL driver for screen. Needed an API that takes bitmap buffer.
• C++ sample and test
• wrap bitmap buffer in MakeCode API
• simulator support
• test hardware support from MakeCode with predefined images.

@pelikhan Are we going to need to create something similar to this in SVG for the servos? Or is there something already built in? If we are making, do we make it as a stand alone image (servos alone) or do we attach it to the BrainPad SVG as one image. All parts ID properly of course.

I'm trying the latest board that came up via Fedex this morning (Thanks!)

• no drive showing up when I connect and/or press reset button. Tested on Windows 10.
• screen display garbage image

• refactor temperature singleton to support custom
• Add support for temperature sensor in codal-brainpad
• calibrate and test sensor in CODAL C++ sample
• integrate modifications in pxt-braindpad
• test simulator support (MakeCode)
• test hardware support from MakeCode

Now buttons don't work. I try to figure it out and understand the structure of environment in whole.

1. Have I change something in pxt-common-packages\libs\core\pins.h? (It looks like, \pxt-brainpad\libs\core\dal.d.ts generated from pins.h) It is incorrect defined buttons.
2. In pxt-brainpad\libs\brainpad\device.d.ts correct pin definition. I guess it is an autogenerated file. Where is it from?

Add 4 more predefined images to complete the show image block.

A set of step-by-step tutorials that enumerate each sensor. For each tutorial, a markdown page + image for the gallery

• light sensor
• temperature sensor
• accelerometer
• servo
• screen

We need the pxtarget.json file changed to reflect our version of the codal-brainpad repo at GHI.

url:
https://github.com/ghi-electronics/codal-brainpad

branch:
v0.0.7

When using this code snippet, I see the default image in my tutorial, and not the image in the code, should be 'walker1'

After deploying firmware light and temperature sensors don't' respond. At the same time when I use Pins function "analog read pin" I get properly values. In config.ts PIN_LIGHT = DAL.PB_1; - is correct. In lightsensore.cpp function sensor(*LOOKUP_PIN(LIGHT), DEVICE_ID_LIGHT_SENSOR) use correct definition? Or the problem in another place? What is the best way fix it up?

The default value when dragging in the music.playTone block is showing part of the function.

There appears to be two calls to music.beat() when I look at the Javascript.

forever(function () {
music.playTone(262, music.beat(music.beat(BeatFraction.Half)))
})

https://makecode.com/_9rLUsTA5WRDF