MicroPython Forum (Archive)

Ok, that makes perfect sense, I can see how that would make it a bit more challenging trying to test and port to the '429. Thanks for the explanation, every bit helps.

-Larry

Thanks for the complete and informative reply to my last question, badi. I can understand what you're saying but I am definitely no USB expert so I wish you the best in finding a solution. Is there anything different about the 429 USB implementation vs. the 405 used on the PyBoard? They all seem to ...

Sorry I'm late to the party, @pythoncoder what you're thinking of is generally handled via automated assembly using a 0 ohm "resistor" since depositing a solder blob across contacts would be complicated due to the surface tension over the solder mask. Or at least that's the way I'm familiar with.

Hi, I decided to give the code from badi's branch for adding the STM32F429 board support a shot and have some observations... First off, I'm not clear on whether the code is partially working on has some issues remaining, from some of the notes for changes it looked like it was at least running if n...

Hi Dave, I've been looking at the existing stmhal code and it definitely looks like a better bet for current porting needs, so I think I will end up copying that and re-working it instead now that I've had a chance to get my feet wet. I did have one question about one of your posts: I expect that I'...

Actually, the "dead" code was from before a restructuring was done in MicroPython. At the time, stmhal hadn't finalized the APIs for peripherals and stuff, and I just went ahead and created something, which is what I used for: http://blog.davehylands.com/2014/01/micropython-running-on-teensy-31.htm...

@dhylands - re: recent code changes Yep, I have pushed several times recently, which might be part of the problem ;-) Things are changing rapidly as I keep finding new things I'm doing wrong, and there's always something new to fix... I've been looking at your HAL code for Teensy as I realized I did...

Hi Dave, Thanks for the tip, I've done quite a bit of work and finally gotten something working in a very rough state. Currently UART.init and UART.write work, although init only sets the baud rate currently. To specify which port to write to you add a keyword argument of uart_id, like so (It defaul...

[I can't edit my previous post since it hasn't been approved by the moderator] Dave, I made a mistake in my last post, the hang is actually in the memset of &self->uart at line 228 in the pyb_uart_init_helper function. I'm not clear on why writing to that should cause it to hang, hence my confusion ...

Thanks for the reply, Dave. I've finally gotten around to forking the project and merging in my changes. Things are kind of a mess in uart.c since I was playing around trying to figure out why it locked up every time I tried to initialize the UART via uart_init. Looks like the struct that's being pa...