Page 1 of 3
MicroPython on i.MX6
Posted: Wed Nov 18, 2015 2:36 pm
by Tetraeder
Hi,
after many attempts I’ve managed to port minimal to i.MX6 quadcore
.
I get a repl via UART.
I report the next day about the progress.
Re: MicroPython on i.MX6
Posted: Wed Nov 18, 2015 3:57 pm
by pfalcon
Do you mean you run it bare-metal, without Linux? If so, that's indeed pretty cool, details wanted.
Re: MicroPython on i.MX6
Posted: Thu Nov 19, 2015 11:01 am
by Tetraeder
Yes as bare-metal. On a Freescale Sabre board.
My tests so far: variable declarations and small calculations(10*5).
Something is not right with UART: it will not appear to me that I typed in but after I hit enter, it is displayed.
Re: MicroPython on i.MX6
Posted: Thu Nov 19, 2015 12:17 pm
by pfalcon
Cute. If you'd select more wide-spread target, like Raspberry Pi, or just bare-metal x86, you might even catch some people testing or even contributing to it. Otherwise, well, keep us posted
.
Re: MicroPython on i.MX6
Posted: Thu Nov 19, 2015 1:34 pm
by torwag
Hmmm,
that means we can run micropython on the upcoming new generation of e-ink devices which will base on the i.MX7.
Wait until those units are cheap enough and we will have an display unit in form of an programmable e-ink display to show calendars, sensor data, weather or other IoT stuff.
Re: MicroPython on i.MX6
Posted: Mon Nov 23, 2015 3:51 pm
by Tetraeder
My UART problems are solved.
It works fine, now.
pfalcon wrote:Cute. If you'd select more wide-spread target, like Raspberry Pi, or just bare-metal x86, you might even catch some people testing or even contributing to it. Otherwise, well, keep us posted
.
I have one raspberry that would be the next target after i.MX6. If by then no one else has it already been ported.
Now I try to display the repl prompt over the HDMI or LVDS connector. And the support for a keyboard.
furthermore at this point the MicroPython-lib is not complete there also needs some more time.
Re: MicroPython on i.MX6
Posted: Thu Jan 21, 2016 10:32 am
by Tetraeder
Small update,
currently able to run:
* communication over UART (debug interface)
* Set Pin and toggle output state
* Display (only pictures no video content)
* Temperature monitor
Next,
* USB
Re: MicroPython on i.MX6
Posted: Thu Mar 03, 2016 12:19 am
by hosk
Do you have some news about porting?
Are you planning publish code?
Honza
Re: MicroPython on i.MX6
Posted: Thu Mar 03, 2016 6:23 am
by Tetraeder
Hi Honza,
not found much time to work on.
Currently working on CDC (USB).
I would publish the code but I do not know if I could publish the code of NXP (Freescale) on Github? Because I use the driver package from NXP.
Re: MicroPython on i.MX6
Posted: Mon Apr 25, 2016 2:14 pm
by Tetraeder
Hi,
the USB CDC support is done.
Next will be MSD.
I have found the the LICENSE of the NXP/Freescale SDK, which I use. Can anyone tell me if I can publish uPy port with the NXP/Freescale code? Only what I have to do is to check the disclaimer in each file, right?
Following the LICENSE:
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
o Redistributions of source code must retain the above copyright notice, this list
of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.
o Neither the name of Freescale Semiconductor, Inc. nor the names of its
contributors may be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.