|
|
Post by senatorpenguin on Nov 16, 2010 22:23:20 GMT -5
Here are the things you need to get your Evalbot up and running without having to rely on trial versions of expensive IDEs: 1. The Stellaris Firmware Development Kit. www.luminarymicro.com/products/software_updates.htmlThe "EK-LM3S9B92 Firmware Development Package" is what you need to download and extract somewhere. This has all of the examples, drivers, libraries, and utilities you need except for: 2. LMFlash.exe, to program the evalbot without using the bootloader. This is the only part of the process that requires Windows as far as I'm aware (let me know if you find a way around this). It is on the same page as the sdk, but under the Utilities tab. 3. A working toolchain for the ARM processor. The instructions here worked well for me (I'm on a Core 2 Duo MBP): claymore.engineer.gvsu.edu/egr326/LM3S6965Under "Tips & Tricks" are also invaluable instructions for getting Mac drivers for the ICDI interface, though I didn't need to do the kextload-ing (more than once) or the rebooting. 4. The utility to send any program updates to the board over the USB-serial port, sflash. Its precompiled in the tools/bin directory of the sdk for windows, otherwise just compile it with make (it will name it and all tools .exe regardless of what system you are on). Once you have these, you should be able to build all the examples in the SDK simply by navigating to the top level of the SDK and running 'make' (provided the cross-compiler is in your path environment variable) The .bin files that are created in the gcc directory of each project directory can be programmed to the Evalbot using LMflash.exe, but since I prefer development in OS X, the bootloader is preferable. Adding this snippet of code to the top of any main.c file (or blinky.c in my case) will cause the execution to jump to the bootloader (conveniently located in the ROM on the chip) if Switch 1 is pressed when the chip is reset. #include "inc/hw_types.h"
#include "inc/hw_memmap.h"
#include "driverlib/debug.h"
#include "driverlib/rom.h"
#include "driverlib/gpio.h"
#include "driverlib/sysctl.h"
#include "utils/uartstdio.h"
//Check for a firmware update
//Hold down switch 1 while resetting to trigger an update
void bl_check() {
//Configure switch 1 as an input w/pullup (input normally high)
ROM_SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOD);
ROM_GPIOPinTypeGPIOInput(GPIO_PORTD_BASE, GPIO_PIN_6);
ROM_GPIOPadConfigSet(GPIO_PORTD_BASE, GPIO_PIN_6, GPIO_STRENGTH_2MA, GPIO_PIN_TYPE_STD_WPU);
//update the firmware if the button is pressed
if (ROM_GPIOPinRead(GPIO_PORTD_BASE, GPIO_PIN_6) == 0) {
//Configure UART0 to receive flash update
ROM_SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOA);
ROM_GPIOPinTypeUART(GPIO_PORTA_BASE, GPIO_PIN_0 | GPIO_PIN_1);
UARTStdioInit(0);
//jump to the bootloader in ROM
//This never returns
ROM_UpdateUART();
}
}
This bl_check() function should be called immediately after configuring the clock in main(). Attached is the project directory of the blinky example with the bootloader code and a cleaned up Makefile. All that needs to be adjusted is the location of the StellarisWare SDK in the ROOT variable of the Makefile. Once this has been programmed into the Evalbot with LMflash.exe, the sflash program on any system can be used to send updates if you first hold down switch 1 while pressing the reset button. Attachments:
|
|
|
|
Post by senatorpenguin on Nov 16, 2010 22:34:41 GMT -5
I've been able to get the OLED driver, motor driver, and USB host controller working as well. I've attached the code for using each of these. The USB host code only works with mice, but the examples should show you how to get started with other devices. Also in the attachment is a demo project with with an expanded makefile (make install will run sflash) that displays things on the screen, and moves around based on the clicks of a standard wireless 3-button mouse. I look forward to seeing what everyone can do with this incredibly full-featured little bot. Attachments:
|
|
kemp
New Member
Posts: 24
|
Post by kemp on Nov 17, 2010 11:17:22 GMT -5
This looks *very* helpful. I was hoping to ditch the official bootloader and so on as soon as possible.
|
|
ghost
New Member
Posts: 3
|
Post by ghost on Jan 25, 2011 9:16:18 GMT -5
Thank you for your great tutorial.
I also tried to compile the librarys from micrium for my own projects but I didn't succeed.
Now I'm trying to compile your example but it won't work.
This is the output
CC hello.c
hello.c: In function 'main':
hello.c:145:5: warning: array subscript has type 'char'
CC startup.c
startup.c:34:0: warning: ignoring #pragma language
CC ../../../StellarisWare/utils/uartstdio.c
CC ../peripherals/motor.c
CC ../peripherals/oled.c
CC ../peripherals/usbhost_mouse.c
../peripherals/usbhost_mouse.c: In function 'USBHCDEvents':
../peripherals/usbhost_mouse.c:78:8: error: 'USB_UART_EN' undeclared (first use in this function)
../peripherals/usbhost_mouse.c:78:8: note: each undeclared identifier is reported only once for each function it appears in
../peripherals/usbhost_mouse.c: In function 'usb_modeCallback':
../peripherals/usbhost_mouse.c:133:8: error: 'USB_UART_EN' undeclared (first use in this function)
../peripherals/usbhost_mouse.c: In function 'usb_mouseCallback':
../peripherals/usbhost_mouse.c:155:8: error: 'USB_UART_EN' undeclared (first use in this function)
make: *** [gcc/usbhost_mouse.o] Fehler 1
|
|
|
|
Post by artvandelay on Jan 25, 2011 10:14:02 GMT -5
Ghost: looks like this was an error in the program. Try adding
#define USB_UART_EN 1
somewhere up in the headers.
|
|
ghost
New Member
Posts: 3
|
Post by ghost on Jan 25, 2011 11:56:06 GMT -5
Ghost: looks like this was an error in the program. Try adding #define USB_UART_EN 1 somewhere up in the headers. Thx, it works now |
|
|
|
Post by senatorpenguin on Jan 26, 2011 3:27:17 GMT -5
Thank you for your great tutorial. I also tried to compile the librarys from micrium for my own projects but I didn't succeed. The micrium code is all written for their expensive real-time operating system that the evalbot was created to sell, so it won't compile unless you use uCOS III. However, reading how their peripheral libraries work offers insight into how to use some of the more interesting and less documented aspects of the board. Especially the OLED screen, which I can only guess as to which controller it uses. |
|
dids
New Member
Posts: 2
|
Post by dids on Feb 4, 2011 0:56:46 GMT -5
Having all sorts of problems wrapping my head around this.
I've been comparing my code to your code, even had a peek at the nunchuk library code.
What I'm looking for at the moment is being able to use the left and right bumpers for input, to trigger certain type of motor movement. I've set the bumpers as input and in my while loop I've got an if checking to see if the bumpers pressed.
The behaviour is really weird, if it's plugged into USB, the motor will spin for a fraction of a second and right after that the USB connection will disconnect and then reconnect.
Now, I should also add that if I use ROM_SysCtlClockSet(SYSCTL_SYSDIV_4 | SYSCTL_USE_PLL | SYSCTL_OSC_MAIN | SYSCTL_XTAL_16MHZ); the OLED display shows a random pixel mess and the whole thing becomes somewhat unresponsive.
Also, I've commented out UARTStdioInit(0); as the compiler produces an error about referencing UARTStdioInit, which I have no clue about as my code's pretty identical to the sample ones available. My compiler setup is my own though, running Windows, CodeSourcery G++ Lite with Eclipse.
Any ideas would be greatly appreciated. :-)
|
|
|
|
Post by laiudm on Feb 5, 2011 9:58:24 GMT -5
Great work with your demo.zip senatorpenguin!
Unfortunately when I load hello.bin on my EvalBot the USB interface doesn't work. The +5v power to the USB port doesn't even get turned on, although the OLED display and UART work.
I've separately confirmed the +5v PSU works (I tweaked blinky to set
EN_VBUS high), so know there's not a hardware problem.
Does anyone have any ideas what the problem could be? My chip is rev C3; have others got this app working on this rev?
Cheers,
Dave
|
|
|
|
Post by jackthevendicator on Feb 5, 2011 18:02:38 GMT -5
Great work with your demo.zip senatorpenguin! Unfortunately when I load hello.bin on my EvalBot the USB interface doesn't work. The +5v power to the USB port doesn't even get turned on, although the OLED display and UART work. I've separately confirmed the +5v PSU works (I tweaked blinky to set EN_VBUS high), so know there's not a hardware problem. Does anyone have any ideas what the problem could be? My chip is rev C3; have others got this app working on this rev? Cheers, Dave According to the schematics, PB0 (Port B GPIO 0) must be set low to enable usb host mode, so you just need to add the following lines under ROM_SysCtlPeripheralEnable(SYSCTL_PERIPH_USB0);: ROM_GPIOPinTypeGPIOOutput(GPIO_PORTB_BASE, GPIO_PIN_0);
ROM_GPIOPinWrite(GPIO_PORTB_BASE, GPIO_PIN_0, 0); |
|
|
|
Post by martinhubacek on Feb 5, 2011 18:42:00 GMT -5
Hi, I cannot run the Evalbot with hello.bin example app & mouse too.
1. The power is not applied to USB Host connector
so i added
SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOA);
GPIOPinTypeGPIOOutput(GPIO_PORTA_BASE, GPIO_PIN_6);
GPIO_PORTA_DATA_R |= 1 << 6;
and the power is applied but only for a while, the next function init_usbHostMouse(); turn the power off again.. No luck even if i try to add USB power on code after the calling the init_usbHostMouse(); function.
2. The USB Host/Device switch doesn't solved the issue. I have double checked schematics, measured the TP22 to make sure there's logical low signal...
Any other ideas please?
|
|
|
|
Post by laiudm on Feb 6, 2011 8:53:58 GMT -5
All, I have spent a huge amount of time trying to get usb-host mode working. I've read and re-read the documentation, walked through the usblib code etc., and concluded that the OTG-specific functionality is somehow broken. Either it's a chip fault or a fault on my evalbot. I finally gave up on the OTG-mode and instead tried getting it to work in purely host mode (which is really what I want anyway!). I've now got this working! I've attached the files that change from senatorpenguin's post above. Try my demo.bin and see if it works for you. Specific changes from the original code are: - Added define for USB_UART_EN (mentioned earlier)
- Added code to set PB0 to 0 (although this isn't strictly necessary, since there's already a pull down on that pin).
- Made a number of other simple changes from OTG calls to HCD calls.
- Changed the interrupt driver in startup.c to point to the host interrupt handler.
Let me know how you get on. Cheers, Dave Attachments:
|
|
|
|
Post by laiudm on Feb 6, 2011 10:09:57 GMT -5
I've now tweaked the usb_host_msc application that comes as a part of StellarisWare for the ek-lm3s9b92 board. The tweaks take account of hardware differences between that board and the evalbot (and the fact that OTG USB modes doesn't seem to work). If you update the StellarisWare directory with the attached files it should work on your evalbot. I've included us_host_msc.bin too in case you want to try it out before trying to compile it for yourself. Note: I've only updated the gcc version, as I'm using that as my toolchain. If you have another toolchain you'll need to update the corresponding startup.c file. Attachments:
|
|
|
|
Post by martinhubacek on Feb 6, 2011 13:27:29 GMT -5
Thanks laiudm ! It all works perfectly now. Now I can learn to work with USB. Both samples works.
Thanks a lot again.
|
|
|
|
Post by senatorpenguin on Feb 7, 2011 3:53:35 GMT -5
Cool, it seems like everyone figured out the glitches in my code. Aside from the USB_UART_EN (that define was in a file I forgot to attach) the rest were hacks I included to deal with the old revision of the chip I have. I got the Evalbot back in October with a B1 rev chip, which has all sorts of screwy glitches in the USB OTG mode, and I doubt they help on the newer revs.
|
|
