[Microbit-Python] Repl not echoing back

Wed Dec 30 17:34:52 EST 2015

Hi Naomi,

even though this all sounds very much like a hardware
problem, you might want to try reflashing the DAPLink
firmware which implements the serial console USB connections:

https://www.mbed.com/en/development/hardware/prototyping-production/daplink/daplink-on-kl26z/

Cheers,
-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts (#1, Dec 30 2015)
>>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
>>> Python Database Interfaces ...           http://products.egenix.com/
>>> Plone/Zope Database Interfaces ...           http://zope.egenix.com/
________________________________________________________________________

::: We implement business ideas - efficiently in both time and costs :::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/
                      http://www.malemburg.com/

On 14.12.2015 00:42, Naomi Ceder wrote:
> Yep, those suggestions make sense. I particularly like the Michelle idea.
> :-)
> 
> Since Mary is functioning in all other respects I'll keep her here for
> hacking until the others safely arrive.
> 
> Cheers,
> Naomi
> 
> On 13 December 2015 at 03:23, Nicholas H.Tollervey <ntoll at ntoll.org> wrote:
> 
>> Folks,
>>
>> Poor old Mary micro:bit... my (wife) Mary is going to be heartbroken
>> that her namesake has a bad case of the collywobbles.
>>
>> Here's what I suggest:
>>
>> * We "retire" Mary - can you post her back to me and I'll make sure it
>> gets to Jonny at ARM who'll be interested in such hardware failures?
>>
>> * We "promote" one of the new boards heading in your direction to the
>> world tour. Given this is a US based series of events I propose we name
>> the new micro:bit in honour of the FLOTUS: "Michelle micro:bit". :-P
>>
>> * Naomi, can you write up how Mary got "sick" and ping me a PR for the
>> website? I'll add a note to explain the appearance of Michelle and then
>> we can let the tour continue.
>>
>> Sound like a plan?
>>
>> N.
>>
>> On 13/12/15 01:33, Naomi Ceder wrote:
>>> Hi Carol,
>>>
>>> I just tried picocom with exactly the same results - I'm still on
>>> yosemite, but getting the same behaviour on 5 terminal programs and two
>>> different OS's I'm going to say the issue is the device at this point.
>>>
>>> Cheers,
>>> Naomi
>>>
>>>
>>> On 12 December 2015 at 17:27, Carol Willing
>>> <willingc at willingconsulting.com <mailto:willingc at willingconsulting.com>>
>>> wrote:
>>>
>>>     Hi Naomi,
>>>
>>>     Perhaps a shot in the dark, did you try picocom?  picocom
>>>     /dev/ttyACM0 -b 115200  Replacing with the correct port. I've used
>>>     with the Mac Pro. I'm still running Yosemite. Are you on El Capitan?
>>>
>>>     You could try getting rid of any cruft of old USB /dev/tty files.
>>>
>>>
>>>     Damien, Does the microbit have a hard reset by pulling a GPIO pin
>> low?
>>>
>>>
>>>>     Naomi Ceder <mailto:naomi.ceder at gmail.com>
>>>>     December 11, 2015 at 7:37 PM
>>>>     Hi everyone,
>>>>
>>>>     I'm having a very weird issue with Mary the micro:bit.
>>>>
>>>>     It had been working fine... until I was about to demo before the
>>>>     Chicago Python group (ChiPy) last night.
>>>>
>>>>     Then suddenly the repl wouldn't work. That is, I could apparently
>>>>     connect, I could type commands in, the LED on the microbit would
>>>>     flash as normal, but nothing was echoed back. I could put scripts
>>>>     on the flash and the would run normally, but after trying 3
>>>>     different terminal programs (all of which had worked before),
>>>>     still no joy.
>>>>
>>>>     Tonight I've been experimenting more and I can confirm that the
>>>>     commands I'm entering do get to the microbit and are executed as
>>>>     normal. Even arrowing up and tab completion are working normally,
>>>>     but nothing gets sent back to my screen.
>>>>
>>>>     I've mainly kept the comm settings at what worked well before
>>>>     115200, N-8-1 and I might add that I've used 2 or 3 different
>>>>     versions of the firmware with the same reaction, two different USB
>>>>     cables, a lot of swearing, and I'm sort of at wit's end.
>>>>
>>>>     Has anyone else encountered this? Is there something obvious that
>>>>     I'm missing? Or something mysterious that I need to know? Or is it
>>>>     just a wonky micro:bit. I honestly didn't do a thing to it from
>>>>     when it worked fine until when it didn't, and it strikes me as a
>>>>     bit odd that it will do everything as before, EXCEPT echo the
>>>>     characters back to the terminal.
>>>>
>>>>     Halp?
>>>>
>>>>     Thanks,
>>>>     Naomi
>>>>
>>>>
>>>>     --
>>>>     Naomi Ceder
>>>>     https://plus.google.com/u/0/111396744045017339164/about
>>>>     _______________________________________________
>>>>     Microbit mailing list
>>>>     Microbit at python.org <mailto:Microbit at python.org>
>>>>     https://mail.python.org/mailman/listinfo/microbit
>>>
>>>     --
>>>     Sent from Postbox
>>>     <
>> https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach
>>>
>>>
>>>     _______________________________________________
>>>     Microbit mailing list
>>>     Microbit at python.org <mailto:Microbit at python.org>
>>>     https://mail.python.org/mailman/listinfo/microbit
>>>
>>>
>>>
>>>
>>> --
>>> Naomi Ceder
>>> https://plus.google.com/u/0/111396744045017339164/about
>>>
>>>
>>> _______________________________________________
>>> Microbit mailing list
>>> Microbit at python.org
>>> https://mail.python.org/mailman/listinfo/microbit
>>>
>>
>>
>>
>> _______________________________________________
>> Microbit mailing list
>> Microbit at python.org
>> https://mail.python.org/mailman/listinfo/microbit
>>
>>
> 
> 