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

Pages: 1 ... 24 25 [26] 27 28 ... 30
376
NXPTM M522XX, KINETIS and i.MX RT / Re: New Service Pack SP8 with USB support
« on: September 24, 2008, 12:26:16 PM »
Hi mark,
  With SP8 I am trying the ethernet module again, and noticed that Full Duplex led is not on. When I run my old application (prior to sp8) it comes on (the 100MB is on ok). I am using the same NETWORK_PARAMETERS on both projects.


static const NETWORK_PARAMETERS network_default = {
    (LAN_100M | FULL_DUPLEX | RX_FLOW_CONTROL),                 
    {0x00, 0xcf, 0x52, 0x23, 0x00, 0x00},                               
    { 192, 168, 0, 3 },                                                  // ucOurIP - our default IP address
    { 255, 255, 255, 0 },                                                // ucNetMask - Our default network mask
    { 192, 168, 0, 1 },                                                  // ucDefGW - Our default gateway
    { 192, 168, 0, 1 },                                                  // ucDNS_server - Our default DNS server
};

Neil

377
NXPTM M522XX, KINETIS and i.MX RT / Re: fresh project
« on: September 18, 2008, 05:16:48 PM »
Hi Mark,
  I have removed the USE_MAINTENANCE, and all the LED outputs, apart from the ethernet ones.

Can the below be removed? :
INIT_WATCHDOG_DISABLE() ;// ensure IRQ4 is an input
#define CONFIG_TEST_OUTPUT()       PORTTC |= PORT_TC_BIT3; DDRTC |= PORT_TC_BIT3; // {27}
#define TOGGLE_TEST_OUTPUT()       PORTTC ^= PORT_TC_BIT3;
WATCHDOG_DISABLE()// pull this input down to disable watchdog (enable debugging) {3}

Regards
Neil

378
NXPTM M522XX, KINETIS and i.MX RT / fresh project
« on: September 18, 2008, 09:27:37 AM »
Hi mark,
  I am about to start a fresh project (just for testing), on my own board. Is there any I/Os that are used (for demo and eval boards) in utasker that I have to be aware of,as  I use varoius pins on my own board.

Thanks
Neil

379
NXPTM M522XX, KINETIS and i.MX RT / Re: Extra Ethernet Port
« on: September 18, 2008, 09:24:56 AM »
Mark,
  Thanks for the reply. I thought it wouldnt be possible, but worth a try.

Neil

380
NXPTM M522XX, KINETIS and i.MX RT / Extra Ethernet Port
« on: September 17, 2008, 05:26:02 PM »
Hi mark,
  Is it possible to have 2 ethernet sockets on a board, paralled up, connected to the 5223x chip? This would save us having to put in a switch. Just not sure if this is possible, or we will get collision . One ethernet will be connected to another board, and, the other port will be connected to a local network.

Neil

381
µTasker general / Re: spi flash test failed
« on: September 17, 2008, 11:47:28 AM »
Hi Mike,
  I placed the command fnEraseFlashSector(TEST_DEVICE, 0); in front of the fnWriteBytesFlash(TEST_DEVICE, test_buffer1, SPI_FLASH_PAGE_LENGTH); command, and worked fine. 


I have set the utasker up so the parameter block is in Flash, and file system in SPI memory, I setup the following:

#define FLASH_FILE_SYSTEM
#define PARAMETER_BLOCK_START 0x3f000                            // {34} FLASH location at 2 parameter blocks short of end of internal FLASH
#define uFILE_START 0x40000                                      // immediately after internal FLASH

So does the command fnGetParsFile(..) read from the internal flash?

Thanks
Neil

382
µTasker general / spi flash test failed
« on: September 16, 2008, 09:57:17 PM »
Hi Mark,
  When checking the new SP8 project the fnTestSPIFLASH(..) returned 'FLASH TEST FAILED' . Looking at the code it failed on the code :
     fnWriteBytesFlash(TEST_DEVICE, test_buffer1, SPI_FLASH_PAGE_LENGTH);
    fnGetParsFile(TEST_DEVICE, test_buffer2, SPI_FLASH_PAGE_LENGTH);


To test the spi chip (only 1 on my board, dont have demo or eval) I added the following in the M52233X.c file:

void WriteToPage(unsigned long ulPageNumberOffset, volatile unsigned char *ucData)
{   
   fnSPI_command(WRITE_BUFFER_1, ulPageNumberOffset, ucData,SPI_FLASH_PAGE_LENGTH);
   fnSPI_command(ERASE_PROG_FROM_BUFFER_1, ulPageNumberOffset, ucData,SPI_FLASH_PAGE_LENGTH);
}

void ReadFromPage(unsigned long ulPageNumberOffset, volatile unsigned char *ucData)
{   
   fnSPI_command(CONTINUOUS_ARRAY_READ, ulPageNumberOffset << 9, ucData,SPI_FLASH_PAGE_LENGTH);
}

and within the fnTestSPIFLASH(..) I replaced the   fnWriteBytesFlash(..)and  fnGetParsFile(..) with:
    WriteToPage(2,test_buffer1) ;
   ReadFromPage(2,test_buffer2);

And worked fine.

Any ideas what can be the problem?

Neil

383
NXPTM M522XX, KINETIS and i.MX RT / Re: New Service Pack SP8 with USB support
« on: September 16, 2008, 08:39:05 PM »
Hi mark,
  You are right, my typo error.. Its been a long day..  :D

Thanks
Neil

384
NXPTM M522XX, KINETIS and i.MX RT / Re: New Service Pack SP8 with USB support
« on: September 16, 2008, 07:37:00 PM »
Hi Mark,
  Thanks for the reply.

I done the above, and now get the message:

Error   : function has no prototype
spi_flash_m5223x_atmel.h line 43       ucSPI_FLASH_Type[0] = fnCheckAT45dbxxx();                            // flag whether the SPI FLASH device is connected 

Error   : identifier 'fnCheckAT45dbxxx(...)' redeclared
was declared as: '__regabi int (...)'
now declared as: '__regabi unsigned char ()'
spi_flash_m5223x_atmel.h line 346   { 


Neil

385
NXPTM M522XX, KINETIS and i.MX RT / Re: New Service Pack SP8 with USB support
« on: September 16, 2008, 06:19:50 PM »
Hi Mark,
 Thanks for your help today, much appreciated  :)

I have copied the SP8 files over my current SP6. When I compile it it comes up with error that it cant find the following:

Error   : the file 'spi_flash_m5223x_sst25.h' cannot be opened
M5223X.c line 225               #include "spi_flash_m5223x_sst25.h"                          // {61} 
Error   : the file 'spi_flash_m5223x_sst25.h' cannot be opened
M5223X.c line 583           #include "spi_flash_m5223x_sst25.h"                              // {61} 
Error   : the file 'spi_flash_m5223x_sst25.h' cannot be opened
M5223X.c line 2195           #include "spi_flash_m5223x_sst25.h"                              // {61} 

I can see the files in the M5223X folder, and the path points to this , as well as other locations.

I also noticed the following is defined:
        #define SPI_FLASH_ST                                             // use ST FLASH rather than ATMEL
I couldnt find anything for atmel.

Neil

386
NXPTM M522XX, KINETIS and i.MX RT / Re: setting up for spi file system (but getting compiler errors)
« on: September 16, 2008, 03:06:15 PM »
Hi mark,
  Where do I find which SP I am using? I made sure I had both SPI_FILE_SYSTEM and FLASH_FILE_SYSTEM defined after I got the errors.

Neil

387
NXPTM M522XX, KINETIS and i.MX RT / setting up for spi file system (but getting compiler errors)
« on: September 16, 2008, 02:44:07 PM »
Hi,
  Im starting to use the SPI filesystem, and getting compiling errors. I made changes as discussed in the 'ufilesystem in SPI Flash' and got the following errors:

Error   : macro 'FILE_GRANULARITY' redefined
(included from:
 types.h:76
 config.h:414
 M5223X.c:65)
app_hw_m5223x.h line 68       #define FILE_GRANULARITY (1024)                                      // File made up of 1k byte FLASH blocks 

Error   : undefined identifier 'M95XXX_WRITE_ENABLE'
M5223X.c line 2310       static const unsigned char ucWriteEnable[] = {M95XXX_WRITE_ENABLE, TERMINATE_WRITE}; // enable write 

Error   : function has no prototype
M5223X.c line 2318           fnWaitWriteComplete();                                           // wait until free to write 

Error   : function has no prototype
M5223X.c line 2324           fnWriteBytesEEPROM(ptrEEPROM, 0, EEPROM_PAGE_SIZE);              // delete a page 

And quite a few more, but didnt list them here.

Neil

388
NXPTM M522XX, KINETIS and i.MX RT / cts and rts
« on: September 08, 2008, 02:33:46 PM »
Hi Mark,
  I am using the CTS and RTS on UART1 (com2) as digital pins, but whatever I do it doesnt make any difference. After the serial port gets setup, without hardware handshake , I then do the following:
 
 PUBPAR=0x5; //set tx and rx as primary functions and cts/rts as io
 DDRUB=0x4;  //set rts as output,cts as input
 PORTUB=0;//set rts pin to 0.

at this stage, I check the voltage level of the rts pin, and its high.
When I display the value of PORTUB, I get 4 indicating rts pin is high.
If I apply 3.3v to the cts pin, and also display PORTUB, I still get 4.

Any ideas what I am doing wrong? I have checked the pins and all are correct.

Neil

389
NXPTM M522XX, KINETIS and i.MX RT / flushing serial buffer
« on: September 08, 2008, 01:39:13 PM »
Hi mark,
  What is the best way to flush the serial buffer?

Neil

390
µTasker general / mono timer within serial task
« on: September 08, 2008, 12:24:49 PM »
Hi Mark,
  I have a serial task where a string is sent through a serial port, and expects a reply within 2 seconds. Within the task I send the string and start a timer as follows:
uTaskerMonoTimer( TASK_OWNSERIAL, (DELAY_LIMIT)(2*SEC), E_TIMER_TIMEOUT );// start monitor timer

If I get a reply within the 2 seconds, how do I stop the timer from trigering the task?

Neil

Pages: 1 ... 24 25 [26] 27 28 ... 30