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

Pages: [1]
1
NXPTM LPC2XXX and LPC17XX / Re: LPC2366 Flash size wrong
« on: January 07, 2010, 11:12:38 AM »
Hi Mark and others
 Just to muddy the waters further, mark, you may need to consider the MCB2300 board in a slightly different light. 

You say (as do your defines) that this board has a 2378 chip.  My version 3 board
has a 100pin 2368 chip and a DP83848 Phy chip circa late 2006 according to the schematic! 

This may lead to some confusions when refering simply to MCB2300 board.

Good Luck

FOXY
Martin Fox

2
NXPTM LPC2XXX and LPC17XX / Re: Issues with First Steps
« on: January 03, 2010, 10:02:48 AM »
Thanks Mark I will work my way through it.

Btw,  I haven't used the #define OWN_TASK yet as it wasn't mentioned in the first steps guide but I notice in some other posts that other users are using it in their own code.  Should I be using it also or has it been superceeded by the other declarations in the example?

Regards

FOXY( Martin Fox)

3
NXPTM LPC2XXX and LPC17XX / Issues with First Steps
« on: January 02, 2010, 09:20:52 PM »
Hi

I am working through the User-Guide First Steps section with Olimex LPC-P2378 board and have some comments about progress so far.

1.   It would be useful to remind complete Newbies like me not to forget #include config.h   in the new2ly created task source file (in my case martin.c which I added to the project. Spent quite a long time working out the compiler errors.

2.  the fnDebugDec(ucCounter++,0,0); statement gives a compilation error (too many parameters) . On Checking the code in device.c it has indeed only 2 paraqmeters.  I guess the .pdf needs updating with the correct code sample.

3.  There seems to be a decrepency in the #define SERIAL_PORT_0  '3' in LPC in the .pf doc.  In app-hwxxxx.h file this define expects an integer 3 rather than a char '3'  not sure if this makes a difference.

4.  I finally got a good build in DEBUG mode for the simulator but could not find any instruction as to how to get the simulted serial port to perform with UART_0 going to COM 2 on my pc using
TeraTerm.  However I did get a TELNET connection to work (also from TeraTerm), so I had a go at building for the Hardware board with the following (seemingly ambiguous message back)

1>Performing Post-Build Event...
1>arm-none-eabi-gcc -march=armv4t -mlittle-endian -mthumb -mthumb-interwork -Wall -Wstrict-prototypes -I../../uTMartin-1 -D _GNU -D _LPC23XX -g -Os -Wl,-Map=uTMartin-1.map --no-gc-sections -nostartfiles -TuTaskerLPC23XX.ld -o uTMartin-1.elf Build/application.o Build/debug.o Build/webInterface.o Build/KeyScan.o Build/LCD.o Build/TFT.o Build/NetworkIndicator.o Build/startup_gnu.o Build/LPC23XX.o Build/GLCD.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/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/tcp.o Build/telnet.o Build/tftp.o Build/udp.o Build/webutils.o Build/NetBIOS.o
1>Build/LPC23XX.o:(.rodata+0x84): undefined reference to `fnMyFirstTask'
1>collect2: ld returned 1 exit status
1>cs-make: *** [uTMartin-1.elf] Error 1
1>Build log was saved at "file://c:\APPLICATIONS\uTASKER\uTaskerV1.4_LPC\Applications\utMartin-1\Simulator\uTasker___Win32_uTasker_LPC23XX_with_GNU_build\BuildLog.htm"
1>uTMartin-1 - 0 error(s), 0 warning(s)
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========

A subsequent download to the board resulted in the App running (Led Blinking) but no output on either the Serial or TELNET connections.

I guess it is because the standard 'make_uTMartin-1_GNU_LPC23XX file (a clone of the DemoProject) does not yet include my Martin.c Task file.  Some instructions for we Newbies (no previous experience with build-link-deploy chain) would be useful here.

Thanks in advance

FOXY (Martin Fox)
as I am not sure how/where/what to manually insert the necessary instructions into 

4
NXPTM LPC2XXX and LPC17XX / Re: Problem Building MCB2300 V3 board
« on: December 29, 2009, 10:02:53 PM »
Hi mark

yes, i've read that somewhere in your extensive documentation, then promptly forgotten it again!

Thanks again for your cool support.

Martin

5
NXPTM LPC2XXX and LPC17XX / Re: Problem Building MCB2300 V3 board
« on: December 29, 2009, 09:07:05 PM »
Thanks Mark

Rebuild did it and Simulation builds OK.  B....y VS.

However when simulating (correct build as it now shows the 2 row panel), the IP and MAC are showing those specified for my OLIMEX (other) project. IP is set up to a different value for MBC2300 and MAC should still be all zero as I haven't been onto the simulated web-server yet to change it.

best regards

FOXY   


6
NXPTM LPC2XXX and LPC17XX / Problem Building MCB2300 V3 board
« on: December 29, 2009, 08:28:48 PM »
Hi

I have 2 development boards.  
Olimex LPC-P7378 (No  LCD 144pin NXP-2378 chip)
Kiel MCB2300 V3 (2 Row LCD, NXP2368 100pin chip)

Tried 'getting started' on OLIMEX and it built fine for both DEBUG and GNU-Target.  Simulated and Ran fine in Hardware. UnDefined both SUPPORT_LCD and SUPPORT_GLCD since neither were appropriate for the hardware.

Tried the same with MCB2300 using a 'new' set of uTasker Files. changed to
#define LPC2368FBD100, #define KEIL_MCB2300, undefined SUPPORT_GLCD and defined SUPPORT_LCD.

Build (for DEBUG) failed  with


1>Linking...
1>LCD.obj : error LNK2019: unresolved external symbol _CollectCommand referenced in function __fnWriteDisplay
1>.\Debug/uTaskerV1-4.exe : fatal error LNK1120: 1 unresolved externals


I know Mark has tested MBC2300 but I don't know if it is the same version board (V3).

If I undefine SUPPORT_LCD it builds OK but of course looses a useful LCD panel.
Has anone come across this problem before.  If so is there a fix?

Being a total Newbie at VS, C and ARM7 I don't have sufficient confidence yet to go poking around in the innards of the code.

Thanks in advance

FOXY (Martin Fox)  

Pages: [1]