From mithro at mithis.com Mon Apr 3 13:25:55 2017 From: mithro at mithis.com (Tim Ansell) Date: Mon, 3 Apr 2017 13:25:55 +1000 Subject: [Chat] Instructions for loading bootloader onto bare Tomu boards Message-ID: Forwarded from the tomu-discuss list Hello everyone, It appears that I had forgotten to forward the promised instructions for getting a bootloader onto a bare Tomu board, so here they finally are. Better late then never! This process is needed if you got an unflashed Tomu board at LCA2017 or 33C3, or if building your own board. Anyone who got their Tomu boards from me *after* LCA2017 should find their board already has the bootloader on them but these instructions are useful if you accidently overwrite the bootloader and the board stops responding. Instructions for flashing the bootloader onto your Tomu board using OpenOCD and a RPi can be found at https://github.com/im-tomu/ tomu-bootloader/tree/master/openocd -- I would love instructions for loading the bootloader using other devices but haven't had any time to write them. The new Tomu bootloader has the following differences to the bootloader which ships on the EFM32HG; * Allow using the USB port for firmware loading without needed an external oscillator (which doesn't exist on the Tomu board). * Always enter the bootloader. It does *not* require a pull up on the 'C' pin. * This bootloader will identify itself as BOOTLOADER version EFM32HG bootloader v1.a, Chip ID 24A622015669A7A1 The important parts are version EFM32**HG** bootloader v1.**a** The bootloader repo is found at https://github.com/im-tomu/tomu-bootloader Once flashed with new USB bootloader and blinky example the Tomu should appear as a CDC-ACM serial port out of the box. Connect with a serial program (minicom, cu, screen) and hit 'i' to get the identity info and 'b' to start the blinky example, 'u' will allow uploading new user firmware. *Don't* press 'd' otherwise you'll need to use JTAG to recover the device (that is destructive upload that clears the bootloader). A big thankyou to Aleksa Sarai (cyphar) who wrote the flashing instructions and Jonas Jelten (TheJJ) who created the patched bootloader. Looking forward to seeing all the cool things people do with the Tomu board! Tim 'mithro' Ansell -------------- next part -------------- An HTML attachment was scrubbed... URL: From marc at merlins.org Mon Apr 17 09:57:22 2017 From: marc at merlins.org (Marc MERLIN) Date: Sun, 16 Apr 2017 16:57:22 -0700 Subject: [Chat] Open Hardware Miniconf - IoTuz progress In-Reply-To: <93924f25-c3a3-fae1-eeea-525f5aa98183@espressif.com> References: <93924f25-c3a3-fae1-eeea-525f5aa98183@espressif.com> Message-ID: <20170416235722.lq5uequvlhn2q2e4@merlins.org> On Fri, Jan 20, 2017 at 01:28:41PM +1100, Angus Gratton via Chat wrote: > Hi, > > For anyone who joined in for Open Hardware Miniconf assembly project on > Tuesday, there are some updates: > > - The crashes that some people were seeing on the day are now solved (thx > Jan!), if you "git pull" the firmware and re-compile, things should be OK. > > - Some additional hardware support (colourful LEDs!) has also been added to > the IoTuz firmware. > > - Some people have Micropython up and running, which is awesome.. > > - The "test" Arduino sketches in the IoTuz hardware repository have some > additions. Marc Merlin a bunch of new things working in Arduino, including > the touchscreen. Eh, so it's only been 3 months. Either because I'm slow, or because it was about 100H of work :) Either way, for all of you with IoTuz boards maybe gathering dust. Please bring them out and do something cool with them. The software available during the miniconf was "minimal". I was a miniconf attendee just like you, but I took that as a challenge because I'm not very smart :) Anyway, now you don't have that excuse anymore, here is a bunch of code: https://github.com/marcmerlin/IoTuz Miniconf report and IoTuz Dmeo: http://marc.merlins.org/perso/arduino/post_2017-01-16_IoTuz-Driver-for-our-ESP32-board-built-at-Open-Hardware-Miniconf-at-Linux_Conf_au-2017.html Or a 2mn demo video: https://www.youtube.com/watch?v=Kvcvpdip12A There are still things to be done if you want excitement: 1) IR sending 2) audio recording and playing 3) bluetooth and wifi control of the board 4) whatever else you can come up with, surprise us :) Cheers, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 1024R/763BE901