Microsoft MakeCode

A new target arrived onto the scene: KittenBot Bridge (SAM D5)

#1

A great new target arrived onto the scene: KittenBot Bridge

mQ6yPRZNcpEzJpt2dU3LfbpbVa9W4KNd968yz7xF.jpeg1920×1080

Ref: https://pixelfed.social/p/gbraad/91803319722446848

just received this last Friday and so far haven’t had a lot of time to ‘play’ with this, but I do notice that some essentials are still missing. For instance, since there the pin mapping is not known, I haven’t been able to attach a simple TFT yet to the board and try running it with Arcade (target SAM D51). All so far I have been able to do was make the LED blink and use Maker.

It does have a test target at http://maker.kittenbot.cn/ but it does not allow the use of adding extensions. They all fail … Hope more information will arrive, but so far my issues on GitHub and by email have done unanswered.

Note: you might notice there the SD-Wireless inserted to the right. This device allows to communicate with the Micro:bit, but the library https://github.com/KittenBot/pxt-sdwireless did not work for me with this board, and impossible to add to their Maker target. It does work with the Meowbit.

#2 
# detected UF2 file
# Found CFG DATA at 0x2d18
# size information incorrect; continuing anyway

PINS_PORT_SIZE = PA_32
PIN_A0 = PA02
PIN_A1 = PA05
PIN_A2 = PA06
PIN_A3 = PA04
PIN_A4 = PB08
PIN_A5 = PB09
PIN_D0 = PA23
PIN_D1 = PA22
PIN_D2 = PB17
PIN_D3 = PB16
PIN_D4 = PB13
PIN_D5 = PB14
PIN_D6 = PB15
PIN_D6 = PB12
PIN_D6 = PA02
PIN_D9 = PA20
PIN_D10 = PA18
PIN_D11 = PA19
PIN_D12 = PA17
PIN_D13 = PA23
PIN_MISO = PA14
PIN_MOSI = PA12
PIN_RX = PA23
PIN_SCK = PA13
PIN_SCL = PB03
PIN_SDA = PB02
PIN_TX = PA22
PIN_ACCELEROMETER_INT = PB01
PIN_BTN_A = PIN_D11
PIN_BTN_B = PIN_D12
PIN_BTN_DOWN = P_1241
PIN_BTN_LEFT = P_1240
PIN_BTN_MENU = PIN_D10
PIN_BTN_RIGHT = P_1140
PIN_BTN_UP = P_1141
PIN_DISPLAY_BL = PIN_D5
PIN_DISPLAY_CS = PB12
PIN_DISPLAY_DC = PIN_D3
PIN_DISPLAY_MOSI = PIN_D6
PIN_DISPLAY_RST = PIN_D2
PIN_DISPLAY_SCK = PIN_D4
PIN_LED = PA16
PIN_LIGHT = PB00
PIN_NEOPIXEL = PB22
PIN_P0 = PIN_A0
PIN_P1 = PIN_A1
PIN_P2 = PIN_TX
PIN_P3 = PIN_A3
PIN_P4 = PIN_A4
PIN_P5 = PIN_A5
PIN_P6 = PIN_D6
PIN_P7 = PB12
PIN_P8 = PIN_A0
PIN_P9 = PIN_D9
PIN_P10 = PIN_RX
PIN_P11 = PIN_D11
PIN_P12 = PIN_D12
PIN_P13 = PIN_SCK
PIN_P14 = PIN_MISO
PIN_P15 = PIN_MOSI
PIN_P16 = PIN_D10
PIN_TEMPERATURE = PB05
ACCELEROMETER_TYPE = MPU6050
BOOTLOADER_BOARD_ID = 0x239a003d
DISPLAY_CFG0 = 0x80
DISPLAY_CFG1 = 0x12c2d
DISPLAY_CFG2 = 0x18
DISPLAY_HEIGHT = 128
DISPLAY_WIDTH = 160
FLASH_BYTES = 0x80000
NUM_NEOPIXELS = 1
RAM_BYTES = 0x30000
UF2_FAMILY = ATSAMD51

Thanks @mmoskal for suggesting the CF2 patcher . Had seen it before, but now it clicks :wink:

Also got hold of part of the device configuration as used with Maker: https://github.com/gbraad/pxt-maker-kittenbot-bridge

#3

I think a mistake was made here. The Chip Select of the display is not wired to an outside pin.It references PB12, but that pin is referenced as:

PIN_D6 = PB15
PIN_D6 = PB12
PIN_D6 = PA02

which seems odd.

#4

Found the configuration on the Chinese repos: https://gitee.com/Kittenbot/uf2-samdx1/blob/kitten-bridge/boards/kittenbot-bridge/board_config.h

#5

These displays will work with cs just tied to gnd. Maybe this is what they do.

The runtime will take first occurrence of config entry but the patcher will probably take last. Need to fix that mismatch. In any event it looks like a mistake.

#6

From next month KittenBot will be selling the Arcade shield for this device. Production has already started … and here is a small teaser from what was shown at the Maker Faire ShenZhen :wink:
WeChat%20Image_20191113000605

2 Likes