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

Pages: [1]
1
NXPTM M522XX, KINETIS and i.MX RT / Re: FTP PROBLEM
« on: March 15, 2010, 08:05:33 PM »
Hi Mark,

I´ve done tests and all works correct now!

Thanks for the quick response!

Best Regards.

2
NXPTM M522XX, KINETIS and i.MX RT / Re: FTP PROBLEM
« on: March 11, 2010, 10:42:19 PM »
Hi Mark,

Once again I think have found some incorrect behavior on the FTP authentication.

The fnCheckPass() is parsing the user/pass and accepting substrings of the correct string. If the string is shorter then the reference, but have the same initial characters sequence  then will be parsed as valid.

I mean, if the correct password is foobar, an user can access using foo.

The same happens with the username.

3
µTasker general / Re: Bootloader and SPI FLASH
« on: December 03, 2009, 05:19:39 PM »
Hi Mark.

I was also trying to calculate this after I realize the difference in the flash sector size (564 rather than 256).

After that, I decided to use 256k flash block, that makes things easier.

Thanks for your help.

Best Regards.

4
µTasker general / Re: Bootloader and SPI FLASH
« on: December 03, 2009, 02:42:08 PM »
Hi Mark,

I have been done some tests here. I´ve changed the UPLOAD_FILE_LOCATION to uFILE_SYSTEM_END + 0x44000, but still doesn´t worked.

So i checked that when I upload a H.bin file, it is allocated in the address 0x86200 what gives uFILE_SYSTEM_END + 042200.

Changing again the UPLOAD_FILE_LOCATION to uFILE_SYSTEM_END + 042200, the upload process worked out.

I´m not sure on what causes this difference. Can you help me?

Thanks.
Regards.

5
NXPTM M522XX, KINETIS and i.MX RT / MAC address.
« on: December 01, 2009, 07:28:38 PM »
HI Mark,

I´m seeking a way to write the MAC address of one unit to his flash. I know that is been done in the parameters block, but i need to keep the MAC address even in the SW upload. In my tests, when I do a SW upload the mac changes to the default value.

Whats the better way to do that?

Thanks.
Best regards.

6
µTasker general / Re: Bootloader and SPI FLASH
« on: December 01, 2009, 01:28:46 PM »
Hi Mark,

We are using the AT45DB081 and following the configuration shown on uFileSystem in SPI FLASH document (http://www.utasker.com/docs/uTasker/uTaskerFileSystemSPI_FLASH_003.PDF).


We keep the parameters block on the end of internal flash, while the file system is on the SPI FLASH.

We believe that the problem is in the bootloader FILE_LOCATION. We understood that the upload_file_location points to the end of the file system rather then to a specific file.

How can us associate a FILE_LOCATION (address) with the initial char of the file. I´m mean: what will be the address of H.BIN??

My SPI FLASH configuration on uTasker

config.h:
Code: [Select]
#define SPI_FILE_SYSTEM
#define FLASH_FILE_SYSTEM
#define FILE_GRANULARITY (8*SPI_FLASH_BLOCK_LENGTH)
#define uFILE_SYSTEM_START (MEMORY_RANGE_POINTER)(uFILE_START)
#define uFILE_SYSTEM_END   (MEMORY_RANGE_POINTER)(uFILE_START + FILE_SYSTEM_SIZE)

app_hw_xx.h
Code: [Select]
#define FLASH_START_ADDRESS (0x00000000)
#define SIZE_OF_FLASH              (256*1024)

//#define SPI_FLASH_SST25                                          // use SST SPI FLASH rather than ATMEL
//#define SPI_FLASH_ST                                             // use ST FLASH rather than ATMEL
//#define SPI_DATA_FLASH                                           // FLASH type is data FLASH supporting sub-sectors (relevant for ST types)
#define SPI_FLASH_AT45DB081

#define SPI_FLASH_PAGE_LENGTH 264
#define SPI_FLASH_BLOCK_LENGTH (8*SPI_FLASH_PAGE_LENGTH)             // block size - a block can be deleted
#define SPI_FLASH_PAGES         (4*1024)                     // 1Meg part
#define SPI_DATA_FLASH_0_SIZE   (SPI_FLASH_PAGES*SPI_FLASH_PAGE_LENGTH)
#define SPI_FLASH_START        (FLASH_START_ADDRESS + SIZE_OF_FLASH)     // SPI FLASH starts immediately after FLASH

#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
#define SINGLE_FILE_SIZE (FILE_GRANULARITY)                      // each file a multiple of 16k (64k ST)
#define FILE_SYSTEM_SIZE (64*SINGLE_FILE_SIZE)
#define PARAMETER_BLOCK_SIZE    FLASH_GRANULARITY                    // use the smallest size for the device
#define PAR_BLOCK_SIZE  (2*PARAMETER_BLOCK_SIZE)

Boot definitions

config.h
Code: [Select]
#define SPI_SW_UPLOAD                                                  // new SW is situated in SPI FLASH {1}{2}
//#define SPI_FLASH_SST25                                                // {15} use SST SPI FLASH rather than ATMEL
//#define SPI_FLASH_ST                                                   // define that we are using ST FLASH rather than default ATMEL {9}
//#define SPI_DATA_FLASH

//#define USE_PARAMETER_BLOCK                                            // enable a parameter block for storing and retrieving non-volatile information
 #define USE_PAR_SWAP_BLOCK                                           // we support a backup block which can be restored if desired

//#define SPI_FILE_SYSTEM                                              // we have an external file system via SPI interface, rather than internal in FLASH
#define FLASH_FILE_SYSTEM                                            // we have an internal file system in FLASH

bootloader.c
Code: [Select]
#define UPLOAD_FILE_LOCATION   (uFILE_SYSTEM_END + 0)            // start of SPI FLASH {3}
#define UTASKER_APP_START      0x1000                            // external SPI FLASH solution requires two FLASH block for the boot code
#define UTASK_APP_LENGTH       (MAX_FILE_LENGTH)(0x18000 - UTASKER_APP_START)// 92k

Best Regards.

7
µTasker general / Bootloader and SPI FLASH
« on: November 30, 2009, 08:34:07 PM »
Hi,

I´m using the M522XX with an external flash. Now, i´m trying to upload a new software.

I do like usuall. I have send the H_Ipload.bin via FTP, turn off and on the boar, but the file is still in the FTP.

Can someone help me out with this configuration?.

thanks.

8
NXPTM M522XX, KINETIS and i.MX RT / FTP PROBLEM
« on: October 13, 2009, 10:50:09 PM »
I´m using the FTP on the uTasker v 1.4 and having some trouble.

I have enabled ACTIVE_FTP_LOGIN, for use the ftp only with authentication and changed the default user and password.

This works fine on IE, but on DOS ftp I was able to login with any USERNAME / PASS.

On Firefox, i was able to access with a blank password on the second try.

My configuration:

config.h

//#define ANONYMOUS_LOGIN                                      
#define FILE_NAMES_PER_FTP_FRAME    6                      
#define FTP_SOCKETS 2                                  
#define FTP_SUPPORTS_NAME_DISPLAY            
#define FTP_SUPPORTS_DELETE                      
#define FTP_SUPPORTS_DOWNLOAD                  
#define FTP_VERIFY_DATA_PORT                      
#define FTP_PASV_SUPPORT                            
#define DATA_PORT_TRIGGERS_CONTROL          
#define FTP_USER_LOGIN
#define FTP_WILDCARD_DEL                            
#define FTP_DATA_WINDOWS            2            
#ifdef INTERNAL_USER_FILES
#define FTP_DISPLAY_USER_FILES                
#define MAX_FILE_NAME_LENGTH    20          

I´m using CW 7.0.

Where is my mistake?

Thanks

9
NXPTM M522XX, KINETIS and i.MX RT / Re: uTasker V1.4 for M522XX now available
« on: September 03, 2009, 07:04:57 PM »
Hi Mark,

I´m already being using the uTasker 1.3 and now changing to 1.4. At the same time I´m changing from CodeWarrior 6.3 to 7.0.

When i make the uTasker project all works fine, but, with the bootloader project I am not able to get the .elf file to program the M5223 device. Can this be a misconfiguration or some problem in CodeWarrior or i´m missing something on uTasker?

Thanks

Pages: [1]