RedBear at Kickstarter

Discussion and questions about boards that can run MicroPython but don't have a dedicated forum.
Target audience: Everyone interested in running MicroPython on other hardware.
Post Reply
User avatar
bmarkus
Posts: 111
Joined: Tue Oct 21, 2014 5:58 am

RedBear at Kickstarter

Post by bmarkus » Tue Nov 24, 2015 6:41 am

There is a RedBear project running at Kickstarter which is already founded, based on STM32F205 ARM Cortex-M3 and a Broadcom chip offering WiFi and Bluetooth connectivity:

https://www.kickstarter.com/projects/19 ... le-iot-boa

They are advertising Arduino, Java and Python without details on Python or mentioning MicroPython. Does anybody have more info?
Tiny Core Linux (piCore) developer
HAM radio call: HA5DI (Béla)

phsdv
Posts: 12
Joined: Wed Apr 22, 2015 2:36 pm

Re: RedBear at Kickstarter

Post by phsdv » Mon Nov 30, 2015 12:55 pm

It seams that they made the stretch goal and will support Python:
https://www.kickstarter.com/projects/19 ... ts/1422670
To me it is not clear if this will be microPython or not. From the comment sections:
We have just announced our 2 Stretch Goals, see Updates. If we hit the goal, we will port an opensourced Python interpreter to the Duo. We will conduct more research before we can make a decision.
https://www.kickstarter.com/projects/19 ... t-11802784

Looks like an opensource Python. Are there any other options than microPython?

User avatar
deshipu
Posts: 1354
Joined: Thu May 28, 2015 5:54 pm

Re: RedBear at Kickstarter

Post by deshipu » Mon Feb 01, 2016 9:41 am

Arduino Due is a Linux computer, so I don't think they will have much work with that -- they will just package the cPython interpreter?

User avatar
dhylands
Posts: 3268
Joined: Mon Jan 06, 2014 6:08 pm
Location: Peachland, BC, Canada
Contact:

Re: RedBear at Kickstarter

Post by dhylands » Mon Feb 01, 2016 12:54 pm

Not likely. The Arduino Due is basically equivalent to an Espruino Pico. The Due has 512K flash and 96K RAM. You won't be running linux on that anytime soon. Although I'm not sure what that has to do with the RedBear Duo, which has an STM32F205 on it (1 Mb flash and 128K RAM).

Tetraeder
Posts: 53
Joined: Thu Mar 05, 2015 1:12 pm
Location: Germany

Re: RedBear at Kickstarter

Post by Tetraeder » Thu Jun 16, 2016 6:48 am

FYI - https://github.com/redbear/Duo there is MicroPython linked in README.

User avatar
deshipu
Posts: 1354
Joined: Thu May 28, 2015 5:54 pm

Re: RedBear at Kickstarter

Post by deshipu » Thu Jun 16, 2016 8:17 am

Ah, and a "modified Microptyhon" repository: https://github.com/redbear/micropython

Looks like they forked somewhere around 1.7. I wonder if they plan to merge.

Edit: looking at the commits, they are synchronising with upstream regularly, the last merge is two weeks ago, so there is hope.

User avatar
Roberthh
Posts: 1837
Joined: Sat May 09, 2015 4:13 pm
Location: Rhineland, Europe

Re: RedBear at Kickstarter

Post by Roberthh » Thu Jun 16, 2016 6:28 pm

The code in directory duo does not build on my machine. A lot of compiling errors. No README i the directory, no other instructions.
The stuff in stmhal does build.
Update: It builds on a 32 bit virtual mint linux machine
Update 2: No reaction after flashing

User avatar
Roberthh
Posts: 1837
Joined: Sat May 09, 2015 4:13 pm
Location: Rhineland, Europe

Re: RedBear at Kickstarter

Post by Roberthh » Sat Jun 18, 2016 6:45 am

After some trying I found out, that it offers a REPL prompt at UART 1, 9600 baud. UART 1 is NOT the USB port.
It is a pretty minimal config, hardly usable, and a little bit unstable. That is the boot message:

Code: Select all

MicroPython v1.7-512-g1618bfe on 2016-06-16; RedBear Duo with STM32F205RG
Type "help()" for more information.
help() is not present, and no other supporting module. And that's what sometimes comes up, when it's performing an internal garbage collection, is something like:

Code: Select all

GC: total: 1984, used: 752, free: 1232
 No. of 1-blocks: 15, 2-blocks: 6, max blk sz: 8
That#s consistent with the heap space set to 2k in file wiring.c
It performs a soft reset on Ctrl-B, not Ctrl-D. When pressing Ctrl-D, is simply goes silent.
Summary; a fair start, but still a long way to go.

Post Reply