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

Pages: 1 ... 4 5 [6] 7
76
NXPTM M522XX, KINETIS and i.MX RT / bare min app link errors
« on: September 12, 2007, 09:29:54 PM »
 Hi, I'm using the CW 6.3 light version and I see 2 projects in the list box on in the upper
left corner of the IDE when I open uTakserV1.3.mcp,  M52235EVB_ROM and bare_min_app_rom. I can build and run M52235EVB_ROM with no problem. When I select bar_min_app_rom I get the following link errors :

 Undefined  "main"  from start in startup.s
 Undefined  "mcf52235_init"  from start in startup.s


 I read through the docs but can't see anything I have to set.
 Any ideas ?

 Thanks,
 John

77
NXPTM M522XX, KINETIS and i.MX RT / Re: Email
« on: September 07, 2007, 04:55:20 PM »
Thanks Mark, I can send a test email ! Now I'm going to start
going through the documentation :)

 John


78
NXPTM M522XX, KINETIS and i.MX RT / Email
« on: September 06, 2007, 04:19:49 PM »
Hi,
 I defined SMTP and FTP in config.h and uploaded the web pages. The LAN config page
shows all the values I programmed in applications.c, except the DNS server is not shown.
In the admin page the fields initially display garbage, ie "?vX2" etc except password and
the SMTP server addr field is disabled. When I enter a value in the SMTP IP field and
save it, it display as garbage again.

 Thanks,
 John
 

79
NXPTM M522XX, KINETIS and i.MX RT / Re: Code warrior debug & Web Page
« on: September 06, 2007, 02:53:52 PM »
 Mark, thanks for the reply. I just got the simulator compiled and running under
windows and will start working on the project.
 BTW I download the free VS 8.0 express software from MS then had to copy
the Windows SDK inc and lib dirs that a co worker had installed on his machine in
my VS tree. I also had to add various libs to the linker command line in VS ie
user23.LIB etc.

 John
 

80
NXPTM M522XX, KINETIS and i.MX RT / Code warrior debug & Web Page
« on: September 04, 2007, 09:34:33 PM »
 Hi,
 I just installed the CodeWarrior 6.3 IDE and opened up the uTaskerV1.3.mcp
and set the target to M52235EVB_ROM. It compiles OK. I noticed that in order to
flash it into the M52233DEMO I had to use the FreeScale flash utilty. If I run this first
I am able to then use the CW debugger on the code. If I make a code change and try
to run it from CW, it displays the status like it's down loading 78K bytes etc, but when
it runs, it's running the previous code that was flashed in with the FreeScale utilty.
Is this a feature of the free 128K limit version of CW ?

 When I try to access a web page on the pcb I get a uTasker 404 error, page not found.
I access it with my IP address, ie 10.1.2.48. I tried accessing astats.htm, index.htm etc  with the same result. HTTP is set in config.h. Is there something else that must be set ?

Thanks,
 John


81
NXPTM M522XX, KINETIS and i.MX RT / Re: codeSourcery and SP5 code
« on: September 04, 2007, 06:26:01 PM »
Mark, my 30 day eval of CS ran out and they gave me no time line when they
would get the uTasker project compiled properly and the debugger running on the M52233DEMO pcb ,so I'm going to try the Code Warrior debugger.

 John

82
NXPTM M522XX, KINETIS and i.MX RT / Re: codeSourcery and SP5 code
« on: August 31, 2007, 03:48:51 PM »
Mark, I tried compiling the project using CS 4.2.23 and flashing it in with the
freeScale utilty and it didn't run. I notified CS of this. I'll give the CW 6.3 debugger a shot and see how it works.

 Thanks for the help,
 John

83
NXPTM M522XX, KINETIS and i.MX RT / Re: codeSourcery and SP5 code
« on: August 30, 2007, 07:23:06 PM »
Mark,
 I'm making some progress. I started clean and unziped the uTasker, SP4, then SP5
files. I commented out RTC_SUPPORT, disabled the WATCHDOG and set the default
network settings to use my network values  and set ethernet to use 10MZ instead of auto-neg. I downloaded the FreeScale CF flash utility and flashed in the code. When it
booted up LED1 was blinking at ~2.5hz rate, the ACT LED was blinking and the LNK LED was on. I was able to ping the address I coded in ! I think changing the auto-neg setting
got the network up.
 When I tried loading the elf into the CS 4.2.23 debugger it stopped immediately like
before with the same debug log. I sent the code to CS to see if they can figure out what is going on. Is there another USB debugger you would recommend using with this
project ?


 Thanks,
 John




84
NXPTM M522XX, KINETIS and i.MX RT / Re: codeSourcery and SP5 code
« on: August 29, 2007, 09:38:31 PM »
 I tried using the m52235evb-rom.ld from SP4 instead of the updated version for CS > 4.1.32 when I compiled with CS 4.1.32. The only difference is the updated version has a _region_array label at the end of the rom section. I still get the _start label warning regardless of which version I use. I never got the  _region_array error, even using the SP4 .ld file.

 John

85
NXPTM M522XX, KINETIS and i.MX RT / Re: codeSourcery and SP5 code
« on: August 29, 2007, 08:16:36 PM »
 I compared the map files produced by the 4.1.32 and 4.2.23 codeSourcery
packages searching for _start references and nothing looked obviously wrong, but
then I'm no expert here :)

86
NXPTM M522XX, KINETIS and i.MX RT / codeSourcery and SP5 code
« on: August 29, 2007, 07:55:46 PM »
 We've been working the last few days trying to get uTasker running on our
M52233DEMO pcb. Here's the results so far:

 Using codeSourcery 4.2.23 IDE to compile and debug

1) I had to modify the m52335evb-rom.ld file to include the _init and _fini lables
in order to compile without errors. When I ran it in the debugger it would
run for about 30 secs then stop the the following debug console message:

   Sourcery G++ Debug Sprite for ColdFire ELF (8/29/07 2:40 PM) (Suspended)   
      Thread
  • (Suspended: Signal 'SIGTRAP' received. Description: SIGTRAP.) <Stack is not available: Target is not responding (timed out).>   

   

 I modified the source code to disable the WATCHDOG and added the RTC interuppt
vector. I modified the makefile to use -O2 and -mcpu=52233. It still would not run.

I tried a uTaskerV1.3.elf file that was compiled with codeSourcery 4.1.32 and
I was able to run it where it hit a breakpoint in main(). I talked to codeSourcery and
they told me to download the 4.1.23 package and try it. I did this and compiled
the code with with following warnings :

..\..\..\Hardware\M5223X\M5223X.c: In function '_SCI1_Interrupt':
..\..\..\Hardware\M5223X\M5223X.c:1359: warning: unused variable 'ucDummy'
..\..\..\Hardware\M5223X\M5223X.c: At top level:
..\..\..\Hardware\M5223X\M5223X.c:354: warning: '_sw_wdog_timeout' defined but n
ot used
..\..\..\stack\http.c: In function 'fnHTTPListener':
..\..\..\stack\http.c:560: warning: 'ucPush' may be used uninitialized in this f
unction
..\..\..\stack\http.c:559: warning: 'Len' may be used uninitialized in this func
tion
c:/program files/codesourcery4.1.32/sourcery g++/bin/../lib/gcc/m68k-elf/4.1.1/.
./../../../m68k-elf/bin/ld.exe: warning: cannot find entry symbol _start; defaul
ting to 00000000

 I didn't get that last warnnig compiling under 4.2.23. When I tried debugging this elf
with the 4.2.23 IDE it would stop immediately with the following debug console message:

Sourcery G++ Debug Sprite for ColdFire ELF (8/29/07 2:50 PM) (Suspended)   
   Thread
  • (Suspended: Signal 'SIGTRAP' received. Description: Trace/breakpoint trap.)   

      1 <symbol is not available> 0x1fffffff   


 I'm stuck at this point.

 John


    
   
 

87
NXPTM M522XX, KINETIS and i.MX RT / Source tree question
« on: August 28, 2007, 07:07:00 PM »
 I'm starting to study the source files and see references like

 #ifdef _M5223x , #ifdef  _CODE_WARRIOR_CF etc in config.h and other files
but can't find where these labels are defined. Am I missing something ?

 John

88
NXPTM M522XX, KINETIS and i.MX RT / Re: codeSourcery 4.2-23 compile error
« on: August 28, 2007, 02:54:48 PM »
Mark, I modified app_hw_m5223x.h to disable the WATCHDOG and set a breakpoint in fnInitHW() that checks it but it never hit it. The Debugger runs the code for about 30 secs then enters the suspended state, with the msg

(Suspended: Signal 'SIGTRAP' received. Description: SIGTRAP.) <Stack is not available: Target is not responding (timed out).>   

 The debugger is telling me the target is "Timing out" after that point when I try to
restart it etc. Attached is the S record load . I am running this on a M52233DEMO board
with a P & E USB BDM


 Thanks,
 John

89
NXPTM M522XX, KINETIS and i.MX RT / Re: codeSourcery 4.2-23 compile error
« on: August 27, 2007, 09:41:45 PM »
 Mark,
 I tried debugging the code in codeSourcery after it compiled OK, but get the following error after about 30 secs running. No source code window pops up displaying where it's at in the code when the trap occurs. I did not modify any of the *.h files yet
and I'm just building uTasker without the bootloader at this point. Is that OK ?

 uTasker [C/C++ Local Application]   
   Sourcery G++ Debug Sprite for ColdFire ELF (8/27/07 4:29 PM) (Suspended)   
      Thread
  • (Suspended: Signal 'SIGTRAP' received. Description: SIGTRAP.) <Stack is not available: Target is not responding (timed out).>   

   m68k-elf-gdb (8/27/07 4:29 PM)   
   C:\Documents and Settings\jreynolds\CodeSourcery\uTasker\Applications\uTaskerV1.3\GNU_ColdFire\uTaskerV1.3.elf (8/27/07 4:29 PM)   
 

90
NXPTM M522XX, KINETIS and i.MX RT / Re: codeSourcery 4.2-23 compile error
« on: August 27, 2007, 06:38:40 PM »
Mark,
 I had to add the _init and _fini labels to m52235evb-rom.ld file as follows
to correct the problem

  . = ALIGN(0x4);
    __INIT_SECTION__ = . ;
   _init = . ;
    LONG (0x4e560000)   /* linkw %fp,#0 */
    *(.init)
    SHORT (0x4e5e)   /* unlk %fp */
    SHORT (0x4e75)   /* rts */

    . = ALIGN(0x4);
    __FINI_SECTION__ = . ;
    _fini = . ;
    LONG (0x4e560000)   /* linkw %fp,#0 */
    *(.fini)
    SHORT (0x4e5e)   /* unlk %fp */
    SHORT (0x4e75)   /* rts */



 John

Pages: 1 ... 4 5 [6] 7