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.


Topics - phomann

Pages: [1]
1
Luminary Micro TM LM3SXXXX / Responding to TI's Finder utility
« on: September 28, 2010, 08:03:54 AM »
Hi Mark,

I want my application to respond to TI's Finder application.

The Finder application is a utility that communicates via UDP (Port 23 I think which is normally the telnet port)

The purpose of Finder is to locate Stellaris  boards on the LAN, and display their MAC and IP address  so the user can see what IP address has been assigned by DHCP, etc.

The source code for the PC application is in the Stellarwise tool/finder directory. The source for the target boards is in;
utils/locator.c, and .h


The finder broadcasts a UDP message on port 23.  The target boards bind to port 23 setup to respond to any IP address.

Is it possible to setup a UDP listener that will receive the broadcast UDP packet?

Cheers,

Peter.




2
µTasker general / fnDebugChar()
« on: September 20, 2010, 12:41:27 AM »
Hi Mark,

Before I write my own, is there a fnDebugChar() function? I couldn't seem to find anything.

Cheers,

Peter.

3
Luminary Micro TM LM3SXXXX / Creating a 25KHz interrupt
« on: May 05, 2010, 05:47:01 AM »
Mi Mark,

I want to create a 25Khz ISR to use for various timing functions, including a tasks run time. Is there anything in uTasker to support this type of ISR?

If not, are there any issues I may need to look out for? Presumably, the simulator will not be able to simulate this type of functionality.

Cheers,

Peter.

4
Luminary Micro TM LM3SXXXX / Problem uploading new firmware.
« on: March 30, 2010, 07:08:30 AM »
Hi Mark,

I'm having trouble uploading new firmware via the admin web page. It used to work, so I'm wondering if I hit a limit somewhere?

I'm using the internal flash and don't have any external Flash.


I've changed;

 the resolution of the file resolution from 1K to 2K 

The types MAX_FILE_LENGTH and MAX_FILE_SYSTEM_OFFSET are unsigned long

UTASKER_APP_START  from 0x800 to 0x1000

UPLOAD_FILE_LOCATION from 0x28400 to 0x2b000  This corresponds with file 'a' location in a 2K block file system


The #define UTASK_APP_LENGTH is left at (MAX_FILE_LENGTH)(94 * 1024)  Is this an issue.

The size of my application a_Upload.bin  is 83kb


When I try to upluad the file via the web page I get the message 'Sorry but upload has failed.'

But, if I use ftp to upload the file and then press reset, the new application is programmed by the boot loader and it works correctly.

I'm presuming that the file is not being uploaded via the web page due to some limitation that is being checked.

Any idea as to what that may be?




5
Luminary Micro TM LM3SXXXX / Overlapping Sectors when building.
« on: November 19, 2009, 04:26:07 AM »
Hi,

Can anyone help out here. When I'm linking with GCC (Code Sorcery) I'm having trouble with overlapping sectors. Does anyone know how to fix this or what it means?

Code: [Select]
arm-none-eabi-gcc -mcpu=cortex-m3 -mlittle-endian -mthumb -Wall -Wstrict-prototypes -I../../uTaskerV1.4 -D _GNU -D _LM3SXXXX -g -Os -Wl,-Map=uTaskerV1.4.map --no-gc-sections -nostartfiles -TuTaskerLM3SXXXX.ld -o uTaskerV1.4.elf Build/application.o Build/debug.o Build/webInterface.o Build/KeyScan.o Build/CGLCD.o Build/GLCD.o Build/LCD.o Build/NetworkIndicator.o Build/usb_application.o Build/LM3SXXXX.o Build/MODBUS.o Build/modbus_app.o Build/eth_drv.o Build/Driver.o Build/uMalloc.o Build/uTasker.o Build/Tty_drv.o Build/iic_drv.o Build/USB_drv.o Build/uFile.o Build/watchdog.o Build/GlobalTimer.o Build/low_power.o Build/Ethernet.o Build/arp.o Build/dhcp.o Build/dns.o Build/ftp.o Build/http.o Build/icmp.o Build/ip_utils.o Build/ip.o Build/pop3.o Build/smtp.o Build/snmp.o Build/tcp.o Build/telnet.o Build/tftp.o Build/udp.o Build/webutils.o Build/NetBIOS.o Build/iap.o Build/io.o Build/lib.o Build/basic.o Build/DataMap.o Build/ModIP_app.o Build/Basic_app.o
c:/program files/codesourcery/sourcery g++ lite/bin/../lib/gcc/arm-none-eabi/4.2.3/../../../../arm-none-eabi/bin/ld.exe: section .rodata [00000004 -> 00003213] overlaps section .vectors [00000000 -> 00000007]
c:/program files/codesourcery/sourcery g++ lite/bin/../lib/gcc/arm-none-eabi/4.2.3/../../../../arm-none-eabi/bin/ld.exe: section .text [00000008 -> 000127eb] overlaps section .rodata [00000004 -> 00003213]
c:/program files/codesourcery/sourcery g++ lite/bin/../lib/gcc/arm-none-eabi/4.2.3/../../../../arm-none-eabi/bin/ld.exe: section .data [00003214 -> 000037ff] overlaps section .text [00000008 -> 000127eb]
c:/program files/codesourcery/sourcery g++ lite/bin/../lib/gcc/arm-none-eabi/4.2.3/../../../../arm-none-eabi/bin/ld.exe: uTaskerV1.4.elf: section .rodata lma 0x4 overlaps previous sections
c:/program files/codesourcery/sourcery g++ lite/bin/../lib/gcc/arm-none-eabi/4.2.3/../../../../arm-none-eabi/bin/ld.exe: uTaskerV1.4.elf: section .text lma 0x8 overlaps previous sections
collect2: ld returned 1 exit status
cs-make: *** [uTaskerV1.4.elf] Error 1

Cheers,

Peter.

6
µTasker general / Were to obtain Ethernet MAC addresses from?
« on: January 27, 2009, 07:16:29 AM »
Hi all,

Has anyone had experience with the Microchip MAC Address chips. I'm considering it as a possibility as I'm not sure of the cost of purchasing a block of MAC addresses.

The MicroChip component 24AA02E48 also has a 256 byte flash and an i2C interface. Has anyone used them with, or integrated them into uTasker?


Otherwise, what do others do for obtaining MAC addresses?

Cheers,


Peter.

7
Luminary Micro TM LM3SXXXX / uTasker Bootloader
« on: October 02, 2008, 07:45:48 AM »
Mi Mark,

I tried to build the Bootloader project using uVision and get the following errors:
Code: [Select]
Build target 'uTaskerBoot'
linking...
.\Objects\uTaskerBoot.axf: Error: L6320W: Ignoring --entry command. Cannot find argument 'Reset_Handler'.
.\Objects\uTaskerBoot.axf: Warning: L6320W: Ignoring --first command. Cannot find argument '__Vectors'.
Target not created

I presume that the addresses of these two need to be set up some where?

Cheers,

Peter.

8
Luminary Micro TM LM3SXXXX / System Tick Speed.
« on: September 30, 2008, 09:09:30 AM »
Hi Mark,

The example application uses a system tick of 50mS. It is my understanding that this should cause tasks to run 20 times per second. I tried halving this expecting the  watchdog task to toggle the LED at twice the speed, yet it seems to toggle slower.
When I changed the tick time to 10ms, the led toggled even slower. Am I missing something?  ???

Also, is it correct that with a tick of 50ms, the fastest a task can run is 200 times a second. In order to get decent response times over Ethernet. I want to set the tick time to 1ms, is this possible?

cheers,

Peter.

9
Luminary Micro TM LM3SXXXX / TCP simple example problems.
« on: September 19, 2008, 06:07:10 AM »
Hi Mark,

I'm using the LM3S6965 EK board with the Code Sourcery compiler (Or will be) and am trying to get the example shown in;
http://www.utasker.com/forum/index.php?topic=25.msg73#msg73

I've copied the uTasker project to a new project called TestIP and added the code in the above message to the application.c file. When I compile it, I get the fowwowing errors;

Code: [Select]
1>Compiling...
1>application.c
1>c:\utaskerv1.3_beta-lm3s\applications\testip\application.c(584) : error C2232: '->tTCP_Header' : left operand has 'struct' type, use '.'
1>c:\utaskerv1.3_beta-lm3s\applications\testip\application.c(584) : warning C4047: 'function' : 'unsigned char *' differs in levels of indirection from 'int'
1>c:\utaskerv1.3_beta-lm3s\applications\testip\application.c(584) : warning C4024: 'fnSendTCP' : different types for formal and actual parameter 2
1>c:\utaskerv1.3_beta-lm3s\applications\testip\application.c(584) : error C2198: 'fnSendTCP' : too few arguments for call

The code as inserted into application.c is identical as far as I can tell. and shown below. I presume that I am doing something wrong;

Code: [Select]
#define TEST_BUFFER_LENGTH 300
typedef struct stTCP_MESSAGE
{
    TCP_HEADER     tTCP_Header;     // reserve header space
    unsigned char   ucTCP_Message[TEST_BUFFER_LENGTH];
} TCP_MESSAGE;


static unsigned short usTestPort = 9999;


static int fnTestListener(USOCKET Socket, unsigned char ucEvent, unsigned char *ucIp_Data, unsigned short usPortLen)
{
   TCP_MESSAGE test_message;

    switch (ucEvent) {
    case TCP_EVENT_CONREQ:                                             
    case TCP_EVENT_CONNECTED:
    case TCP_EVENT_CLOSE:
    case TCP_EVENT_ACK:
    case TCP_EVENT_ARP_RESOLUTION_FAILED:
    case TCP_EVENT_PARTIAL_ACK:
        break;
    case TCP_EVENT_REGENERATE:
    case TCP_EVENT_DATA:
        if ((ucEvent == TCP_EVENT_REGENERATE) || (!uMemcmp((CHAR*)ucIp_Data, "TEST" , 4)))
{
            uStrcpy((CHAR*)test_message.ucTCP_Message, "Hi!!");
            if (fnSendTCP(Socket, (unsigned char *)&test_message->tTCP_Header, 4, TCP_FLAG_PUSH) > 0)
{
                return APP_SENT_DATA;
            }
        }
        break;
    case TCP_EVENT_ABORT:
    case TCP_EVENT_CLOSED:
{
        fnTCP_Listen(Socket, usTestPort, 0);                    // go back to listening state on next port number
        break;
        }
    }
    return APP_ACCEPT;
}


Cheers,

Peter






Pages: [1]