squalyl

Else you will need 16+ GPIOs to drive the data bus, RD, WR, CS, etc... http://en.wikipedia.org/wiki/Parallel_ATA A digital audio stream is at least 44100sps * 2ch * 2bytes/sample = 176400 bytes per second that will have to be sent to an audio DAC via I2S. This seems doable but not interesting. You can still use the IDE interface to emit audio playback events (start, stop, seek) and read the TOC (track duration etc) but you'd better use a cd drive with an analog output. it was quite common in the IDE days. Some of them even have a TTL SPDIF output.

Small update: beware of the GPIODATA register Adress lines 9..2 act as a mask, so it's useless to write at GPIODATA+0x000 See page 608 of datasheet... The LM4F is the first microprocessor that forces me to do that much RTFM!

Yes, we crossed messages ! as always, writing about my problem made me find it. I'm now setting the correct bit in GPIOHBCTL, and it works \o/ So guys, in order to access GPIO via the AHB addresses, you have to set the correct bit for your port in the GPIOHBCTL register, address 0x400fe000+0x06C , page 247 of datasheet ! Hope it can be useful to someone else!

hello I'm playing with my stellaris launchpad, I got openocd 0.7.0 working and I'm trying to write my own GPIO init code. I wrote this generic routine to initialize the uart pins. I've defined several flags, and according to the value of these flags, I'm attempting to write the appropriate GPIO configuration registers. For that, I'm using the AHB access method, writing to BASE+OFF where OFF is the offset of the required register (eg #define LM4F_GPIO_GPIODIR 0x400 // GPIO Direction) BASE is 0x40058000 + (port<<16) I'm using this because it's easier to com

./3 oh, I didn't realize that! nice idea

thank you !

hello, I had the idea to start a french stellaris forum. But I have no time to manage it properly, and the activity is not so high, so I closed it. So I think a multilingual section is a more efficient way of doing things. Then maybe, could I redirect my DNS entry to the french speaking section?

why don't you refer to the real reference, the datasheet? This is a must-read, this issue is clearly explained in the GPIO chapter. I don't mean "read through the 1200 pages in a row", but "open the chapter for the module you're using and rtfm!".

I made something close: a zero-dollar veroboard booster pack from drawer parts: Obviously It's juste a base for something else

so what can you run with that? bash? what more?

if you want to play with 802154 there is the MRF24J40 module from Microchip. At farnell it's €8. I'm actually planning a boosterpack using this thing.

Hello, I'm actually using the official toolchain from ARM on launchpad. I have no problem to compile code. Did not execute anything yet, because I'm working on other things in parallel. regards

I just did like the github project. TARGET=arm-none-eabi the prefix is /opt/stella Do you have a preference for $PREFIX? the binaries have "natural" names, do arm-none-eabi-gcc et al. I know one can create a relocatable toolchain so that it does not depend on the prefix and can be installed elsewhere, I don't remember how to do this at the moment. I also cross-built binutils for mingw, working on gcc now.

Based on the makefile from the github project above, I could build a native "vanilla" toolchain from official sources, with just two little glitches: -I have to manually create a $PREFIX/arm-none-eabi/usr/include folder before building gcc the second time, or it won't build! (but nothing gets installed there) I get a pretty message: "the directory that should contain system headers does not exist", but no one on the intarwebs seems to have a satisfying solution. I don't want to patch sources, the goal is to build from official tarballs. -ld cannot find crt0.o when running arm-none-eabi

Okay, I'm building one now. I expected some patches to be required. thanks!