Messages

106

utFAT / Re: utFAT - preliminary information

« on: December 13, 2009, 11:57:14 PM »

Mark,

uFat looks to be very interesting, I have a few of questions

1. Will it be possible to run a uFat with an SPI memory chip instead of an SD card? I'm interested because I would like to use a slightly more flexible file name scheme rather than relying on the first letter dictating the file location

2. Will uFat be able to support userfile collections stored as a single file in the uFat system?

3. Will uFat support similar commands to the uFileSystem making porting easier?

Cheers

Martin

107

Luminary Micro ^TM LM3SXXXX / Re: Simulator vs. GCC

« on: November 19, 2009, 08:46:00 PM »

If you can't stand Eclipse (Code red use it) Rowley are VERY good on eval licences, we evaluated for 3 or 4 months because I was dipping in and out of the project.
They also support a wide range of chips. Might be worth going the eval route with them and as its GCC based a switch to another IDE would be fairly easy. One point to note is that Marks builds for uTasker are based on Crossworks V1.7 and the new version is V2. I still use V1.7 as I'm mid project and don't have time to change, and I know a couple of things have changed see http://rowley.zendesk.com/forums/51134/entries/46164 which is the following comment. There may also be other minor changes.

Cheers

Martin


I used the "asm" keyword with the V1 version of CrossWorks but it no longer appears to work on V2. What should I do?

The asm keyword is a GNU C extension, the error is now occurring because CrossWorks V2 enables ANSI checking by default.

The solution is to either use the __asm__ keyword in place of the asm keyword or, alternatively, set the Compile > Enforce ANSI Checking project property to No to allow asm to work.

108

Luminary Micro ^TM LM3SXXXX / Re: Simulator vs. GCC

« on: November 19, 2009, 07:46:45 PM »

Just a comment, but Crossworks is $1500 for a comercial licence not $3000. One reason I went with Crossworks was that they had written their own libraries. This point is often missed when people compare GCC to IAR and Keil. Have you tried using the code red suite http://code-red-tech.com/index.php its also GCC based, but with their own libraries.

Cheers

Martin

109

Luminary Micro ^TM LM3SXXXX / Re: Simulator vs. GCC

« on: November 18, 2009, 07:45:45 PM »

Hi Paul,

Although I use GCC, I use Rowley crossworks, who have created their own libs.

Sorry for the short answer, I'm leaving the office

Martin

110

Luminary Micro ^TM LM3SXXXX / Re: Simulator vs. GCC

« on: November 18, 2009, 05:31:50 PM »

Hi Paul,

I hit this issue too, but Mark has implemented his own string functions which are very efficient and do not rely on printf/sprintf. The problem is that sprintf can be VERY hungry on memory. I would suggest you look at Marks string functions.

I presume you are using uTasker V1.4 because the string functions were rationalised in this version. This link documents the string functions
http://www.utasker.com/forum/index.php?topic=641.0

Also see http://www.utasker.com/forum/index.php?topic=571.0 and http://www.utasker.com/forum/index.php?topic=30.0

Hope this helps

Cheers

Martin

111

µTasker general / Re: How can get uTasker v1.4?

« on: November 05, 2009, 07:49:17 PM »

Hi,

What Mark means is that all Regestered users that have paid a licence fee will get the link to the version 1.4.

If you are interesting in evaluating uTasker go to this page http://www.utasker.com/Licensing/License.html

Cheers

Martin

112

LCD Graphics Library and Simulator / Re: uTasker graphic LCD support and graphic library

« on: November 01, 2009, 07:56:32 PM »

Hi paul,

I've been following your posts too, as I use the LM6965, LM1968 and uTasker in two different products. I've made the changes Mark suggested and can confirm the display wraps on the simulator, for the LM6965 EK.

Cheers

Martin

113

Luminary Micro ^TM LM3SXXXX / Re: demo bin file not working with LM3s6i965-rec board

« on: October 09, 2009, 07:55:02 AM »

Hi Suhas,

Make sure you are using the latest version of the Luminary Downloader, there were problems with earlier versions. I'm using build 776 of the Luminary downloader and that works for me.

see this posting http://www.utasker.com/forum/index.php?topic=567.0

I think thats your problem.

Cheers

Martin

114

Luminary Micro ^TM LM3SXXXX / Re: demo bin file not working with LM3s6i965-rec board

« on: October 08, 2009, 12:56:06 PM »

Hi Suhas,

Does the status light on the board flash, that means the code is running.

The display will not show anything as the demo was built with uTasker V1.3 which does not support graphics displays, V1.4 does though.

When you connect an Ethernet cable does the Link light light on your computer?

Is the network adapter on your computer that is connected to the LM3S6965 setup for an IP address of 192.168.0.x where x is any number that is not 3 which is the static IP address of the demo board. Note on Windows XP you can setup multiple IP addresses for a single Network adapter by going to the TCPIP properties and pressing the advanced button, then adding another IP address.

Once the IP address is setup on your PC, can you PING the card type PING 192.168.0.3 at a command prompt, do you get a reply?

Next if you try and browse to http://192.168.0.3 do you get an orange page with a 404 file not found message?

If this happens then try uploading the web pages that are avaliable on the uTasker download page (where you downloaded the demo).
I've attached those files to this email along with a batch file to upload them (From Mark) just unzip the attached file and run copy_all.bat

Once you've done the above, you can refresh the web page http://192.168.0.3 and you should see something.

Good luck with this and if the above doesn't work, please indicate the point your reached in the above instructions.

Cheers

Martin

115

µTasker general / Re: Cannot change the magic number

« on: October 07, 2009, 09:22:52 AM »

Hi Ewan,

I use the bootloader with the Luminary LM3S chips, so might be able to help. One thing that you do not make clear in your email is that, are you re-flashing the target with the new bootloader and application via JTAG. Every time you change the magic number you have to change the bootloader in the target, because it has this magic number hard coded into it. Are you just creating a "H_Upload_Enc.bin" file and expecting the old bootloader to load it? that will not work.

Cheers Martin

116

Luminary Micro ^TM LM3SXXXX / What is your recomended compiler for ARM processors

« on: September 25, 2009, 01:32:09 AM »

Hi Mark,

JUst out of interest which compiler to you think is the best for ARM development GCC (Rowley), IAR or Keil. Which in your experience produces the fastest most compact code. And also have you come across any significant bugs in any of them. I use Rowley at the moment but am thinking about wether to upgrade or switch compilers. Just today I've hit a problem where it looks like my code is compiling incorectly but this could just be optomisation screwing with the debugging.

Cheers

Martin

117

µTasker general / Re: Simulating custom peripherals?

« on: September 09, 2009, 11:00:23 AM »

Com0Com is brilliant I'm finding more and more uses for it.

I have permanently defined 3 serial port pairs on my computers (I use high numbers so I don't clash with anything)
COM100 <> COM110
COM101 <> COM111
COM102 <> COM112
And always connect my utasker projects to COM100, 101, 102 for Uarts 0,1,2

I've also used the terminal emulator Realterm http://realterm.sourceforge.net/ I'm using version V2.0.0.65 from here http://www.i2cchip.com/realterm/
Realterm has a bit of a clunky interface but the killer tool for me is that for a small donation you can get a spy driver that will allow you to spy on communications on a com port (Virtual or real). Another powerful tool to monitor serial port comms can be found here http://www.serial-port-monitor.com/

Lastly here's an interesting link showing how com0com or rather com2tcp can be used
http://logmett.com/forum/viewtopic.php?t=699

Have fun

Cheers

Martin

118

µTasker general / Re: Simulating custom peripherals?

« on: September 08, 2009, 03:25:22 PM »

Just my 2 cents.

I needed to simulate connection to an external serial LCD display from CrystalFontz, this was easy to do I just wrote a crystal Fontz emulator as another uTasker Project and compiled it down to an exe. I then used com0com http://com0com.sourceforge.net/ to connect my new device to uTasker.

As for simulating inputs I modded the utasker simulator slightly to allow PC keyboard input to be routed through to my application see this post
http://www.utasker.com/forum/index.php?topic=634.0

Cheers

Martin

119

µTasker general / Re: Replacement for uFileSystem?

« on: September 08, 2009, 12:09:40 PM »

Hi JuKu,

The 6LoWPAN project mentioned in the link below, uses the EFSL FAT library I believe so that might be worth looking at. I think they have integrated it with uTasker.

Also I know USB / FAT / SD is all on Marks to-do list.

Cheers

Martin

See this link http://www.utasker.com/forum/index.php?topic=615.0

120

MODBUS / Re: Simple Modbus Simulator

« on: September 08, 2009, 12:31:34 AM »

Thanks Mark,

I found that

static int fnMODBUSsimulator(int iType, MODBUS_RX_FUNCTION *modbus_rx_function)
{
    switch (iType) {
    case SERIAL_ROUTE_FROM_SLAVE:
        {
        unsigned char ucTest[7];                                         // the message to be sent must have the address at the start and 2 additional bytes space at the end for a check sum to be added. Do not use const data!
        ucTest[0] = modbus_rx_function->ucSourceAddress;                 // our address
        ucTest[1] = modbus_rx_function->ucFunctionCode;
        ucTest[2] = 2;
        ucTest[3] = 0;                 // our address
        ucTest[4] = modbus_rx_function->ucSourceAddress;                 // our address
        return (fnMODBUS_transmit(modbus_rx_function, ucTest, (sizeof(ucTest)))); // answer with pre-defined response
        }
    }
    return 0;
}

Did what I wanted (Note your example didn't quite work, its byte count was wrong and only returned 1 byte not 2).

All I had to do was define the slave to be a gateway as below      

(MODBUS_MODE_RTU | MODBUS_SERIAL_SLAVE | MODBUS_RS485_POSITIVE | MODBUS_SERIAL_GATEWAY),         // default to RTU mode as slave - serial port 0

Cheers

Martin