We are using ARM7-TDMI for it . (LPC 2148 precisely) The thing is that we are not using any development boards . So that means that we will be doing bare metal programming (or thats what we concluded). I found the toolchain presentation on embeddednirvana quite helpful .
I had a few questions : 1. What all do you need to take care of while running a basic code on an ARM processor ? Hardware and software wise . We have taken care of the basics like reset logic , power supply , clock , etc . Whats the hello world of h/w programming ? Should I generate a square wave on one of the GPIO pins ?
2.How helpful would QEMU be ? Because we wont be having a GUI as such . We have to just read sensors outputs using the ADC and convert it to signals which we can send to the PC (via USB) .
3.As we are using LPC 2148 , is it necessary to use flash magic ? http://www.flashmagictool.com Does anybody have any experience with this ? Is there any other open source tool that could do this ?
4. If anyone has any good resources which google has missed , those would be most welcome .
As this is my first project on ARM , any other general advice and tips will be most helpful :)
> We are using ARM7-TDMI for it . (LPC 2148 precisely) > The thing is that we are not using any development boards . So that means > that we will be doing bare metal programming (or thats what we concluded). > I found the toolchain presentation on embeddednirvana quite helpful .
> I had a few questions : > 1. What all do you need to take care of while running a basic code on an > ARM processor ? Hardware and software wise . We have taken care of the > basics like reset logic , power supply , clock , etc . Whats the hello > world of h/w programming ? Should I generate a square wave on one of the > GPIO pins ?
1. I guess for LPC series 2148 lot of code is already available. I would suggest not to re-invent the wheel unless you are doing it as a hobby.
> 2.How helpful would QEMU be ? Because we wont be having a GUI as such . We > have to just read sensors outputs using the ADC and convert it to signals > which we can send to the PC (via USB) .
2. I would suggest you work with the hardware. QEMU would not be much of use, unless you are trying to port some OS, or some other tool.
Don't use flashmagic, get a JTAG (would cost less than 1000 bucks) and use openocd and GDB. This would be very useful for you debug your program step by step
> Does anybody have any experience with this ? Is there any other open > source tool that could do this ?
>> We are using ARM7-TDMI for it . (LPC 2148 precisely) >> The thing is that we are not using any development boards . So that means >> that we will be doing bare metal programming (or thats what we concluded). >> I found the toolchain presentation on embeddednirvana quite helpful .
>> I had a few questions : >> 1. What all do you need to take care of while running a basic code on an >> ARM processor ? Hardware and software wise . We have taken care of the >> basics like reset logic , power supply , clock , etc . Whats the hello >> world of h/w programming ? Should I generate a square wave on one of the >> GPIO pins ?
> 1. I guess for LPC series 2148 lot of code is already available. I would > suggest not to re-invent the wheel unless you are doing it as a hobby.
>> 2.How helpful would QEMU be ? Because we wont be having a GUI as such . >> We have to just read sensors outputs using the ADC and convert it to >> signals which we can send to the PC (via USB) .
> 2. I would suggest you work with the hardware. QEMU would not be much of > use, unless you are trying to port some OS, or some other tool.
> Don't use flashmagic, get a JTAG (would cost less than 1000 bucks) and > use openocd and GDB. This would be very useful for you debug your program > step by step
>> Does anybody have any experience with this ? Is there any other open >> source tool that could do this ?
Actually i was trying to get one of those (raspberry pi) , but just to learn and not for this project as such. I have registered for it , but i guess it will take quite some time . I actually already use linux as much as i can . I use debian . I also wanted to ask about the weekly meetings at embedded nirvana . What are the timings for it ? And where are they held in COEP?
I would recommend debian for all development work. Fedora and ubuntu tend to be not so debugged, in exchange for having the latest and greatest software and features.
We usually meet up the Embedded Design Center Lab, COEP, Dept. of Instrumentation and Control. We will post on the group about the next meeting. Till then you can ask your doubts on this group.
Regards, Tanushri
On Sun, Mar 18, 2012 at 10:40 PM, J T Dsouza <jtd1...@gmail.com> wrote:
> I would recommend debian for all development work. Fedora and ubuntu tend > to be not so debugged, in exchange for having the latest and greatest > software and features.
>> Just in case you felt the need of a development board then do check this:
