×

SparkFun Electronics will be closed on July 3rd, 2015 in observance of Independence Day. Any orders placed after 2:00pm MT on July 2nd will be shipped out after the weekend. Thanks!

DigitalMagZ

Member Since: January 7, 2010

Country: United States

  • PEOPLE HAVING SCREEN CONFIG ISSUES!! Many people have made comments regarding the stability and reliability of these type of screens and their firmware. Something to keep in mind when using these screens.

    They are their own system, running their own microprocessor and getting both commands and data from a UART interface.

    If you have this screen (or any other serial device) connected to the same UART that is being used to program the board (ie: any Arduino with one UART and using that UART with the screen (Rx and Tx pins)), you run the risk of inadvertently sending commands during the programming process to the LCD that reconfigure it and cause it to not behave as expected!

    Think about it. When you program an Arduino, both Rx and Tx LEDs show activity, meaning that the Arduino IDE is sending data to the board, and the board is responding. If the LCD screen is ALSO connected to the Arduino via the Rx and Tx pins, it too will be reading the bytes that is being send back to the IDE. If there is a byte sequence that includes the command to change the LCD baud rate, defined screen size, or whatever, then your screen will most likely not work correctly unless you send the appropriate commands to reconfigure it.

    Either unplug the screen during the programming process, or ensure that the screen is using it’s own UART (another hardware UART or a software UART) so that the programming process does not change the configuration. Otherwise, who knows what baud rate or screen size it will be set too and yes, you will get random characters, no characters, and inconsistent cursor locations. Initially, I had the same problems as others have commented on. I have been using these screens for years without any issues once I realized this gotcha.

  • PEOPLE HAVING SCREEN CONFIG ISSUES!! Many people have made comments regarding the stability and reliability of these type of screens and their firmware. Something to keep in mind when using these screens.

    They are their own system, running their own microprocessor and getting both commands and data from a UART interface.

    If you have this screen (or any other serial device) connected to the same UART that is being used to program the board (ie: any Arduino with one UART and using that UART with the screen (Rx and Tx pins)), you run the risk of inadvertently sending commands during the programming process to the LCD that reconfigure it and cause it to not behave as expected!

    Think about it. When you program an Arduino, both Rx and Tx LEDs show activity, meaning that the Arduino IDE is sending data to the board, and the board is responding. If the LCD screen is ALSO connected to the Arduino via the Rx and Tx pins, it too will be reading the bytes that is being send back to the IDE. If there is a byte sequence that includes the command to change the LCD baud rate, defined screen size, or whatever, then your screen will most likely not work correctly unless you send the appropriate commands to reconfigure it.

    Either unplug the screen during the programming process, or ensure that the screen is using it’s own UART (another hardware UART or a software UART) so that the programming process does not change the configuration. Otherwise, who knows what baud rate or screen size it will be set too and yes, you will get random characters, no characters, and inconsistent cursor locations. Initially, I had the same problems as others have commented on. I have been using these screens for years without any issues once I realized this gotcha.

  • Im having a difficult time with this device. It seems the UART is very unreliable when sending commands via Hercules. I send music commands, and it might work ONCE, then I get the ERROR response when I send any other commands. The GPIO buttons always work and if I use them, I can send another command via UART before it breaks again. Whats up with that?

    Edit: I have found out that the module expects a return carrage ‘\r’ after the command. When I used Hercules, I was pressing enter after commands, which sends a ‘\n\r’. The module does not like the ‘\n’ before the ‘\r’ and it will cause problems… Just an FYI!

    Also, how does one obtain the firmware upgrade software and upgrade tool??

  • Ummmmmmm…. What’s up with Rx and Tx not being swapped on the FTDI port?? I tried direct connecting my FTDI and realized that Rx on the FTDI goes to Rx on the breakout board. Same with Tx. What gives??

  • +1 for a module only option!!!

  • Anyone else having issues with these boards? Using Windows 7 64-Bit, the setup does not follow the tutorial. When I plug the board in, it comes up in device manager as “Sparkfun ProMicro bootloader” with the “new USB” sound initially, then I get the “USB removed” sound and the device changes name to Arduino Leonardo before I install or try to upload anything. I installed the Leonardo drivers but when I try to load a sketch, i get the following error at the upload stage:

    avrdude: ser_send(): write error: sorry no info avail

    I have been at this for hours. I got two boards and tried three computers (one was a WinXP 32 virtual machine)…same problems…

    Yes, im using Arduino 1.0 with the modified boards.txt file for Leonardo.