Activity log for bug #145618

Date Who What changed Old value New value Message
2007-09-27 12:47:30 Kofi Leblanc bug added bug
2007-09-27 14:35:26 Kofi Leblanc description Equipment: Hardware: 1. usb-to-rs232 cable (PL2303H) 2. 68hc11 microcontroller Software: 1. ubuntu running ckermit (or minicom) What works: 1. When I manually reset the microcontroller it sends its prompt - "BUFFALO 3.4 (ext) - Bit User Fast Friendly Aid to Logical Operation" Which means: 1. Receive (Rx) is working 2. The speed is configured correctly 3. No other hardware issues What doesn't work: 1. When I send text commands I get no response from the microcontroller. 2. File transmission Behavior: 1. At the connection window the blinking prompt goes blank momentarily but no character appears (The character echo is handle by the controller, so typing characters will appear at the prompt) 2. The microcontroller's LED indicating transmission is not receiving a signal Noticeable behaviour: 1. I've successfully been able to communicate with the microcontroller using a MAC OS X laptop. (Using the same cable running kermit) 2. When I restart ckermit in Ubuntu, I notice that it sends a command to the microcontroller. For instance, if i were attempting to see a memory dump of the contents of the microcontroller I would type: md 1400 When i restart ckermit, this command would be sent to the microcontroller. (Perhaps the cable is clearing out it's buffer) ... Well that's it. Thanks for reading this far. Hopefully my problem is easily solvable. please terminate.
2008-08-08 11:38:19 Jean-Baptiste Lallement None: status New Incomplete
2008-08-08 11:38:19 Jean-Baptiste Lallement None: statusexplanation Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). Thanks!
2008-09-01 21:03:34 Jean-Baptiste Lallement None: status Incomplete Invalid
2008-09-01 21:03:34 Jean-Baptiste Lallement None: statusexplanation Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). Thanks! We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!