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

Pages: 1 [2] 3
16
ATMELTM AT91SAM7X and AVR32 / Re: AVR32 bare-minimum boot loader
« on: September 18, 2010, 07:14:42 AM »
Do you have any documentation on these programs?
 - uTaskerFileCreate.exe
 - uTaskerCombine.exe

Also, I'm simply trying to load the boot loader and the appication firnware.  I just want to reset the board and have it execute the application code at 0x80000800. Initially, do I need to combine the boot loader and the initial firmware load together?  I'm using this linker file (lnkuc3a0512_bm.xcl), which has the following settitngs:

* The assumed memory layout is:
 *
 *   Start   Stop      Name   Type
 *   ----------   ----------   -----   --------------
 *   0x00000104   0x0000FFFF   SRAM   RAM 
 *   0x80000800   0x8007FFFF   FLASH   FLASH

And the boot loader has the following:
#define START_OF_FLASH 0x80000000

#elif defined (_HW_AVR32)                                           
    #define UTASKER_APP_START      (START_OF_FLASH + 0x800)             // internal FLASH solution
    #define UPLOAD_FILE_LOCATION   (unsigned char *)uFILE_START          // location in internal FLASH
    #define UTASK_APP_LENGTH       FILE_SYSTEM_SIZE                          // 128k



17
ATMELTM AT91SAM7X and AVR32 / Re: AVR32 bare-minimum boot loader
« on: September 18, 2010, 06:23:40 AM »
Never mind

18
ATMELTM AT91SAM7X and AVR32 / AVR32 bare-minimum boot loader
« on: September 18, 2010, 05:11:47 AM »
I'm trying to get the boot loader running.  What file extension is the convert program looking for?

uTaskerConvert.exe

19
ATMELTM AT91SAM7X and AVR32 / Re: FLASH_GRANULARITY
« on: September 12, 2010, 05:16:16 AM »
Thank you for the detailed explaination.

20
ATMELTM AT91SAM7X and AVR32 / Re: FLASH_GRANULARITY
« on: September 11, 2010, 04:17:00 PM »
Please explain this

   #define FLASH_LINE_SIZE              16                                             
 // lines made up of 16 words (theoretically 4 are necessary but it is more practical to have the size larger than a file header)


kenneth

21
ATMELTM AT91SAM7X and AVR32 / Re: FLASH_GRANULARITY
« on: September 10, 2010, 11:08:09 PM »
Thank you,

I understand now.

22
ATMELTM AT91SAM7X and AVR32 / FLASH_GRANULARITY
« on: September 10, 2010, 02:43:51 PM »
Hi Mark,

I'm trying to use an external SPI_FLASH (AT45DB642) with the PARAMETER_BLOCK_START located in tne internal flash. I'm using the EVK1105, which has an AVR32 (AT32UC3A0512). It seems that both device (AVR32 and AT45DB642) have different FLASH_GRANULARITY, (AVR32 = 512, AT45DB = 1024).  Will the different granularity cause a problem, and which one should I use for FLASH_GRANULARITY in the project.


Thanks

23
ATMELTM AT91SAM7X and AVR32 / Re: PWM Register Mapping
« on: July 28, 2010, 03:47:37 AM »
Thnak you, no problem

24
ATMELTM AT91SAM7X and AVR32 / PWM Register Mapping
« on: July 26, 2010, 01:43:26 PM »
Hi Mark,

I don't see the typical register mapping for the PWM module in AVR32.h.

i.e. #define PWM_ENA  *(volatile unsigned long*)(PWM_BLOCK + 0x04)

Am I overlooking something?

Thanks,
Kenneth

25
ATMELTM AT91SAM7X and AVR32 / EVK1100 LCD Support
« on: July 24, 2010, 08:53:46 AM »
Hi Mark,

It seems that your current release for AVR32 (1.4.3) doesn't support the EVK1100 LCD, which operates in SPI mode.  I just want to make sure you don't have any code before I begin writing a driver.


Thanks,
Kenneth

26
ATMELTM AT91SAM7X and AVR32 / EVK1105 PERIODIC Software Timer
« on: July 07, 2010, 12:07:36 PM »
Hi Mark,

I need a PERIODIC software timer.  Is there a way to set this up or should I just keep retriggering it?  Iguess the other option is to use a GLOBAL_HARDWARE_TIMER.



Thank you,
Kenneth

27
ATMELTM AT91SAM7X and AVR32 / USB Support for AVR32
« on: June 23, 2010, 03:44:44 AM »
When I enabled the USB_INTERFACE macro, it gave an error stating "USB_HW is undefined".
Does this USB stack supports the AVR32 mcu's?

Thank you
Kenneth

28
ATMELTM AT91SAM7X and AVR32 / uTaskerV1.4.3 AVR32 w/ EVK1105
« on: June 21, 2010, 06:57:32 AM »
Mark,

I'm using uTaskerV1.4.3 with IAR and a EVK1105.  It builds and downloads OK, but when I press the reset button LED0 flashes about 4 times and the LCD screen blinks.  The cycle repeat itself over and over.  I believe the board is resetting itself.  I tried it on 2 boards, and the results are the same.  I'm trying to run the default project ( no changes made,... just build and download).  Have you seen this before?  Any suggestions?

Thanks for any help

29
ATMELTM AT91SAM7X and AVR32 / Re: TCP (Closing Connection)
« on: December 09, 2009, 07:52:10 AM »
Hi Mark,

Thanks for the info.  I have another question regarding tracking the TCP states.  I noticed in fnTELNETListener, you track the states and set the the TCP_EVENT_ABORT: case back to the listening state.  Should I be tracking and assigning things likewise?



// Telnet client/server standard call back
//
static int fnTELNETListener(USOCKET Socket, unsigned char ucEvent, unsigned char *ucIp_Data, unsigned short usPortLen)
{

case TCP_EVENT_CONNECTED:                                            // TCP connection has been established
        TELNET_session->ucState = TELNET_STATE_CONNECTED;
        return (TELNET_session->fnApp(Socket, TCP_EVENT_CONNECTED, ucIp_Data, usPortLen));

    case TCP_EVENT_ABORT:
        fnTCP_Listen(Socket, TELNET_session->usTelnetPortNumber, ptrTELNET->usMaxWindow); // set back to listening state
        fnResetTelnetSession(TELNET_session);
        TELNET_session->fnApp(Socket, TCP_EVENT_ABORT, ucIp_Data, usPortLen);
        // fall through intentionally
    case TCP_EVENT_CLOSE:
        return (TELNET_session->fnApp(Socket, TCP_EVENT_CLOSE, ucIp_Data, usPortLen));    

    case TCP_EVENT_CLOSED:
        TELNET_session->fnApp(Socket, TCP_EVENT_CLOSED, ucIp_Data, usPortLen);
        fnResetTelnetSession(TELNET_session);
        fnTCP_Listen(Socket, TELNET_session->usTelnetPortNumber, ptrTELNET->usMaxWindow); // set TCP port back to listening state
        break;

30
ATMELTM AT91SAM7X and AVR32 / TCP (Closing Connection)
« on: December 08, 2009, 07:14:28 AM »
I have a SAM7X board operating as a CLIENT, which initiates communication with a server.  After receiving the desired data, I want to the SAM7X to initiates the close sequence.  How is this done?

Thanks

Pages: 1 [2] 3