Topics

1

NXP^TM M522XX, KINETIS and i.MX RT / 52259 EVB UART interrupt

« on: February 23, 2011, 10:20:23 PM »

Hi, I'm using the uTasker 1.4 project for a 52259 EVB board. After some time with the simulator, and successfully trying most of the proyect features, I decided to start with the actual target board. The question is about UART interrupts not being generated and how to debug this problem.

Using CW, I tried setting a breakpoint in  _SCI1_Interrupt but nothing happens when the character is received, however the breakpoint is hit every 10 seconds when the Async routine I wrote is scheduled, and  I just get two bytes from the UART using fn. The rest of the information is lost.

Transmission works fine, every time I send out a byte the breakpoint is hit and I see the data at the hyperterm at 9600baud. I also tried UART0 and UART2 with similar results.


I'm sure I'm missing something, but I can't figure it out, any help is greatly appreciated.

Elio Mussini

2

µTasker general / 83640 PHY

« on: May 19, 2010, 10:25:11 PM »

Hi, we have built our design based on the 52259EVB from Freescale, but unfortunately we can not get the 83640 PHY from National to report ethernet link. This problem is probably not realted to uTasker, but any help would be appreciated.

We have built three prototypes with similar results:

a. No ethernet link at all in 100Mb mode.
b. If we force 10Mb mode by writing to the 0x0 register in the PHY and force the PC's network card to 10BaseT, the pc reports link, but our design doesnt.
c. We checked straps, reset and clock (25mhz) to be ok in the 83640.
d. We compared waveforms in our design and in the EBV and found that TX_CLK and RX_CLK signals in the 83640 are 50mhz with lots of jitter instead of the 25 Mhz required for the part to run in 100Mb mode. Also in 10Mb mode, frequency is 5Mhz instead of 2.5Mhz
e. The normal Link pulse sent every 16ms is 50ns instead of 100.
f. We compared all the 83640 registers in our design with the registers in a running EBV board, and the contents are identical!

We tried several prototypes with and without the 82259  installed and observed similar results. We were wondering if anybody designed based on the 82259 EVB board and had similar problems, or maybe can suggest an approach for debugging this problem.

Thanks for your time

Elio Mussini

3

NXP^TM M522XX, KINETIS and i.MX RT / FTP and the simulator

« on: November 25, 2009, 05:43:05 AM »

Hello all, I'm new to uTasker. I received the uTasker package today, and started testing with the simulator target. This maybe a simple question, but using the DOS batch file to FTP the demo pages to the simulator, I noticed that the DOS FTP client connects fine, but when requesting the files directory from the simultor I get an access violation in FTP.C (line702). I checked the ptrFiles and it seems corrupted. The interesting thing is that I started playing with FTP.c and changed:

 #define user_files_are_in_internal_flash 1
 to
 #define user_files_are_in_internal_flash 0

After recompiling, the FTP client connected fine and uploaded all the pages with no problems. Also the simulator started serving the web pages properly. Please help me understand this behavior. Thanks in advance.


Elio