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

Pages: 1 [2]
16
utFAT / Re: SD Card using demo file print command limited to 4096 byte files
« on: July 05, 2010, 08:16:30 PM »
Mark-

I applied all the patches (except 7a because it would not compile).  

With he changes, even the f430_320x240_24.bmp cannot print without the read errors.  utasker320x240.bmp runs about 1/2 way through before the read error happens.



I added an extra command to the disk commands called view (DO_VIEW_FILE) which works pretty well except for the read errors.

I'm just adding a view file command to the print file command in debug.c


                 if (DO_VIEW_FILE == ucType) {                     // {kevin 1}
                  fnDisplayBitmap(ucTemp, utFile.usLastReadWriteLength);   // {kevin 1} display bmp on tft
               }                                          // {kevin 1}
               else {                                       // {kevin 1}
                  for (iLoop = 0; iLoop < utFile.usLastReadWriteLength; iLoop++) {
                     if ((ucTemp[iLoop] < 0x0a) || (ucTemp[iLoop] > 'z')) {
                        ucTemp[iLoop] = '.';                         // non-printable characters replaced
                     }
                  }
                       fnWrite(DebugHandle, ucTemp, utFile.usLastReadWriteLength); // print the read data buffer
               }                                          // {kevin 1}

17
utFAT / Re: utFAT Patch List
« on: July 05, 2010, 06:34:19 PM »
Mark-

When I add #7  (first part) above, I get the following

c:\documents and settings\kevin\my documents\downloads\development\utasker\utaskerv1.4_lpc\utasker\utfat\mass_storage.c(2016) : error C2065: 'usDirFlags' : undeclared identifier
c:\documents and settings\kevin\my documents\downloads\development\utasker\utaskerv1.4_lpc\utasker\utfat\mass_storage.c(2016) : error C2065: 'UTDIR_SET_START' : undeclared identifier
c:\documents and settings\kevin\my documents\downloads\development\utasker\utaskerv1.4_lpc\utasker\utfat\mass_storage.c(2017) : error C2065: 'DirStart' : undeclared identifier
c:\documents and settings\kevin\my documents\downloads\development\utasker\utaskerv1.4_lpc\utasker\utfat\mass_storage.c(2017) : error C2065: 'DirStart' : undeclared identifier

18
utFAT / Re: SD Card using demo file print command limited to 4096 byte files
« on: July 05, 2010, 03:44:34 PM »
The READ error seems to be file/pattern dependent.

I can print f430_320x240_24.bmp  with no read error, but uTasker_320x240.bmp gives me a READ ERROR.

-Kevin

19
utFAT / Re: SD Card using demo file print command limited to 4096 byte files
« on: July 05, 2010, 03:36:25 PM »
Mark-

Sometimes it works, sometimes not.  

I went back and started with the original LPC V1.4

application.c - Seached for 192.168.0 and changed to local network address

config.h - un-comment #define LPC2478FBD208
config.h - comment //  #define LPC2378FBD144

http://www.utasker.com/forum/index.php?topic=690.msg4208#msg4208

1) In webInterface.c. At every conditional define for SUPPORT_GLCD  add also || defined SUPPORT_TFT  {4 locations if I counted correctly}

2) In app_user_files.h. At every conditional define for SUPPORT_GLCD add also || defined SUPPORT_TFT {2 locations}


FTP Put text files in D:/dir1.

Files over 4096 bytes give me "READ ERROR occured". in telnet (Uart not working in the simulator)

When compiling I get 2 warnings (no errors)


c:\documents and settings\kevin\my documents\downloads\development\utasker\utaskerv1.4_lpc\applications\aabv1-0\tft.c(406) : warning C4244: 'initializing' : conversion from 'unsigned long' to 'unsigned short', possible loss of data

c:\documents and settings\kevin\my documents\downloads\development\utasker\utaskerv1.4_lpc\utasker\utfat\mass_storage.c(2637) : warning C4146: unary minus operator applied to unsigned type, result still unsigned

-Kevin

20
utFAT / Re: SD Card using demo file print command limited to 4096 byte files
« on: July 01, 2010, 03:35:41 AM »
Mark-

I tried it out on a previous version (prior to adding my first task) and print works great with both uart and telnet.

Sorry, I should have checked first.

-Kevin

21
utFAT / Re: SD Card using demo file print command limited to 4096 byte files
« on: June 25, 2010, 05:33:45 PM »
I'm not sure if it will make a difference, but in the UART set to use COM1 and was monitoring it with TeraTerm using a USB serial port at com13 on the same PC.

22
utFAT / SD Card using demo file print command limited to 4096 byte files
« on: June 25, 2010, 02:57:42 AM »
I'm using the simulator with SD CARD support and the debug disk command print.

When I use the disk > print file command on a file larger than 4096 bytes,  I get "READ ERROR occured".  Is this a limit in uTFat or just in the debug print command?

-Kevin

23
µTasker general / Re: How to use the UART to get data and send data!
« on: June 16, 2010, 03:30:47 AM »
I ran through the "myfirsttask" tutorial and now everything seems to work.

24
µTasker general / Re: How to use the UART to get data and send data!
« on: June 16, 2010, 01:47:18 AM »
I cannot get the simulator uart to work on COM1 (only serial port) or COM13 (usb to serial dongle).

I've got COM1 connected through a null modem to COM13 and have tera term connected to COM13.

app_hw_lpc23xx.h is set up as follows:
Code: [Select]
#ifdef SERIAL_INTERFACE
    #define WELCOME_MESSAGE_UART   "\r\n\nHello, world... LPC2XXX\r\n"
    #define NUMBER_EXTERNAL_SERIAL 0                                     // {6}
    #define NUMBER_SERIAL   (UARTS_AVAILABLE)                            // the number of physical queues needed for serial interface(s)
    #define SIM_COM_EXTENDED                                             // COM ports defined from 1..255
    #define SERIAL_PORT_0   1                                            // if we open UART channel 0 we simulate using this COM port on the PC
    #define SERIAL_PORT_1   4                                            // if we open UART channel 1 we simulate using this COM port on the PC
    #define SERIAL_PORT_2   11                                           // if we open UART channel 2 we simulate using this COM port on the PC
    #define SERIAL_PORT_3   12                                           // if we open UART channel 3 we simulate using this COM port on the PC

    #ifdef OLIMEX_LPC_P2103
        #define DEMO_UART        0                                       // use UART 0
    #else
        #define DEMO_UART        0                                       // use UART 0
      //#define PPP_UART         1                                       // use UART 1 for PPP
    #endif
    #define MODBUS_UART_0        0
    #define MODBUS_UART_1        1
    #define MODBUS_UART_2        2
    #define MODBUS_UART_3        3
  //#define SUPPORT_HW_FLOW                                              // enable hardware flow control support
    #if defined LPC2103 || defined LPC2102 || defined LPC2101
        #define TX_BUFFER_SIZE   (512)                                   // the size of RS232 input and output buffers
        #define RX_BUFFER_SIZE   (32)
    #else
        #define TX_BUFFER_SIZE   (4*1024)                                // the size of RS232 input and output buffers
        #define RX_BUFFER_SIZE   (64)
    #endif

    #ifndef _LPC21XX
      //#define UART1_PORT2                                              // set for alternative pin uses - TXD1 and RXD1 on P2.0 and P2.1 rather than TXD1 on P0.15 and RXD1 on P0.16
      //#define UART2_PORT2                                              // TXD2 and RXD2 on P2.8 and P2.9 rather than TXD2 and RXD2 on P0.10 and P0.11
      //#define UART3_PORT0_HIGH                                         // TXD3 and RXD3 on P0.25 and P0.26 rather than TXD3 and RXD3 on P0.0 and P0.1
    #endif

    #ifdef SUPPORT_HW_FLOW                                               // define the ports for RTS/CTS use
        #define RTS_0_PORT_SET     FIO0SET
        #define RTS_0_PORT_CLR     FIO0CLR
        #define RTS_0_PIN          PORT0_BIT6
        #define RTS_0_PORT_DDR     FIO0DIR
        #define RTS_0_PORT         PORT_0

        #define RTS_1_PORT_SET     FIO0SET
        #define RTS_1_PORT_CLR     FIO0CLR
        #define RTS_1_PIN          PORT0_BIT7
        #define RTS_1_PORT_DDR     FIO0DIR
        #define RTS_1_PORT         PORT_0

        #define RTS_2_PORT_SET     FIO0SET
        #define RTS_2_PORT_CLR     FIO0CLR
        #define RTS_2_PIN          PORT0_BIT5
        #define RTS_2_PORT_DDR     FIO0DIR
        #define RTS_2_PORT         PORT_0

        #define RTS_3_PORT_SET     FIO0SET
        #define RTS_3_PORT_CLR     FIO0CLR
        #define RTS_3_PIN          PORT0_BIT4
        #define RTS_3_PORT_DDR     FIO0DIR
        #define RTS_3_PORT         PORT_0

        #define CTS_0_PIN          PORT2_BIT0                            // CTS can be defined on ports 0 and 2 due to their interrupt capabilitieds
        #define CTS_0_PORT_DDR     FIO2DIR
        #define CTS_0_PORT         PORT_2
        #define CTS_0_STATE        FIO2PIN
        #define CTS_0_INT_PRIORITY 5

        #define CTS_1_PIN          PORT2_BIT1
        #define CTS_1_PORT_DDR     FIO2DIR
        #define CTS_1_PORT         PORT_2
        #define CTS_1_STATE        FIO2PIN
        #define CTS_1_INT_PRIORITY 5

        #define CTS_2_PIN          PORT2_BIT2
        #define CTS_2_PORT_DDR     FIO2DIR
        #define CTS_2_PORT         PORT_2
        #define CTS_2_STATE        FIO2PIN
        #define CTS_2_INT_PRIORITY 5

        #define CTS_3_PIN          PORT2_BIT3
        #define CTS_3_PORT_DDR     FIO2DIR
        #define CTS_3_PORT         PORT_2
        #define CTS_3_STATE        FIO2PIN
        #define CTS_3_INT_PRIORITY 5
    #endif
Is there something else I have to do to enable the menu through the serial port when using the Simulator?

-Kevin

25
NXPTM LPC2XXX and LPC17XX / LPC2478-STK, SD Card and displaying images
« on: June 14, 2010, 08:49:06 PM »
I'm using only the simulator at this time, but the target is the LPC2478-STK.

1. I've enabled SDCARD_SUPPORT and re-named the HTTP default file BMenu.htm (I think that's the spelling), ftp'd the HTTP files to the SD-Card and the Web page is being served from the SD-CARD (with a few glitches like the refresh generating a 404 error).

2. Do you have a recommendation fro displaying .bmp files from the SD card?  I was trying to use place the file in the same sdram location as when the image is posted from the web page, but I can't find the routine that does it or the location of the buffer.  I thought I might try adding a uart menu command to load bmp's from the sd card.

3. When I want to run this on hardware, can I just use the SEL0, SCLK0, MISO0 and MOSI0 lines that appear to be unused on the LPC2478-STK?

Thanks
Kevin

26
LCD Graphics Library and Simulator / Re: uTasker graphic LCD support and graphic library
« on: June 09, 2010, 01:39:05 PM »
I'm not sure if this belongs in this topic or not...

Loadnig BMP files to the TFT can make the simulator and target non-responsive.

I first noticed it with the LPC2478-STK demo file and confirmed it with the simulator.

The two BMP files supply by utasker, work fine, but one I created myself from photoshop resulted in the issue:
File loads (HTTP POST) and displays with no problems, board and simulator appear to be working. From HTTP I can then browse to one of the original uTasker images, but once I hit upload, I loose all contact with the board and with the simulator.

I tracked it down to a two byte pad in my file utasker BMP length field is 0x36, 0x84, 0x03, 0x00 in my image it was 0x38, 0x84, 0x03, 0x00.  My file had two extra 0x00 bytes at the end of the file that were not needed.

When I changed the length field in my BMP to match the utasker BMP, everything worked well.  Removing the two extra bytes at the end of the file had no effect. 

It looks like loading a good BMP after the bad BMP causes the issue.  When I issue a break all from the debug window the stack frame value turns red as you can see in the screen capture:




-Kevin

27
NXPTM LPC2XXX and LPC17XX / Re: Issue with uTasker on Olimex LPC2478-STK
« on: June 08, 2010, 01:53:19 AM »
That worked!

Thanks Mark!

-Kevin

28
NXPTM LPC2XXX and LPC17XX / Re: Issue with uTasker on Olimex LPC2478-STK
« on: June 05, 2010, 10:28:05 PM »
Mark-

When I run the demo file from the website on the real HW, the TFT page displays a black box (prior to an image upload)

When I run the simulator, I get a broken link icon instead of the black box.

Do I have to enable external SDRAM in the source code?

I'm going to start from scratch and see what happens.

-Kevin

29
NXPTM LPC2XXX and LPC17XX / Re: Issue with uTasker on Olimex LPC2478-STK
« on: June 04, 2010, 02:12:43 AM »
Additional info, I get no errors but the following warning
TFT.c
c:\documents and settings\kevin\my documents\downloads\development\utasker\utaskerv1.4_lpc\applications\utaskerv1.4\tft.c(406) : warning C4244: 'initializing' : conversion from 'unsigned long' to 'unsigned short', possible loss of data


30
NXPTM LPC2XXX and LPC17XX / Re: Issue with uTasker on Olimex LPC2478-STK
« on: June 04, 2010, 01:38:25 AM »
I'm not sure if this is the same issue, but...

I'm running the simulator only for the LPC2478-STK and the TFT does not display images posted to it.
The broken link image is all that is displayed.  My guess is the BMP file is not being posted to the correct memory.

I commented out the following to get the web pages to display
//#define FTP_UTFAT                                      // allow FTP to work with utFAT
//#define HTTP_UTFAT                                    // allow HTTP to work with utFAT


#define SUPPORT_TFT is defined by default and builds with no errors

If I define define SUPPORT_GLCD, I get 576 errors
#define SUPPORT_GLCD
uTasker - 576 error(s), 10 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========


-Kevin



Pages: 1 [2]