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

Pages: 1 2 [3] 4
31
µTasker general / Re: uTasker Serial Loader
« on: May 11, 2009, 06:51:52 AM »
Hi Mark,

Can the encryption program that is used for encrypting the ethernet uploadable firmware be used for the serial bootloader image? If so, can I use the decryption module in uTasker to decrypt the serial uploaded image.?

I understand that it would mean that the bootloader would be larger and may possibly have duplicate code in it. Maybe, the decryption  stuff could be in the serial boot loader, and the ethernet uploader could do a call to it for the decryption.

Without encryption I'm not sure many would want to provide images of their software.

Cheers,


Peter.


32
µTasker general / Re: uTasker Serial Loader
« on: May 10, 2009, 12:10:07 AM »
Hi Mark,

Thanks for that. Does the boot loader also include the encryption/decryption capability?

Cheers,


Peter.


33
µTasker general / Re: uTasker Serial Loader
« on: May 08, 2009, 04:49:43 AM »
Hi Mark,

That's great. I already have a use for it on the LM3 :)

Cheers,

Peter.

34
µTasker general / Re: static web pages or hard coded html
« on: April 08, 2009, 06:21:29 AM »
Hi Mark,

I too am very interested in being able to have web pages served from Program code. I'd be happy to do some testing on the LM3 port.  As to how to put the pages into code, there is a perl script in UIP called makefsdata that does it. It is in StellarisWare.  Luminary Micro also have a program in that tools directory C:\StellarisWare\tools\makefsfile that also does it.

As a stopgap, I'll use this to embed the web pages into code then on initialisation put then into the file system. At this stage I have enough code space to to that.

Cheers,

Peter.

35
µTasker general / Re: Were to obtain Ethernet MAC addresses from?
« on: January 28, 2009, 01:15:00 AM »
Hi Mark,

Thanks for the reply. It looks like purchasing a block of 4000 may be the way to go.

Cheers,


Peter.

36
µTasker general / Were to obtain Ethernet MAC addresses from?
« on: January 27, 2009, 07:16:29 AM »
Hi all,

Has anyone had experience with the Microchip MAC Address chips. I'm considering it as a possibility as I'm not sure of the cost of purchasing a block of MAC addresses.

The MicroChip component 24AA02E48 also has a 256 byte flash and an i2C interface. Has anyone used them with, or integrated them into uTasker?


Otherwise, what do others do for obtaining MAC addresses?

Cheers,


Peter.

37
Luminary Micro TM LM3SXXXX / Re: uTasker Bootloader
« on: October 06, 2008, 12:36:19 AM »
Hi mark,

I've sent the project to you as I can't see how to remove the 2 vaeiablel.

Cheers,

Peter.

38
Luminary Micro TM LM3SXXXX / Re: uTasker Bootloader
« on: October 05, 2008, 10:02:40 AM »
Hi Mark,

Did you manage to see if there is a missing file with the bootloader?

Cheers,

Peter

39
Luminary Micro TM LM3SXXXX / Re: System Tick Speed.
« on: October 03, 2008, 04:43:08 AM »
Hi Mark,

Thanks for that. I'll do what you suggest regarding the Timer Tick definition.

Cheers,

Peter.

40
Luminary Micro TM LM3SXXXX / Re: uTasker Bootloader
« on: October 03, 2008, 04:41:43 AM »
Hi Mark,

If you look in the standard Keil directory, C:\Keil\ARM\Startup\Luminary They have an assembly  startup file called Startup.s

its contents are below and in it are the missing vectors. None of the files in the C:\uTaskerV1.3_beta-LM3S\Hardware\LM3SXXXX directory or anywhere under the C:\uTaskerV1.3_beta-LM3S can I find a file that has the vector table.

Code: [Select]
; <<< Use Configuration Wizard in Context Menu >>>
;******************************************************************************
;
; Startup.s - Startup code for Stellaris.
;
; Copyright (c) 2006-2008 Luminary Micro, Inc.  All rights reserved.
;
; Software License Agreement
;
; Luminary Micro, Inc. (LMI) is supplying this software for use solely and
; exclusively on LMI's microcontroller products.
;
; The software is owned by LMI and/or its suppliers, and is protected under
; applicable copyright laws.  All rights are reserved.  You may not combine
; this software with "viral" open-source software in order to form a larger
; program.  Any use in violation of the foregoing restrictions may subject
; the user to criminal sanctions under applicable laws, as well as to civil
; liability for the breach of the terms and conditions of this license.
;
; THIS SOFTWARE IS PROVIDED "AS IS".  NO WARRANTIES, WHETHER EXPRESS, IMPLIED
; OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF
; MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE APPLY TO THIS SOFTWARE.
; LMI SHALL NOT, IN ANY CIRCUMSTANCES, BE LIABLE FOR SPECIAL, INCIDENTAL, OR
; CONSEQUENTIAL DAMAGES, FOR ANY REASON WHATSOEVER.
;
; This is part of revision 2523 of the Stellaris Peripheral Driver Library.
;
;******************************************************************************

;******************************************************************************
;
; <o> Stack Size (in Bytes) <0x0-0xFFFFFFFF:8>
;
;******************************************************************************
Stack   EQU     0x00000100

;******************************************************************************
;
; <o> Heap Size (in Bytes) <0x0-0xFFFFFFFF:8>
;
;******************************************************************************
Heap    EQU     0x00000000

;******************************************************************************
;
; Allocate space for the stack.
;
;******************************************************************************
        AREA    STACK, NOINIT, READWRITE, ALIGN=3
StackMem
        SPACE   Stack
__initial_sp

;******************************************************************************
;
; Allocate space for the heap.
;
;******************************************************************************
        AREA    HEAP, NOINIT, READWRITE, ALIGN=3
__heap_base
HeapMem
        SPACE   Heap
__heap_limit

;******************************************************************************
;
; Indicate that the code in this file preserves 8-byte alignment of the stack.
;
;******************************************************************************
        PRESERVE8

;******************************************************************************
;
; Place code into the reset code section.
;
;******************************************************************************
        AREA    RESET, CODE, READONLY
        THUMB

;******************************************************************************
;
; The vector table.
;
;******************************************************************************
        EXPORT  __Vectors
__Vectors
        DCD     StackMem + Stack            ; Top of Stack
        DCD     Reset_Handler               ; Reset Handler
        DCD     NmiSR                       ; NMI Handler
        DCD     FaultISR                    ; Hard Fault Handler
        DCD     IntDefaultHandler           ; MPU Fault Handler
        DCD     IntDefaultHandler           ; Bus Fault Handler
        DCD     IntDefaultHandler           ; Usage Fault Handler
        DCD     0                           ; Reserved
        DCD     0                           ; Reserved
        DCD     0                           ; Reserved
        DCD     0                           ; Reserved
        DCD     IntDefaultHandler           ; SVCall Handler
        DCD     IntDefaultHandler           ; Debug Monitor Handler
        DCD     0                           ; Reserved
        DCD     IntDefaultHandler           ; PendSV Handler
        DCD     IntDefaultHandler           ; SysTick Handler
        DCD     IntDefaultHandler           ; GPIO Port A
        DCD     IntDefaultHandler           ; GPIO Port B
        DCD     IntDefaultHandler           ; GPIO Port C
        DCD     IntDefaultHandler           ; GPIO Port D
        DCD     IntDefaultHandler           ; GPIO Port E
        DCD     IntDefaultHandler           ; UART0
        DCD     IntDefaultHandler           ; UART1
        DCD     IntDefaultHandler           ; SSI
        DCD     IntDefaultHandler           ; I2C
        DCD     IntDefaultHandler           ; PWM Fault
        DCD     IntDefaultHandler           ; PWM Generator 0
        DCD     IntDefaultHandler           ; PWM Generator 1
        DCD     IntDefaultHandler           ; PWM Generator 2
        DCD     IntDefaultHandler           ; Quadrature Encoder
        DCD     IntDefaultHandler           ; ADC Sequence 0
        DCD     IntDefaultHandler           ; ADC Sequence 1
        DCD     IntDefaultHandler           ; ADC Sequence 2
        DCD     IntDefaultHandler           ; ADC Sequence 3
        DCD     IntDefaultHandler           ; Watchdog
        DCD     IntDefaultHandler           ; Timer 0A
        DCD     IntDefaultHandler           ; Timer 0B
        DCD     IntDefaultHandler           ; Timer 1A
        DCD     IntDefaultHandler           ; Timer 1B
        DCD     IntDefaultHandler           ; Timer 2A
        DCD     IntDefaultHandler           ; Timer 2B
        DCD     IntDefaultHandler           ; Comp 0
        DCD     IntDefaultHandler           ; Comp 1
        DCD     IntDefaultHandler           ; Comp 2
        DCD     IntDefaultHandler           ; System Control
        DCD     IntDefaultHandler           ; Flash Control
        DCD     IntDefaultHandler           ; GPIO Port F
        DCD     IntDefaultHandler           ; GPIO Port G
        DCD     IntDefaultHandler           ; GPIO Port H
        DCD     IntDefaultHandler           ; UART2 Rx and Tx
        DCD     IntDefaultHandler           ; SSI1 Rx and Tx
        DCD     IntDefaultHandler           ; Timer 3 subtimer A
        DCD     IntDefaultHandler           ; Timer 3 subtimer B
        DCD     IntDefaultHandler           ; I2C1 Master and Slave
        DCD     IntDefaultHandler           ; Quadrature Encoder 1
        DCD     IntDefaultHandler           ; CAN0
        DCD     IntDefaultHandler           ; CAN1
        DCD     IntDefaultHandler           ; CAN2
        DCD     IntDefaultHandler           ; Ethernet
        DCD     IntDefaultHandler           ; Hibernate
        DCD     IntDefaultHandler           ; USB0
        DCD     IntDefaultHandler           ; PWM Generator 3
        DCD     IntDefaultHandler           ; uDMA Software Transfer
        DCD     IntDefaultHandler           ; uDMA Error

;******************************************************************************
;
; This is the code that gets called when the processor first starts execution
; following a reset event.
;
;******************************************************************************
        EXPORT  Reset_Handler
Reset_Handler
        ;
        ; Call the C library enty point that handles startup.  This will copy
        ; the .data section initializers from flash to SRAM and zero fill the
        ; .bss section.
        ;
        IMPORT  __main
        B       __main

;******************************************************************************
;
; This is the code that gets called when the processor receives a NMI.  This
; simply enters an infinite loop, preserving the system state for examination
; by a debugger.
;
;******************************************************************************
NmiSR
        B       NmiSR

;******************************************************************************
;
; This is the code that gets called when the processor receives a fault
; interrupt.  This simply enters an infinite loop, preserving the system state
; for examination by a debugger.
;
;******************************************************************************
FaultISR
        B       FaultISR

;******************************************************************************
;
; This is the code that gets called when the processor receives an unexpected
; interrupt.  This simply enters an infinite loop, preserving the system state
; for examination by a debugger.
;
;******************************************************************************
IntDefaultHandler
        B       IntDefaultHandler

;******************************************************************************
;
; Make sure the end of this section is aligned.
;
;******************************************************************************
        ALIGN

;******************************************************************************
;
; Some code in the normal code section for initializing the heap and stack.
;
;******************************************************************************
        AREA    |.text|, CODE, READONLY

;******************************************************************************
;
; The function expected of the C library startup code for defining the stack
; and heap memory locations.  For the C library version of the startup code,
; provide this function so that the C library initialization code can find out
; the location of the stack and heap.
;
;******************************************************************************
    IF :DEF: __MICROLIB
        EXPORT  __initial_sp
        EXPORT  __heap_base
        EXPORT __heap_limit
    ELSE
        IMPORT  __use_two_region_memory
        EXPORT  __user_initial_stackheap
__user_initial_stackheap
        LDR     R0, =HeapMem
        LDR     R1, =(StackMem + Stack)
        LDR     R2, =(HeapMem + Heap)
        LDR     R3, =StackMem
        BX      LR
    ENDIF

;******************************************************************************
;
; Make sure the end of this section is aligned.
;
;******************************************************************************
        ALIGN

;******************************************************************************
;
; Tell the assembler that we're done.
;
;******************************************************************************
        END


I tried adding the Keil startup file (C:\Keil\ARM\Startup\Luminary\Startup.s) to the project and got the error below. Is there a file missing from the LM3 bootloader project?

Code: [Select]
Build target 'uTaskerBoot'
assembling Startup.s...
linking...
.\Objects\uTaskerBoot.axf: Error: L6200E: Symbol __user_initial_stackheap multiply defined (by startup.o and lm3sxxxx_startup_keil.o).
Target not created



Cheers,

Peter.

41
Luminary Micro TM LM3SXXXX / Re: uTasker Bootloader
« on: October 03, 2008, 12:31:01 AM »
Hi Mark,

Thanks for the help. No joy though. I've attached the setting tab for the compiler and linker. I can't see anything obvious.

Cheers,

Peter.

42
Luminary Micro TM LM3SXXXX / uTasker Bootloader
« on: October 02, 2008, 07:45:48 AM »
Mi Mark,

I tried to build the Bootloader project using uVision and get the following errors:
Code: [Select]
Build target 'uTaskerBoot'
linking...
.\Objects\uTaskerBoot.axf: Error: L6320W: Ignoring --entry command. Cannot find argument 'Reset_Handler'.
.\Objects\uTaskerBoot.axf: Warning: L6320W: Ignoring --first command. Cannot find argument '__Vectors'.
Target not created

I presume that the addresses of these two need to be set up some where?

Cheers,

Peter.

43
Luminary Micro TM LM3SXXXX / Re: System Tick Speed.
« on: October 02, 2008, 03:52:19 AM »
Hi Mark,

I looked at the uTaskerSchedule function and answered my own question. So, worst case is when a task has just yeilded control and an event for it is posted, it will have to now wait for all other tasks (that can run) to be run before it can process the event. Is that correct?

Cheers,


Peter.

44
Luminary Micro TM LM3SXXXX / Re: System Tick Speed.
« on: October 02, 2008, 02:55:10 AM »
Hi Mark,

I am only using the simulator at this stage. If I change the tick resolution to 5, the pin on port F simulator display toggles about once every 3 secs.

As to my other question regarding the scheduling of task. When a tcp/ip message comes in, an interrupt sends an event to the tcp/ip task? This task is then schedules to run, and will be run as soon as all the tasks before it in the task list that are ready to be run have been run?

Are the tasks waiting to be run, run in the order that they are in the task list. or the order that they changed to the ready to run state?

Cheers,

Peter.

45
Luminary Micro TM LM3SXXXX / System Tick Speed.
« on: September 30, 2008, 09:09:30 AM »
Hi Mark,

The example application uses a system tick of 50mS. It is my understanding that this should cause tasks to run 20 times per second. I tried halving this expecting the  watchdog task to toggle the LED at twice the speed, yet it seems to toggle slower.
When I changed the tick time to 10ms, the led toggled even slower. Am I missing something?  ???

Also, is it correct that with a tick of 50ms, the fastest a task can run is 200 times a second. In order to get decent response times over Ethernet. I want to set the tick time to 1ms, is this possible?

cheers,

Peter.

Pages: 1 2 [3] 4