Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mhoneywill

Pages: 1 ... 5 6 [7] 8 9 ... 12
91
µTasker general / Re: uTasker Documentation
« on: April 30, 2010, 10:48:36 AM »
Hi Mark,

I understand the problems of trying to juggle product documentation against product development.

One of the tools we use for documentation is "Help and Manual" http://www.ec-software.com/ this allows us to product PDF, CHM and HTML help from one source. Not cheap but very good. Another product that may also do a similar job is  "Infohesive" http://www.2brightsparks.com/infohesive/features.html I have not tried this product but it looks interesting, and its a lot cheaper than help and manual.

I'm also trying to think if there is anyway some of us as users can help with the documentation effort, maybe some form of wiki. Where we can post code snippets etc. and fill in a documentation template that you have setup (function documentation for instance). You can just moderate / correct what we do, and also provide style guidelines. Again there is the extra issue of copying data out of the wiki and into other forms of offline help (PDF/CHM).

You need a combination wiki/Goggledocs type service which can save in an offline format (PDF and CHM), where the wiki can be browsed and searched in a read only mode by users but also edited by selected users. It would obviously need to be multi user allowing concurrent updates at the same time. Its a holy grail but I'm not sure what the solution is.

Cheers

Martin



92
µTasker general / uTasker Documentation
« on: April 20, 2010, 01:37:14 PM »
Hi Mark,

I've just been going through my downloaded copies of the utasker documentation to check my copies are uptodate. And I've got a couple of suggestions.

1. Is it possible to indicate the version number of each document within its description on the website i.e. V0.05 etc. To check which versions I had I have to download every document, open it and check the footer. Maybe you could incorporate the document version in the filename?

2. Is it possible to have one zip file with all the documentation, maybe this zip file could also group documents into different folders depending on topics like "tcpip" "file systems" etc.

I also noticed that the uTaskerTELNET.pdf document seems to have disappeared from the website.

Cheers

Martin

93
µTasker general / Re: Unexpected delay in uTasker simulator
« on: April 08, 2010, 02:46:00 PM »
Hi Andrija,

I'm no expert but I think this may be due to the system clock in windows and also the TICK_RESOLUTION set for uTasker. You might want to define a different TICK_RESOLUTION when running in windows.

This post may help a bit http://www.utasker.com/forum/index.php?topic=612.msg2662#msg2662

I did try to speed up the uTasker simulator by increasing the windows system tick but my initial tests did not seem to work. If you want I can dig out more info on what I tried.

Cheers

Martin

94
µTasker general / Support for AUTOIP
« on: March 25, 2010, 11:13:31 AM »
Hi Mark,

How difficult would it be for uTasker to support AUTOIP IP address allocation, when in DHCP mode. So if a DHCP server cannot be found the board will fall back to a Fixed IP address, if defined, or if the fixed IP address is defined as 0.0.0.0 an AUTOIP address in the range 169.254.x.x would be chosen.

LWIP has an AUTOIP module which might give some implementation idea's http://lwip.wikia.com/wiki/AUTOIP

Also the standard is defined here http://tools.ietf.org/html/rfc3927

The process looks fairly simple and seems to consist of using the ARP protocol to test and broadcast addresses. Combined with NETBIOS names this would make uTasker able to setup its own IP address very easily.

Cheers

Martin

95
µTasker general / Re: USB buffering problem?
« on: March 24, 2010, 08:45:44 AM »
Hi Dave,

I don't know anything about USB on embedded systems, but am aware of a driver stack built for the AVR called LUFA see http://www.fourwalledcubicle.com/LUFA.php

I've not looked at the code in detail so do not know how generic it is or how tightly it is integrated into the AVR, but it might be worth a look.

Cheers

Martin

96
NXPTM LPC2XXX and LPC17XX / Re: Crossworks: "LIBMEM RPC loader has not initialized correctly"
« on: March 23, 2010, 08:11:43 PM »
I would say that the wrong Flash loader has been selected for the project, I've come across a similar problem on the Luminary Micro uTasker project.

I'm using Rowley V1.7 at the moment, but I would try selecting a different loader for the project. Sometimes this is not defined in the utasker configurations because Mark uses IAR for most of his development.

I'm guessing because I do not have a copy of crossworks V2 here.

I'm assuming you have the correct Rowley support packages loaded for the processors you are using.

1. MAKE A COPY OF THE ROWLEY .HZP FILE so you can always recover what you have done
2. Open the Rowley Project and right click on the project in the project explorer and select properties
3. In properties select the "common" configuration so your changes apply to all configurations FLASH / RAM / DEBUG / RELEASE etc
4. In the properties look under "Target Option" at the "loader file path" and "loader file type" settings to see if they are correct, see what options you have.

Look at the above settings in a demo rowley project that does download and work and ensure you have the same settings selected for the "loader" in the utasker project.

Sorry I can't be more specific, good luck

Martin
 

97
µTasker general / Re: MCU Recommendations
« on: March 11, 2010, 11:02:24 AM »
I've just noticed that TI have introduced Luminary support to their CodeComposer IDE see http://www.luminarymicro.com/products/whats_new.html this is another compiler option $445.

This makes yet another Eclipse based IDE avaliable.

CodeComposer http://www.ti.com/ccstudio $445
CodeRed http://www.code-red-tech.com $1000 for Luminary - From $525 for LPC17xx
Yagarto http://www.yagarto.de $free
CodeSoucery http://www.codesourcery.com $400 or $200??

And probably more.

Also Steve I guess you know the newer Luminary LM3S9Bxx chips have CAN too.

Cheers

Martin


98
µTasker general / Re: Simulating custom peripherals?
« on: March 08, 2010, 05:37:12 PM »
Just Updating my previous post I've just found another good free serial port monitor called accessport see http://www.sudt.com/en/ap/index.html

I've attached a screen shot of a trace of a Modbus communication as an example



99
µTasker general / Re: MCU Recommendations
« on: March 07, 2010, 10:30:28 AM »
Hi Steve,

FYI Rowley use the CodeSourcery compiler, but have created there own library's. They do a personal licence for $150 but it can't be used for commercial development.

Looking at the CodeSourcery website it seems that their personal version $399 looks like it can be used for commercial development. Its important to be able to debug on the target hardware so it would be interesting to see how good the JTAG support is. Please feed back to about how well you get on.

One other IDE to look at is CodeRed http://www.code-red-tech.com/index.php

Note CAN is not currently supported in uTasker for the Luminary targets, I am planning to look at porting it but have had no time at the moment. You could quite easily use the CAN libraries supplied by Luminary in StellarisWare they just wouldn't be integrated within uTasker.

Cheers

Martin
 

100
µTasker general / Re: MCU Recommendations
« on: March 03, 2010, 03:03:32 PM »
Hi Steve,

We use the Luminary Micro processors with uTasker and have been very happy with them so far.

Advantages
- Built in PHY with Auto MDX (no more X over cables)
- Large family range with many features
- Good StellarisWare driver library showing you how to use the peripherals.
- Hardware Quadrature decoders on Chip
- UTasker support :-)

Disadvantages
- We have had some issues getting parts, but this was during the takeover by TI, so might be a short term thing

Marks comment about development tools is relevant, we use Rowley as our compiler www.rowley.co.uk good product but not cheap $1500 its still cheaper than the IAR and Keil compilers. You can also go the GNU route but its more difficult to debug on the Target that way.

Mark has commented that Luminary Micro support in uTasker is not as mature as Coldfire support, We have used IIC, UART, GPIO, Ethernet, H/W Timers (used in modbus module) and ADC support. And all seem to work.

Good luck which every way you go, The support from Mark on uTasker is VERY good so I think you will not have to many problems with that

Cheers

Martin

101
NXPTM LPC2XXX and LPC17XX / Re: MOD-SMB380 I2C evaluation on LPC2378-STK
« on: February 18, 2010, 08:19:11 AM »
Yes you want the C++ variant.

Cheers

Martin

102
ATMELTM AT91SAM7X and AVR32 / Re: on board Can interface
« on: February 17, 2010, 06:35:29 PM »
As will I

Martin

103
ATMELTM AT91SAM7X and AVR32 / Re: on board Can interface
« on: February 17, 2010, 01:42:15 PM »
I would be interested in doing the same for the Luminary Micro chips, so pointers would be useful

Regards

Martin

104
µTasker general / Re: Simulator and Win7
« on: January 18, 2010, 11:09:24 AM »
Hello Oellness,

Here are a few things I would try. I would try each in turn.

1. Ensure that you have Wireshark installed which will mean that winpcap is installed. uTasker uses winpcap to create a bridge to its virtual network. This is probably installed otherwise I think uTasker would not run correctly.

2. When Running the simulator ensure that you go to the menu bar and under the "LAN" option choose "Select working NIC", then using the drop down box choose the network adapter that is on the 192.168.166.xxx subnet. If this shows "No Device used for simulation" or the wrong network adapter, then you will need to stop the simulator and restart it. Because uTasker only checks this value on program startup.

3. Ensure that the Lan adapter that you are connecting to in uTasker (The one on your 192.168.166.xxx subnet), is actually plugged into something and shows a link light, winpcap seems to need this.
 
4. You may have some firewalls running that block communications, try disabling them.

For simulation work, I have installed the Microsft Loopback adapter and created my own virtual network for testing, you could do this and create a virtual subnet on 192.168.1.xxx for instance and change the uTasker address to be say 192.168.1.166. I use windowsXP and have not tried installing the Loopback adapter in windows7 see http://support.microsoft.com/default.aspx/kb/839013 for info on installing it in XP. It looks like you can do this in Windows7 too see http://www.windowsreference.com/windows-7/how-to-install-a-loopback-adapter-in-windows-7/

Lastly for simple testing you do not need to set the Gateway and DNS in utasker, this is only needed if uTasker needs to resolve NAMES etc. Its not needed for simple Ping tests.

Good Luck

Martin

105
Luminary Micro TM LM3SXXXX / Re: uTasker V1.4.2 LM3Sxxxx Release with utFAT file system
« on: January 13, 2010, 07:35:23 PM »
Hi Mark,

I've just noticed that the new build includes the file GLCD.C in Applications\uTaskerV1.4\ this looks like an older version of the same file in uTasker\uGLCDLIB\ and can be safely deleted. Its not referenced in the project.

Cheers

Martin

Pages: 1 ... 5 6 [7] 8 9 ... 12