opened
naums
username_0
This is a (clean) Raspberry Pi-port. There is no REPL at the moment, just executed hardcoded strings using the `do_str`-routine. For testing purposes the code can also be built and ran on QEMU, set the `BOARD` variable in the Makefile to "qemu".
Raspberry Pi Port - the second
issue
created
Neon22
username_1
How would you characterise the nature of the difference between this and the unix build ?
comment
created
stinos
username_2
^ that's a good question indeed, last time I tested it (a while ago though) uPy built straight out of the box on a Raspberry Pi. Is this like unix port + (not yet implemented) support for uart/jtag? That could just be built as modules?

Btw you have some dead code in the files, that is one roadblock to getting it merged.
comment
created
WayneKeenan
username_3
It's targeting his custom [bare-metal/embedded OS](https://github.com/username_0/PiOS) not a unix/posix environment.
comment
created
naums
username_0
This is a bare-metal port for the Raspberry Pi (and QEMU versatilepb for that matter). Run make, then you'll have a kernel.img you can copy over to a Raspberry Pi-SD-card and boot the Raspberry Pi from it. This has nothing to do with the Unix-port, and does not need any operating system running on the Raspberry Pi to run. 

The dead code @username_2 is referring to is probably PiOS, right? This is another project of mine, @username_3 already pointed out. I'm using this collection of "drivers" in the Micropython port for UART on both QEMU and Raspberry Pi and JTAG-support. If you don't like the dependency to the external project - I can copy the necessary files into the port itself. That includes gpio.c, both uart.c's, jtag.c + header-files, and everything from the boards-directory. 

PS: the word embedded OS for PiOS is a bit to much. It's rather a selection of drivers with bare-minimum boot-code (at the moment).
comment
created
stinos
username_2
no, the commented out code lines in this commit which don't serve as documentation. Just to name one: main.c line 126 has `//blinkloop();` which is obvioulsy a leftover from playing around
comment
created
naums
username_0
done.
comment