Messages

1

NXP^TM LPC2XXX and LPC17XX / Re: Olimex LPC2378-STK - Another Ethernet problem

« on: July 25, 2009, 05:24:49 PM »

Hi!!!

Your message is very helpful - I have replace definition of EMAC_RxConsumeIndex and now uTasker works fine!!!

Thanks a lot!

Damian

2

NXP^TM LPC2XXX and LPC17XX / Re: Linux compilation

« on: July 25, 2009, 04:29:34 PM »

And of course this conditional syntax works (if You of course define earlier _LINUX_BUILD).

But I think that if ISO says, that between < > and  "" we should use / instead of \, it's better to replace this back slashes. In conditional syntax You have to earlier another configure point and everyone should do this before compilation.

Ok, now I will check this my first problem with uTasker. I hope that will be ok.

Damian

3

NXP^TM LPC2XXX and LPC17XX / Re: Linux compilation

« on: July 25, 2009, 04:18:04 PM »

Hi Mark!

I don't put this conditional syntax, but simply change \ to / and I have another problems:

1) In:
* Applications/uTaskerBoot/types.h
* Applications/uTaskerBoot/config.h
* Applications/uTaskerV1.3/types.h
* Applications/uTaskerV1.3/config.h

i have found "hardware" with first lower letter, but on file system You put this directory with first upper letter. I have changed it.

2) In sources I have found "watchdog.c" with again - with first lower letter. I have change it everywhere to first upper letter and it's looks like ok!

Compilation successful, now I try this conditional syntax for You.

Damian

4

NXP^TM LPC2XXX and LPC17XX / Re: Linux compilation

« on: July 25, 2009, 01:39:24 PM »

Bad news

Look at this:

ISO/IEC 9899:TC2

http://www.open-std.org/JTC1/SC22/WG14/www/docs/n1124.pdf

Point 6.4.7.3:

If the characters ', \, ", //, or /* occur in the sequence between the < and > delimiters, the behavior is undefined. Similarly, if the characters ', \, //, or /* occur in the sequence between the " delimiters, the behavior is undefined.69) A header name preprocessing token is recognized only within a #include preprocessing directive.

Now I will try to change \ to / in sources, but I think that would be great if all sources will be modified for the others. In "free time"

Damian

5

NXP^TM LPC2XXX and LPC17XX / Linux compilation

« on: July 23, 2009, 10:52:49 PM »

Hi...

I back from vacations and I plan to tire You once again.

At start - easy question I think.

Before I use CodeSourcery and Yagarto on Windows - and I don't have problems with compiling.

But now, I use Linux, and... could You tell me how can I compile uTasker?

Few hours I spent to find why 'make' gives me error. After that few hours I saw backslashes everywhere. I change \ to / in makefile, but then I saw many backslashes in C files, in include statements. And I don't know what to do with this :/

How, how I can do make all???

Greetings,
Damian

6

NXP^TM LPC2XXX and LPC17XX / Re: Olimex LPC2378-STK - Another Ethernet problem

« on: June 29, 2009, 08:16:06 PM »

Hi...

Now, I compile sources with Yagarto, and effect is the same Do You have any idea...?

Greetings,
Damian

7

NXP^TM LPC2XXX and LPC17XX / Re: Olimex LPC2378-STK - Another Ethernet problem

« on: June 29, 2009, 12:30:09 AM »

1) Download the reference for your Olimex board form here: http://www.utasker.com/SW_Demos.html
and see whether it behaves the same or not. This may help identify whether it is a HW problem, a build problem or a loading problem.

This works great.

2) If you monitor the activity with Wireshark are there any Ethernet frames being set by your board?

Yes. System sends packets in both cases. Look at this:

BAD HEX FILE (COMPILED MANUALLY):

Code: [Select]

> flash write_image erase C:/pp/Applications/uTaskerV1.3/GNU_LPC23XX/uTaskerV1.3.hex
auto erase enabled
Padding image section 0 with 2 bytes
wrote 53611 byte from file C:/pp/Applications/uTaskerV1.3/GNU_LPC23XX/uTaskerV1.3.hex in 6.234375s (8.397713 kb/s)

Wireshark:

1 0.000000 AsustekC_85:15:cc Broadcast ARP Who has 192.168.0.3?  Tell 192.168.0.2
2 5.390692 AsustekC_85:15:cc Broadcast ARP Who has 192.168.0.3?  Tell 192.168.0.2
3 10.890624 AsustekC_85:15:cc Broadcast ARP Who has 192.168.0.3?  Tell 192.168.0.2
4 16.390571 AsustekC_85:15:cc Broadcast ARP Who has 192.168.0.3?  Tell 192.168.0.2

CORRECT HEX FILE (DOWNLOADED):

Code: [Select]

> flash write_image erase c:/uTaskerV1.3_Olimex_LPC2378-STK.hex
auto erase enabled
Padding image section 0 with 4 bytes
Padding image section 1 with 8 bytes
Padding image section 2 with 2 bytes
wrote 50348 byte from file c:/uTaskerV1.3_Olimex_LPC2378-STK.hex in 6.062500s (8.110180 kb/s)

Wireshark:

21 110.929719 AsustekC_85:15:cc Broadcast ARP Who has 192.168.0.3?  Tell 192.168.0.2
22 110.929852 00:00:00_00:00:00 AsustekC_85:15:cc ARP 192.168.0.3 is at 00:00:00:00:00:00
23 110.929858 192.168.0.2 192.168.0.3 ICMP Echo (ping) request
24 110.930086 192.168.0.3 192.168.0.2 ICMP Echo (ping) reply
25 111.930131 192.168.0.2 192.168.0.3 ICMP Echo (ping) request
26 111.930330 192.168.0.3 192.168.0.2 ICMP Echo (ping) reply


3) Can you ping the board? Does it also crash when you try this or only when you try to browse?

Board crash on any TCP/IP request - ping and http also.

4) Can you say which compiler you are using?

Here You are:

Code: [Select]

C:\pp\Applications\uTaskerV1.3\GNU_LPC23XX>cs-make --version
GNU Make (Sourcery G++ Lite 2009q1-161) 3.81
Copyright (C) 2006  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

This program built for i686-pc-mingw32

My make command:

Code: [Select]

C:\pp\Applications\uTaskerV1.3\GNU_LPC23XX>cs-make -f make_uTaskerV1.3_GNU_LPC23XX


5) If it turns out to be a problem with the generated file you can send a hex file (for loading with FLASH MAGIC) so that it can be tried on our reference board.

It look's like that I have problem with compiler - HEX files sizes also are different (50348B, 53611B).

This is what I have done:

* Download uTaskerV1.3_beta-LPC.zip

* Download uTaskerV1.3_beta-LPC_3.zip

* Unpack uTaskerV1.3_beta-LPC.zip

* Unpack uTaskerV1.3_beta-LPC_3.zip

* Copy SP files to main files with overwrite option

* Select Olimex board in config.h

* Disable LCD SUPPORT in config.h

Should I do something else...?

But if original bin file works fine, there are a hope to run this sources on my board...

Greetings,
Damian

8

NXP^TM LPC2XXX and LPC17XX / Olimex LPC2378-STK - Another Ethernet problem

« on: June 28, 2009, 09:52:25 PM »

Hi All!

I have run uTasker on my Olimex board, but uTasker does not work correctly. I have read previous problems, but this advices not help me.

This is behaviour of my board:

* After power on led blinking, and ethernet led's also power on

* After TCP/IP request to board (via web browser from another computer) led stop blinking, and after few seconds (maybe 5 seconds) ethernet led's goes to power off

* After maybe one second later ethernet led's again goes power on, and led start blinking

* Web browser show Network timeout message

Could You help me?

I write elf file via ARM-USB-OCD and OpenOCD program (by command flash write_image erase uTaskerV1.3.elf elf

I hope someone maybe help me...

Greetings,
Damian

PS. Sorry for my english :/