Topics

1

ATMEL^TM AT91SAM7X and AVR32 / uTasker as an AVR32 Studio project?

« on: September 08, 2009, 12:12:44 PM »

The simulator is great, but I think it is overly optimistic to think that I wouldn't need the JTAG ICE at all when the hardware arrives and I need to get all the peripherals working. Has anybody converted the AVR32 package to an AVR32 Studio project yet? I could do that myself (and I will, if I need to), but if I can save a day(?) of work by asking, I will be very grateful.

2

µTasker general / Simulating custom peripherals?

« on: September 08, 2009, 12:00:46 PM »

As noted in the filesystem replacement post, I am leaning towards picking Utasker for my next project, one of the main reasons being the really great simulator. However, the simulator obviously doesn't know about the peripherals in my project. How could I expand the simulator myself?

It is trivial to write something like

void AccessCustomDevice(...)
{
#ifdef _WINDOWS
  AccessSimulatedCustomDevice(...)
#else
  AccessRealCustomDevice(...)
#endif
}
The issue is how to write the AccessSimulatedCustomDevice(). It is up to me to decide how accurate simulation code I want to write (probably not very ), but how would I integrate that to the rest of the simulator? I am using Visual C++, and that is about the level I know how to do windows programming. However, the simulator isn't really a Visual C++ application. It does run under it and gives us a nice development environment, but there are no forms or other widgets. But maybe it is easily expandable? Am I hoping too much?

3

µTasker general / Replacement for uFileSystem?

« on: September 08, 2009, 11:47:25 AM »

Hi,

I am evaluating the uTasker for my next project, and so far, it looks like a winner. However, there are couple of issues I need to find or create. The application needs a filesystem with long filenames (at least 8.3, preferably true long) and directory structure; there is no way around this. There are filesystem libraries around (FAT and non-FAT). So, assuming the existence of a working filesystem library, could the uTasker system be made to work with that? Has anybody done that, and maybe could give me some guidance? If Mark is working with something like that, could you tell us about it? (I would hate to do a lot of work and next week, learn about an official, supported implementation of same...)

The web server, FTP and (if I decide it is needed) USB mass storage parts are likely those that need most work. I guess I could have an SPI chip in the hardware (not done yet) or modify the imaginary filesystem code to put aside a block for uFileSystem for parameter system and firmware updates. What else do I need to have a look at?

Thank you for your input!