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 - phomann

Pages: 1 [2] 3 4
16
µ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.

17
Luminary Micro TM LM3SXXXX / Re: Creating a 25KHz interrupt
« on: May 07, 2010, 06:46:36 AM »
Hi Mark,

It is working as expected on the target. Thanks for the help.

Cheers,

Peter.

18
Luminary Micro TM LM3SXXXX / Re: Creating a 25KHz interrupt
« on: May 06, 2010, 06:12:58 AM »
Hi Mark,

Thanks for all of that. I think I'll setup another timer for my interrupt. I don't really need to worry about the timulator side of things.

Cheers,

Peter.

19
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.

20
Luminary Micro TM LM3SXXXX / Re: Problem uploading new firmware.
« on: April 06, 2010, 08:17:48 AM »
Hi Mark,

I found the problem. :) :):)

I had installed a compression file called Stuffit. It changed the .bin file application type to 'Stuffit'. Therefore the firmware file was rejected as the applicationtype sent to utasker was stuffit.

It's great the way some companies decide that their application is so important that they have the right to change application types. NOT.


It does identify an problem that could occur with my customers. I'm thinking of changing the file extension of my firmware upgrade files to something unique.

Not sure how to find a unique 3 character extension though. Maybe there is a register or list some where.

Cheers,

Peter.


21
Luminary Micro TM LM3SXXXX / Re: Problem uploading new firmware.
« on: April 06, 2010, 07:28:16 AM »
Hi Mark,

I have used the simulator as you suggested and it is rejecting the data. basically, when it gets to the line( around 750) in http.c ;

Code: [Select]
if (EXPECTING_DATA & header_search_state.ucState)
It fails because header_search_state.ucState is 0x67 and EXPECTING_DATA is 0x02

By looking at the state machine and breaking on the switch statement, the states appear to go;

switch state  (ucEvent         header_search_state.ucState
-------------------------------------------------------------------------       
BOUNDARY_FOUND                              0x03
CONTENT_LENGTH_FOUND                  0x41
FIRST_BOUNDARY_FOUND                   0x45
CONTENT_TYPE_FOUND                      0x65
FIRST_BOUNDARY_FOUND                   0x67
-------------------------------------------------------------------------       


fnHandleWeb(CAN_POST_BEGIN, 0, http_session) is then called and returns 0
The line
Code: [Select]
if (EXPECTING_DATA & header_search_state.ucState) is then executed. It is false so the line
Code: [Select]
http_session->ucState = HTTP_STATE_DUMPING_DATA; is executed and the file is not stored.

Does the above give an insight into why it is failing?


Cheers,

Peter.


22
Luminary Micro TM LM3SXXXX / Re: Problem uploading new firmware.
« on: April 03, 2010, 01:09:02 PM »
Hi Mark,

Sorry, I missed your reply.

Yes, I had already changed the HTM file to;

   <form action=aS.bin enctype="multipart/form-data" method="post">

Funny thing is that it used to work. I have been playing around with webInterface.c as I'm saving text to a file that is entered via a testarea web object using post.

Is it possible that I've interfered with the post  processing of the firmware file?

Cheers,

Peter.


23
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?




24
µTasker general / Re: MCU Recommendations
« on: March 10, 2010, 04:54:29 AM »
Hi,

As I understand the Code Sourcery licences, they need to be renewed per annum. I purchased the personel licence a few years ago and it expired after 12 months. I forgot to read the fine print I guess.  Needless to say, I did not renew.

The good thing about uTasker, the need for an in-circuit debugger is greatly reduced as a lot can be debugged in the simulator.

Cheers,

Peter

25
Luminary Micro TM LM3SXXXX / Re: Overlapping Sectors when building.
« on: November 20, 2009, 05:09:23 AM »
Hi ,

Thanks for the replies. Yes, I've added in quite a bit of code , but was not sure if it was due to some of the sections being used for the first time and the errors showing up.

The .ld fine was not altered to cause it to occur. I was expecting that the assert checks for memory overflow would have fired if a segment was too large.

I'll try to remove some code and see what happens.

Thanks,


Peter.

26
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.

27
µTasker general / Re: http.c. Not parsing form posts correctly
« on: July 16, 2009, 08:28:34 AM »
Hi Mark,

The data I'm trying to transfer is ascii text. The web page has a 80x24 Text window that the test is entered into. I could also be dropped in there by cut and past from an editor etc.

I want to to be able to parse the file translate it and store it in the file system. I also want to be able to take the data from the file reverse translate it and display it in the text window as well.

I'm not sure that the file transfer is what I'm after.

Is the 80x24 text window treated as a large parameter?

As to the parsing of the data, it is done 1 character at a time.

Cheers,

Peter.

28
µTasker general / Re: http.c. Not parsing form posts correctly
« on: July 16, 2009, 05:55:51 AM »
Hi Mark,

Thanks for the reply. I'll let you know how I get om.

Cheers,

Peter.

29
µTasker general / Re: http.c. Not parsing form posts correctly
« on: July 15, 2009, 05:04:36 AM »
Hi Thomas

I have implemented a version which solves the user name / password case. I will send you a new HTTP.c file (plus tcpip.h due to two new HTTP states). See the define PLAIN_TEXT_POST for the new bits which is activated locally in http.c. The define SUPPORT_POST_TEXT is not in fact used since the content type is not checked (the header has a different sequence in this case...) but I think that this should always be used together with SUPPORT_HTTP_POST_TO_APPLICATION because it probably doesn't make much sense to save to a file.

...
...

My tests on the simulator were good. There is however a restriction. The complete post must be received in one TCP frame. This will always be the case as long as the actual post data is not larger than about 1.2k in size - hopefully adequate for what you are doing (?).

...
...


Hi Mark,

I want to load some text data that is processed by my application, with the output stored into a file. Is it still the case that the maximum length of the text is still 1.2K? With the print to debug statement

Code: [Select]
        fnWrite(DebugHandle, (unsigned char *)ptrData, (QUEUE_TRANSFER)http_session->FileLength); // send to debug output

I only see the last 700 or so characters.

If so, how to I deal with it as my text data could be 10s of KB in length? I noticed that you provided a similar example for dealing with S records. Presumably, the size of the S-Records is greater than 1.2K


Cheers,

peter.

30
µTasker general / Re: uTasker Serial Loader
« on: May 12, 2009, 02:36:31 AM »
Hi Mark,

OK thanks for the heads up. I can work something out, even if it is a bit simpler than the standard encryption algorith.

Cheers,

Peter.

Pages: 1 [2] 3 4