Re: [anjuta-devel] GSoC: Anjuta as an AVR development environment



Great to hear you also like the idea Sebastien, as Johannes already pointed out, my primary focus will be lying on AVR microcontrollers, but I will design it in such way, that it would be easily adaptable for other types of microcontrollers.

AVR Microcontrollers are really cheap, and there are a lot of open source programmers which costs around $20 for a kit, and even less when you buy each component yourself.

For the CPU simulator, you mean the AVR simulator? simulavr is a quite good AVR simulator (their trunk version supports more recent AVR microcontrollers like the atmega48/88/168 and more).

With kind regards,
Lucas

2011/3/23 Johannes Schmid <jhs jsschmid de>
Hi!

> I would probably give a bit higher priority than Johannes to make this
> working in Anjuta. We have such requests from time to time and get a
> recent one (the bug 645081) to use a ARM microcontroller.

If you are interested in mentoring Lucas that would be great. ARMs are a
bit a different topic though...

> It's difficult to test without any real hardware, it would be really
> useful if a free CPU simulator that can be used with gdb is available.
> So only the JTAG part will really need some hardware.

Real hardware for Atmel is rather cheap. I even have some lying around
(pretty simple stuff, AtMega8 with SD-Card and serial comminucation, no
JTAG). Could send that to someone interested but we that would need some
SMD soldering to put together.

Still, a CPU simulator would be nice, I think one exists.

> The project manager uses autotools and I'm not sure it's really usable
> for an AVR project. We have a makefile project backend but it's quite
> primitive.

It should work with autotools I think. Might be overkill but as long as
it is working transparently to the user, I wouldn't case.

> I don't think it's too short for 3 months, especially as you don't seem
> to have much experience in C. It's not that difficult but it takes time.
> Perhaps it's possible to write such plugin in Python but I don't know if
> the bindings are good enough.

Python bindings have to be tested. There is introspection but it might
be incomplete. I think there are some issues with implementing
interfaces.

Regards,
Johannes




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]