|
Post by jackthevendicator on May 22, 2011 12:21:08 GMT -5
After making a mess with TI libraries, I've actually managed to create a working port of FreeRTOS for our Evalbot. You can find it here: www.assembla.com/code/freertos-evalbot/git/nodesYou can also find a list of supported integrated peripherals in the README.
|
|
|
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 jackthevendicator on Oct 30, 2010 12:30:54 GMT -5
|
|
|
Post by jackthevendicator on Oct 26, 2010 10:19:16 GMT -5
Just checked, the code for sflash has termios support for serial communication built in, it should compile on *nix systems without too much pain at all. sflash compiles as is: francesco@Gemstone:~/Programmi/IAR/sflash$ gcc -o sflash packet_handler.c uart_handler.c sflash.c francesco@Gemstone:~/Programmi/IAR/sflash$ ./sflash -h
Usage: sflash filename -p [program address] -r [execution address] -c [tty] -d -l [Boot Loader filename] -b [baud rate] -s [data size]
-p [program address]: if address is not specified it is assumed to be 0x00000000 if there is no 0x prefix is added then the address is assumed to be in decimal -r [execution address]: if address is not specified then no run command will be sent. -c [tty]: This is the name of the TTY device to use. -l [Boot Loader filename]: This specifies a boot loader binary that will be loaded to the device before downloading the application specified by the filename parameter. -b [baud rate]: Specifies the baud rate in decimal. -d Disable Auto-Baud support -s [data size]: Specifies the number of data bytes to be sent in each data packet. Must be a multiple of 4 between 4 and 252 (inclusive).
Example: Download test.bin using COM 1 to address 0x800 and run at 0x820 sflash test.bin -p 0x800 -r 0x820 -c 1 eflash must be ported from winsock to linux sockets, but runs on wine: francesco@Gemstone:~/.wine/drive_c/Programmi/IAR Systems/Embedded Workbench 5.4/arm/examples/TexasInstruments/Stellaris/tools/bin$ wine eflash.exe EFLASH Ethernet Boot Loader Download Utility (Version: 4652)
Copyright (C) 2009 Luminary Micro, Inc. All rights reserved.
usage: eflash [options] file
Download a file to a remote device, using the Ethernet Boot Loader. The file should be a binary image, and the IP and MAC address of the target device must be specified. Example: eflash -i 169.254.19.63 --mac=00.1a.b6.00.12.04 enet_lwip.bin
Required options: -i addr, --ip=addr IP address of remote device to program, in dotted-decimal notation (e.g. 169.254.19.63) -m addr, --mac=addr MAC address of remote device to program, specified as a series of hexadecimal numbers delimited with '-', ':', or '.'. (e.g. 00.1a.b6.00.12.04) file binary file to be downloaded to the remote device. (e.g. enet_lwip.bin)
Output control: --quiet, --silent suppress all normal output --verbose display additional status information --debug display additional diagnostic information
Miscellaneous: --version display program version information, then exit --help display this help text, then exit
Support Information: Report any bugs to <support@luminarymicro.com>
IAR runs on wine too: Uploaded with ImageShack.us
|
|
|
Post by jackthevendicator on Oct 25, 2010 16:20:03 GMT -5
From the So keep that in mind. As the evalbot currently ships, you *must* have batteries in it in order to talk to it via the ICDI port unless one of the above mention work arounds is performed. Maybe an high current low drop schottky diode (like those in switching power supplies) could do the trick?
|
|
|
Post by jackthevendicator on Oct 25, 2010 16:10:22 GMT -5
As far as I can tell, the LuminaryFTDI is just a driver for the slightly customized FTDI chip in the ICDI interface. It's a FT2232 dual USB-serial converter, with connections to UART0 and the JTAG interface. The most important puzzle piece for flashing the board would seem to be the actual protocol for downloading the program to the board. IAR uses JTAG to download programs (no bootloader). If you use their bl, they have provided code for two windows programmers(sflash for UART, eflash for ethernet) at arm\examples\TexasInstruments\Stellaris\tools With enough coffee, porting them to linux shouldn't be too horrible. urjtag has plenty of support for ft2232 cables... having the schematics, it should be very easy to write a interface configuration file.
|
|
|
Post by jackthevendicator on Oct 25, 2010 13:16:08 GMT -5
SafeRTOS is overkill for anything we will do. IIRC it's aimed at Hard Real-time and it's certified for use in critical systems that can't fail or people die. Of course... probably it does its best in medical/aeronautic applications. Anyway, other useful stuff: www.luminarymicro.com/products/eki-lm3s9b92.html
|
|
|
Post by jackthevendicator on Oct 25, 2010 10:03:40 GMT -5
|
|
|
Post by jackthevendicator on Oct 24, 2010 11:07:30 GMT -5
|
|
|
Post by jackthevendicator on Oct 24, 2010 7:32:28 GMT -5
I'm *extremely* happy to know I were wrong ;D Is there any chance that they are waiting to pack two items on a single shipping, since I had already ordered a launchpad on a previous order (backordered 27 october)?
|
|
|
Post by jackthevendicator on Oct 20, 2010 12:50:26 GMT -5
#6972 Still no ship date... I might be too pessimist, but I'm starting to think my order won't be fulfilled and will simply fall in a limbo... Too bad
|
|
|
Post by jackthevendicator on Oct 7, 2010 19:30:54 GMT -5
RE: SDIO RE: Motors So what kind of pulling power does that mean? 36W of pure electric power for each motor, with 75-80% efficiency (as wikipedia states). If we know the rpm, we can calculate the torque too. RE: Microphone Awesome! Lots of ideas there! I was thinking about a "sonar"/rangefinder based on time to travel of sound pulses... there was an article somewhere on the internet some time ago... --EDIT-- Article found ;D www.eddiem.com/projects/chirp/chirp.htm
|
|
|
Post by jackthevendicator on Oct 7, 2010 17:18:55 GMT -5
I'm just reading the schematics, and it seems that the audio encoder supports a microphone (the input lines should be on a header). It supports SDIO too (the lines are on one of the wireless headers), so you can buy a wi-fi sdio card and write a driver for it. The motors run at 12V and the controllers can withstand a maximum current of 3A, then they will "trip" and will put a fault signal low. The controller also supports braking by recirculating the back-EMF from the motors.
|
|