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

Pages: [1]
1
NXPTM M522XX, KINETIS and i.MX RT / Re: CS-error
« on: October 19, 2017, 12:54:06 AM »
I figured it out.  The default S-record length is 252.  I had changed it to a shorter length of 32 in the other working projects.  Using 32 in the new project took care of the CS-error condition.

2
NXPTM M522XX, KINETIS and i.MX RT / CS-error
« on: October 18, 2017, 10:56:38 PM »
Mark,

I'm getting CS-error when I attempt to use the serial loader with a program developed in CodeWarrior 10.6 for the MCF52223.  I've used this compiler and the serial loader for many projects, so this is surprising.  It is a new project though.  What triggers the CS-error, and do you have any ideas about what to check in the compiler/linker?

3
Mark,

Thanks.  I'm very close to getting this to work.  I can see with the CodeWarrior debugger than I'm initializing the interrupt vectors in SRAM at the start of my application.  The application crashes when I first enable interrupts.  Even though I set VBR to 0x20000000 in code, its value stays at 0x200001B4 according to the register view.  I can't force it through the debugger, either.  Maybe the debugger is interferring?

Thanks,

Rick

4
I should know this, but... if I put the vector table in SRAM, does CodeWarrior & Processor Expert initialize it or do I have to manage that?  I see 'copy ROM to RAM' code, but my SRAM vector table doesn't seem right.

Thanks,

Rick

5
Hi,

I'm adding the serial bootloader to my non-uTasker application (MCF52223, CodeWarrior + Processor Expert).  Everything appears to be set up right.  I can load the serial bootloader into flash, and I can load the application into flash using the bootloader.  If I inspect memory, I see the application is in flash.  If I single step into the bootloader, I can see it call start_application and find the vector to the right starting address in my application.  It appears to start the application.  I can step through, some of the start up code. but then I get an address error exception.  It appears to be trying to run code at 0x00000000.  The application link map looks OK.  What could this be?

Thanks,

Rick

6
µTasker general / Re: Boot loader for MCF52223
« on: June 22, 2009, 02:12:48 AM »
I'm finally getting around to this project.

I haven't found specific instructions for using the provided configurations for the MCF52223 or M52223EVB.  I've found some posts that suggest I need to use the M52235EVB ROM target but also enable the definition for _M5222X in config.h.  It also looks like I need to disable KIRIN3.  Like this:

From config.h

#ifndef __CONFIG__
#define __CONFIG__

#define MY_PROJECT_NAME     "uTasker Bootloader"

#define BOOT_LOADER                                                      // {4} this ensures that no unnecessary simulation support is required

#define uDisable_Interrupt  __disable_interrupt
#define uEnable_Interrupt   __enable_interrupt

#define TARGET_HW           "Bare-Minimum Boot"

//#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                                                 // FLASH type is data FLASH supporting sub-sectors (relevant for ST types) {9}

//#define KIRIN3                                                           // M5225X family - otherwise remove!

// Specific project builds
#ifndef _BOOT_LOADER_ASSEMBLER
    #ifdef _CODE_WARRIOR_CF
        #pragma const_strings on                                         // ensure strings are of const type
    #endif

    #ifdef _M5223X
      //#define _M5221X                                                  // USB family {10}
        #define _M5222X                                                  // USB family {10}
      //#define _M5225X                                                  // Ethernet/USB family {14}

        #define _MALLOC_ALIGN                                            // support malloc with align option since LAN memory should be on specific boundary
        #define TICK_RESOLUTION        50                                // 50 ms system time period - max possible with M5223X at 60MHz (with prescaler) PIT would be about 70s!



Is that right?  If so, the logic below seems to define the memory for the MCF52221, not the MCF52223.


            #ifndef _M5225X
                #define _M52221                                          // M52221 rather than M52223
            #endif
            #define PLL_OUTPUT_FREQ_INT    48000000                      // run at crystal frequency with no PLL
            #define OSCCLK                 48000000                      // 48 MHz oscillator / crystal input
            #define POST_DIV               1
            #if defined _M5225X                                          // {14}
                #define SIZE_OF_FLASH      (512*1024)                    // M52259 has 512k
                #define SIZE_OF_RAM        (64*1024)
            #elif defined _M52221
                #define SIZE_OF_FLASH      (128*1024)                    // M52221 has 128k
                #define SIZE_OF_RAM        (16*1024)
            #else
                #define SIZE_OF_FLASH      (256*1024)                    // M52223 has 256k
                #define SIZE_OF_RAM        (32*1024)               
            #endif


Hints and guidance to documentation appreciated!

Thanks,

Rick

7
µTasker general / Boot loader for MCF52223
« on: March 26, 2009, 05:11:35 PM »
I'm looking to add a serial port bootloader to a MCF52223 project.  Is uTasker a good choice for this, or would someone recommend alternatives?

Thanks,

Rick

Pages: [1]