 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : Micromite Bug report.
| Author | Message | ||||
Oldbitcollector Senior Member  Joined: 16/05/2014 Location: United StatesPosts: 172 |
I'm working on a project which links another micro to the Micromite. I'm seeing a switch from the BAUD RATE 115200 back to it original 38400 when the Micromite has sit un-powered for a few hours. Thought I'd bring out my experience here and see if anyone else has seen behaviour like this. Jeff My Propeller/Micromite mini-computer project. |
||||
Geoffg Guru  Joined: 06/06/2011 Location: AustraliaPosts: 3167 |
Are you talking about the console baudrate? If so, that is very strange, Is everything else reset? Ie, is the program in memory erased? What version of MMBasic are you using? Geoff Geoff Graham - http://geoffg.net |
||||
| Oldbitcollector Senior Member Joined: 16/05/2014 Location: United StatesPosts: 172 |
Yes, It's the console baudrate that seems to jump back to 38400 after sitting un-powered for more than an hour. The first few times, I disconnected my other micro, connected a USB-to-Serial TTL adapter, got it to start communicating at 115200, then reconnected the micro without issue. (weird huh?) Over the course of a programming session, I can power off and power on the combination without issue. It only seems to happen when the Micromite has been powered off overnight, or for at least an hour or more. Today, just as a whim, I dropped the baudrate on my micro back to 38400 and discovered that the garbage characters I was seeing was simply the Micromite running at a slower speed. The program memory doesn't appear to be affected by the issue. Version is: 4.5C For now, I'm dropping all of the baud rates in my programs to 38400 as a work around. Since I'm using both console and I2C communication channels, it shouldn't be a big issue for my project. Jeff My Propeller/Micromite mini-computer project. |
||||
| Oldbitcollector Senior Member Joined: 16/05/2014 Location: United StatesPosts: 172 |
Just for reference this is what I'm doing with the Micromite. http://propellerpowered.com/forum/index.php?topic=574.0 The first three posts explain the project and how it works. Jeff My Propeller/Micromite mini-computer project. |
||||
TassyJim Guru Joined: 07/08/2011 Location: AustraliaPosts: 5923 |
I tried with the micromite off for just over an hour with no problems. I will leave one off overnight and see what happens in the morning. You could put OPTION BAUDRATE 115200 at the beginning of your program if you want to keep the higher baudrate. Jim VK7JH MMedit MMBasic Help |
||||
| Oldbitcollector Senior Member Joined: 16/05/2014 Location: United StatesPosts: 172 |
I suspect it has something to do with I/O states of the other micro's pins at startup. I've tried the delay circuit listed on page 14, but 350ms is probably still too short. Placing OPTION BAUDRATE 115200 at the beginning of the program might be a possibility, except that when the Micromite doesn't switch down, firing this command in at 38400 will create a lot of garbage that will need to be accounted for and then cleaned up on the RX side of the other micro. It's a sloppy fix. For now, I'll consider myself on the bleeding edge of the technology. Since I've not seen anyone else putting the Micromite in this configuration, and simply switch down to the lower speed. I've still got plenty of horsepower at 38400 for my current needs. Jeff My Propeller/Micromite mini-computer project. |
||||
 Print this page |
