Topics

1

NXP^TM M522XX, KINETIS and i.MX RT / SDCARD_SUPPORT manifest and utfat support

« on: October 12, 2010, 06:48:01 PM »

Hi Mark
It's me again, regarding debug messages I saw when connecting to telnet server ( "TIMEOUT!!!" and "No valid SD-card" )
I found that I had SDCARD_SUPPORT defined. After I commented it, the errors disappeared, obviusly.

What I want to ask is if that is the only manifest required to get FAT support, even if I will try a USB device, like a pen drive.

TIA

Regards
Marcelo

2

NXP^TM M522XX, KINETIS and i.MX RT / Telnet server on M52259DEMO board seems hanging

« on: October 11, 2010, 09:29:48 PM »

Hi Mark
Some weeks ago I asked you a related question. In these days, I could not establish a telnet connection to the board.
You adviced me to grow the heap, and I did it. Additionally, I limited the http sessions to one.
Now the connection is established ( as shown by Wireshark ), but nothing more happens: the client machine send the SYN, and the board answers SYN, ACK. But from that point nothing happens.
My heap is now 27 kb, from which some 4 kb are free; and I have 0 unused stack.
May be this stack depletion the reason the telnet server dont send the menu to the client?
Other TCP and IP funcionality is working OK: http, ftp, ping, and my own protocol.
Could you tell me what to do next?
TIA
Regards
Marcelo

3

NXP^TM M522XX, KINETIS and i.MX RT / Boot loader trouble

« on: September 17, 2010, 10:29:30 PM »

Hi Mark
I'm playing with the boot loader. I'm using uTasker 1.4, and compiling with CW 7.2 on a M52259DEMO board.
I followed all steps from the documentation, but it seems that the boot loader never pass control to the application.
I double checked that
1) The boot loader, when defined  _M5225X then #defines UTASKER_APP_START      0x1000 ( uTaskerBootLoader.c line 63 ) so
2) In the app project, the target M5225X_BM_ROM uses the M5225X_BOOT_APP_FLASH.lcf, and it has the following directives
MEMORY
{
    flash   (RX)   : ORIGIN = 0x00001000, LENGTH = 0x0003F000
   vectorram(RWX) : ORIGIN = 0x20000000, LENGTH = 0x00000400
   sram   (RWX)  : ORIGIN = 0x20000400, LENGTH = 0x00007C00       
   ipsbar  (RWX)  : ORIGIN = 0x40000000, LENGTH = 0x0
}

and is consistent with the boot loader #define
3) Also, I changed the uTaskerCombine command line in BM_Convert.bat so it takes into account the true address of the application.

After that, I flashed the bin combined result. It dont seems to work. The better test I have is to ping the board at its default IP address. Nothing happened.

Then, to try another way, I flashed at first the boot loader, then the application. This last step both ways: leaving the flash programmer alone, and telling it to "Restrict the address range" so it dont overwrite the boot loader.
All at no luck, the board never initializes the TCP stack.

Looking in uTaskerBootLoader.c for occurrences of UTASKER_APP_START, it seems that when defined _M5223X the macro is not acted upon, so no control transfer will occur.
How and where must be the code to control trasfer to happen?

TIA

Regards

Marcelo

4

NXP^TM M522XX, KINETIS and i.MX RT / NQ port behaviour differs between Simulator and Target Board

« on: August 28, 2010, 08:46:34 PM »

Hi Mark
I nearly completed my proof of concept ( RC, by now  )
All development was done in the simulator - great job !
Today I flashed it to M52259DEMO board; near all features are working as expected; the exceptions are
1) I'm testing input recognition using NQ port, bits 1 and 5, because they are wired to the board's switches. When in the simulator, I toggle any of them and the software can "read" the change. But when running in the board, it seems that the pushes on the switches are not recognized. What may be wrong, Mark?
2) I can ping the board, uploaded via ftp the html pages, and can connect with a browser, all exactly like in the simulator. But when trying to connect via telnet, after some little time the telnet client comes up with "Connection to host lost." message. Where  could I need to look?

TIA

Marcelo

5

µTasker general / memory exception storing parameters in flash

« on: July 08, 2010, 09:50:46 PM »

Hi Mark
I'm customizing the stored configuration parameters to my application's needs.
I extended the PARS structure/typedef with the necessary members, and also the webInterface logic to cope with them. All works fine, except when I do some changes and try to save the new parameter values, using the simulator.

The exception occurs at line 2395 of M5223X.c. The code there is as follows

   #ifdef _WINDOWS
    if (ulValue & ~(*(unsigned long*)ptrAdd)) {          // we check that we are not trying to program a bit from '0' to '1'
        *(unsigned char*)0 = 0;                                // this will fail so signal it when debugging
    }
    #endif

It's clear to me that the exception is intentional, because the application is trying to do an illegal operation. But the current demo code does not try to erase the flash prior to write the new conf, and I cannot find a suitable function to do that.
But the most intriguing thing is that I was playing some times with the conf before the customization attempt, without trouble.
Note: when I save the conf for the first time, all is OK, and checking the "flash file", it's as expected. The thing goes wrong when I try to save some new values, i.e, I'm trying to overwrite the flash. 

TIA
Regards
Marcelo

6

µTasker general / How to read/write the digital I/O

« on: June 06, 2010, 02:52:21 PM »

Hi all
I was searching the demo project ( V 1.4 ) for the 5225 demo board and cannot find the place where the led is toggled on/off, to learn by example.

Also, I would like to wake up a task whenever some input is present. How can I do that?

Thank you in advance

Regards

Marcelo

7

µTasker general / CW refuses to flash the uTasker demo

« on: May 31, 2010, 03:08:05 PM »

I'm trying to program a Freescale's M52259DEMO board.
After some pitfalls with the Freescale / MQX code base, I decided to get uTasker a new and deep look.
I liked what I learned from the docs, so I tried it. First, of course, with the simulator.
When I tried to burn the demo project to the board from the Code Warrior IDE, CW complained regarding USB connection error.
And it was six times in a row, including a Windows restart.

I spent some hours searching the net regarding sudden USB errors, until I decided to test the port I was using with a pen drive, which of course went ok.
Again loaded CW and tried to burn the flash, two times, at no luck.
Suspecting some fooling, in the same CW session I closed the uTasker project, and opened another of mine, which uses the MQX code base.
Hard to believe, CW flashed it without any comment. It's obvious to me, that CW is not "seeing" some MQX signature, and refuses to flash, but pretending an error, not telling the truth.

My question is now: how to burn an uTasker project?