Currently there is a holding page in our support knowledge-base here:

https://support.microbit.org/solution/articles/19000044768--hex-file-format

This needs to move over to tech.microbit.org

When it moves, make the support kbase article point to the new tech.microbit.org page

This is the source of the original error:

http://www.bbc.co.uk/mediacentre/mediapacks/microbit/specs

But lots of other places on the internet have copied this and got it wrong.

cc @jaustin

Can we get the BBC to fix this 'error' as it is misleading.

microbit.org-ticket: 368

We discussed today, the view was we should probably host the live daplink firmware image on developer.mbed.org, and put some notes on tech.microbit.org listing links to all the images and what the key differences are.

https://github.com/proto-pic/micro-bit-eagle-libraries

Our Jekyll/permalink setup leads to illogical looking relative links, for example for a Markdown file in the same directory, we end up with (adjacent file)[../adjacent-file].

This works, but it makes it hard to use !Jekyll to browse the docs. GitHub is !Jekyll and should be a priority as soon as we've got the site up and stable.

(Using full URLs somewhat mitigates this, but finding a more complete solution would be better)

In dev-docs/hardware/index.md, the first URL is set to https://github.com/microbit-foundation/dev-community-site/issues

The corrected url should read https://github.com/microbit-foundation/dev-docs/issues

how to create a local version of the docs that looks like tech.microbit.org when run such that PR's have the best quality possible

url: http://tech.microbit.org/hardware/edgeconnector/

The edge connector diagram has disappeared. It was there when we first released the website back in October 2016.

The hardware index page points to ./mechanical.md, which does not exists. Not sure if it's meant to point to /hardware/edgeconnector/, /hardware/edgeconnector_ds/, or something else.

The widget that requests slack access here: http://tech.microbit.org/get-involved/where-to-find/

does not correctly set the ticket type to question. This creates double work at the receiving end, as I can't manage the ticket with a single click, it requires me to edit the properties before resolving the ticket.

Documentation is here:

https://support.freshdesk.com/support/solutions/articles/37690-getting-feedback-from-your-website-with-the-feedback-widget-

And here:

https://support.freshdesk.com/support/solutions/articles/154064-pre-populating-feedback-widget-form

(2) The column labelled dir is described as startup in the list of columns.

microbit.org-ticket: 541

microbit.org-ticket:1533

This page: http://tech.microbit.org/software/in_browser_compiler/

Has a broken link to 'MicroPython on micro:bit'

http://tech.microbit.org/software/in_browser_compiler/micropython

Code: NoSuchKey
Message: The specified key does not exist.
Key: software/in_browser_compiler/micropython
RequestId: E067E3C0ED6F249D
HostId: YRsu2qmJzHvM0eiuy/G0JLEt+Hl4ubFt6g8ilMI0IXzCdls9FhV6udTYLRjHyTPXBwDcrQVnsbw=

I have used makecode web for a long time I made many projects but now all my projects disappeared and I need to do all again.

We've had some queries from users wishing to use the micro:bit to control 4 PWM channels, e.g. for quadcopter control.

The nRF51 datasheet on table 12 states there are 3 TE units, each with 4 channels.

It would be helpful to have some additional tech information in our tech docs stating how each of the timer peripherals are allocated on the micro:bit (in fact, as a wider thing, how about a detailed breakdown of how every nRF51 on board peripheral is mapped to features?) so that it would be easier for people to answer these sorts of questions themselves.

In particular, with full knowledge of how timer TE units are allocated for each Timer, it would be much easier to assess whether going in at the mbed level (or throwing mbed away completely and coding direct to the core) would support various project development ideas.

(6) On the hardware description, the part numbers for the accelerometer and magnetometer are swapped.

microbit.org-ticket: 541

http://tech.microbit.org/bluetooth/

(4) It would help to clarify which is the front and back of the PCB.

microbit.org-ticket: 541

The 'Home' page link on the 'Request to Join Slack Channel' page does not link to home - it redirects back to the same 'Request to Join Slack Channel' page.

url: http://tech.microbit.org/hardware/edgeconnector/

The title on this page is spelt wrong

It lives here
https://pycomic.github.io/microbit.html

Blueooth Low Energy Team should be Bluetooth Low Energy Team

(7) Accelerometer is not spelled Acceleromater.

microbit.org-ticket: 541

http://tech.microbit.org/hardware/powersupply/ says "... the BBC provide some advice on the types of batteries that are approved for use with the micro:bit battery advice", but unfortunately when I follow the link, I see only information on returning faulty micro:bits.

1. simple intro/overview of the hardware specs, including power requirements and environmental conditions

2. I was not clear about power via USB and current draw. Are these limits for the onboard stuff or does it include a small(?) provision for external bits? I assume that USB volts is 5V.

3. I would like to see something about mating cycles of the edge connector and more specific recommendations regarding this and a recommended part(s).

4. What I think would/could be more useful is if the core processor with code was made available and pre-programmed chips sold perhaps with some carrier to enable it to be plugged in to a breadboard.

(1) On the Edge Connector Data sheet, there is nothing to say what the pin numbers on the PCB are, so it would help to have the reference to the pins (as is available in the here link on the more info page).

microbit.org-ticket: 541

This link no longer works: https://www.mbed.com/en/development/hardware/prototyping-production/daplink/daplink-on-kl26z/
Google cache: https://webcache.googleusercontent.com/search?q=cache:cWB53FQwfRAJ:https://www.mbed.com/en/development/hardware/prototyping-production/daplink/daplink-on-kl26z/+&cd=1&hl=en&ct=clnk&gl=uk

The link in the documentation is used here:

I was also linking to this in a list of micro:bit resources, so it'd be great if we could find an alternative or it's new location if it has been moved.

We are refering the interface microcontroller as KL26 or KL26Z, we should probably stick to one.

To be honest, I'm not sure which one is the "correct" one. DAPLink refers to the procressor as a KL26Z, but a google search for "KL26Z" gives mostly results about the FRDM-KL26Z development board. NXP refers to the family as the "Kinetis KL26" (although all parts contain the Z in the format MKL26Zxxxyyyy), so "KL26" is likely to be correct one.

There is no search on tech.microbit.org - so how do people find things if they don't know what category heading that information belongs under?

Some people may not know what Slack is, and at the moment that's our main engagement system.

We should also be clear we don't consider slack a replacement for a forum - as that's put some people off. Drawing the line that Slack is equivalent to IRC/for live collaboration and other communications means will come in time might help clear this up.

For example, in the "Get Involved" page (http://tech.microbit.org/get-involved/where-to-find/):

Javascript Blocks Editor/Makecode/pxt GitHub for issues, suggestions and hacking on pxt

That link should point to https://github.com/Microsoft/pxt-microbit instead.

We should look throughout the docs to fix any other links as well.

Typo on the 'Edge Connector' Page title; title is 'Edge Connectgtor' - http://tech.microbit.org/hardware/edgeconnector/

Where is the search button?

Can we remove the text from the get-involved page that says 'help us automate slack' - we don't need any help doing this, it's already pretty slick.

micro:bit Thursdays on the slack channel is not really happening anymore, so we should remove it from http://tech.microbit.org/get-involved/where-to-find/

https://developer.mbed.org/media/uploads/JonnyA/600xNxmicrobit_platform_image_2.png.pagespeed.ic.uXq2rT5rpA.png
returns 404

The "Schematics" page (http://tech.microbit.org/hardware/schematic/) doesn't appear to provide an actual schematic for the Microbit. If this is intentional, the page probably shouldn't be called "Schematics." Otherwise, a clearly-labeled link to a PDF of the schematic, along with a link to the source files, would be appreciated. Thank you!

(5) in the case of the pull? column, it’s not clear whether the external pullups or pulldowns are obligatory or not. Likewise, it’s not clear under what circumstances the m:b ring pins 2 and 3 are up or down - or either.

microbit.org-ticket: 541

In line with Microsoft's terminology, we should use Makecode instead of PXT

The link to this image is broken: https://developer.mbed.org/media/uploads/JonnyA/600xNxmicrobit_platform_image_2.png.pagespeed.ic.uXq2rT5rpA.png

Can be found in : http://tech.microbit.org/hardware/schematic/
https://github.com/microbit-foundation/dev-docs/blob/4bbb39bf753d61e8700ca4f3d2e1687e64626fb9/hardware/schematic.md

And: http://tech.microbit.org/hardware/edgeconnector/
https://github.com/microbit-foundation/dev-docs/blob/4bbb39bf753d61e8700ca4f3d2e1687e64626fb9/hardware/edgeconnector.md

At http://tech.microbit.org, the Foundation is referred to as the 'micro:bit Education Foundation', and not the 'micro:bit Educational foundation.

Ewan has made some nice resources here and we should link to them

https://www.proto-pic.co.uk/micro-bit-resources.html

Looks like it might be a known issue for DAPLink (still needs confirmation from mbed team): ARMmbed/DAPLink#286

Basically on Windows, after flashing DAPLink, the first target flash can throw a "File sent out of order by PC. Target might not be programmed correctly" error, but it should work the second time.

If this is confirmed it might be nice to have a note in https://github.com/microbit-foundation/dev-docs/blob/master/software/interface.md
Although it would be even better to have a note in https://www.mbed.com/en/platform/hardware/prototyping-production/daplink/daplink-on-kl26z/

https://github.com/anthonykirby/kicad_microbit_connector

On http://tech.microbit.org/hardware/ You state that you have some 3D models of the Micro:bit but don't provide links to them. They would be really handy to have available.

"We have some nice 2D and 3D CAD drawings and models of the micro:bit including all the important dimensions. These models can be used as a basis for generating really nice marketing and project images of the micro:bit, but also as a basis for accurate manufacture of attachments e.g. via 3D printing."

Please explain the problem here
http://tech.microbit.org/hardware/edgeconnector_ds/pinmap.csv is not available

https://github.com/microbit-foundation/dev-docs/blob/master/hardware/pinmap.csv

(3) Notes 1 and 4 are not consistent.

microbit.org-ticket: 541

contributed by: Kok Ho Huen

The attached .fpz file is an active fritzing part for the micro:bit - each of the GPIO pins can be wired to with Fritzing wires.

Ho developed this part in his own time, and has kindly said that we can use it on our tech site:

Microbit.fzpz.zip

https://github.com/bluetooth-mdw/microbit-blue

I have removed the co.uk editors in #68 but we probably want to update our list here, as I expect there are more out there:

https://github.com/microbit-foundation/dev-docs/blob/master/software/index.md#coding-environments-and-ides