I have an older EKI-LM3S811 with IAR workbench board/eval-kit works perfectly.(revision 4652 of the EK-LM3S811)Purchased from Digikey (Grey and Orange colors on case, says IAR RevA9 on spine).
I have now purchased two additional EKI-LM3S811kits (Rev. B12 on Spine, (Says Texas Instruments on the board) that will not install and run properly on other XP machines.
On one, after installing from CD in a virgin XP machine, when I download the examples that put texton the OLED display, the text comes out mirror reversed, and offset about 1/4th from the edge. Even a download of the Asteriods game (qs-ek-lm3s811) plays but with the screen mirror reversed.This is the kit in the black case with the red TI logo on the front. Anyone else report this? Possibly the new board has reversed the OLED wiring on the new board but there is an old OLED driver on the new CD?
When I bring in a fairly complex working 3S811 design created on the original eval kit,the design will not compile, download and run using the new kit. I can see that the board layout has been changed.Is there a list of changes from the Luminary issued EKI-LM3S811 to the TI-issued version?
What incompatibilities were introduced?
Thanks for any help
RonF,
This sounds like an issue with the drivers on your PC recognizing and implementing the EKI-LM3S811 hardware. I recommend following the instructions in the “Installing the Drivers” section of the 811-EVBK.pdf document for the "virgin XP machine."
Lela
I'm getting this same problem: "text comes out mirror reversed".
I'm using a new LM3S811 with FreeRTOS and running the demo that came with FreeRTOS.
."\FreeRTOS\FreeRTOSV7.1.0\Demo\CORTEX_LM3S811_GCC"
I compiled with the latest version of the Lite version of Sourcery CodeBench (gcc).
Any ideas what is causing this mirror images, reversed text?
Thanks!
---------------
Joseph,
Can you compile and program a more simple program, such as hello and let me know what the result is.
I have spoken with someone that experienced this issue before....
In June of 2010, the display on the EK-LM3S811 changed from an OSRAM to a RIT. The different display's and software updated needed is most likely the cause of the reversed text. The software team updated driver/display96x16.1.c/.h to do a read of the DID1 register to determine which display is on the board. All versions of Stellarisware 6075 or later (most current is 8049) have the drivers for both displays.
Have you updated your Stellarisware (driverlib) recently? If not, please do so at www.ti.com/stellarisware.
I successfully compiled the latest version of FreeRTOS 7.1.1. The simplest way is to copy over the new display96x16x1.c and the display96x16x1.h file from here:
C:\StellarisWare\boards\ek-lm3s811\drivers
Then rename them to the osram96x16.c and the ".h" file names -- then you don't have to change the program.
In my case the destination was here...
D:\FreeRTOS\Source\FreeRTOSV7.1.1\Demo\CORTEX_LM3S811_IAR\LuminaryCode
I moved all the files into an "OLD" directory except for "DriverLib.h" -- I modified it to pick up the new driverlib and inc directories inside LuminaryCode.
I also moved over files from here:
C:\StellarisWare\driverlib
C:\StellarisWare\inc
And put them inside the LuminaryCode directory.
I modified osram96x16.c to pint to the header file in "inc"
If you get compile errors it should be obvious as how to change them -- e.g.
#ifndef DRIVER_LIB_H#define DRIVER_LIB_H#include "DriverLib.h"#include "inc\hw_adc.h"#include "inc\hw_comp.h"#include "inc\hw_flash.h"#include "inc\hw_gpio.h"#include "inc\hw_i2c.h"#include "inc\hw_ints.h"#include "inc\hw_memmap.h"#include "inc\hw_nvic.h"#include "inc\hw_pwm.h"#include "inc\hw_qei.h"#include "inc\hw_ssi.h"#include "inc\hw_sysctl.h"#include "inc\hw_timer.h"#include "inc\hw_types.h"#include "inc\hw_uart.h"#include "inc\hw_watchdog.h"#include "inc\osram96x16.h"#include "driverlib\adc.h"#include "driverlib\comp.h"#include "driverlib\cpu.h"#include "driverlib\debug.h"#include "driverlib\flash.h"#include "driverlib\gpio.h"#include "driverlib\i2c.h"#include "driverlib\interrupt.h"#include "driverlib\pwm.h"#include "driverlib\qei.h"#include "driverlib\ssi.h"#include "driverlib\sysctl.h"#include "driverlib\systick.h"#include "driverlib\timer.h"#include "driverlib\uart.h"#include "driverlib\watchdog.h"#endif
If I can do it with my level of knowledge -- you can too...
Hope that helps people...
Dave Robinson