I haven't actually worked with the raspberry pi, but I'm currently working with a similar processor, a Texas Instruments ARM Cortex A8 that runs at 720MHz. On my processor, you have to set up the PLL to take the 24MHz external oscillator to 720MHz, configure several clocks for peripherals, set up the MMU with a huge table of memory addresses and their cache settings, configure the GPIO bank, Select the proper multiplexed setting for the actual pin that the signal is output to, etc. This is all in C as well.
Are you saying that the code you linked is loaded with some sort of JTAG device, and is the entirety of the code running on the chip, or is it run from the command line?
Maybe Texas Instruments are just a bunch of sadists.
> Are you saying that the code you linked is loaded with some sort of JTAG device, and is the entirety of the code running on the chip, or is it run from the command line?
That's all the code you need to write. You also need a firmware binary supplied by the raspberry pi people. You write your binary and the firmware binary to an SD card, and the pi boots and runs your code via some process that is frankly opaque to me. Alternatively you can stick a bootloader on the card and transfer your binary via an ftdi cable, which is a lot less hassle while developing. All this is detailed in the repo I linked if you're interested.
Using the onboard peripherals is admittedly fairly challenging, largely due to the paucity of documentation available. Hopefully more documentation and examples will emerge as more of us tinker with it.
I'm not yet in a position to compare and contrast to TI's stuff, but I have a Stellaris Launchpad I intend to start playing with soon. Will be interesting to see how it compares.
Are you saying that the code you linked is loaded with some sort of JTAG device, and is the entirety of the code running on the chip, or is it run from the command line?
Maybe Texas Instruments are just a bunch of sadists.