1
µTasker general / Re: Great code, broken website
« on: August 15, 2011, 04:26:35 PM »
Looks good Mark! 
News:
Nov 2020: uTasker i.MX RT V1.4.12 is productive - with complete secure loading concept.
Follow uTasker updates at www.twitter.com/uTasker !!
Online Forum registration has now been disabled. Please send an email to an address at the bottom of the home page with your preferred user name and email address if you would like an account.
Return to uTasker main site: www.utasker.com
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.
Pages: [1]
2
µTasker general / Re: Great code, broken website
« on: August 11, 2011, 04:50:37 PM »
Hi Mark,
I can't see any change at the moment, did you make the changes live?
When I do web stuff I try to keep as much as possible free to sort itself out, I avoid using things like fixed sizes & absolute measurements as far as possible as everyone's display is different.
I can't see any change at the moment, did you make the changes live?
When I do web stuff I try to keep as much as possible free to sort itself out, I avoid using things like fixed sizes & absolute measurements as far as possible as everyone's display is different.
3
µTasker general / Re: Great code, broken website
« on: August 10, 2011, 02:35:47 PM »
Mark - I'm a luddite and actually develop on a Panasonic CF-18 toughbook, which will probably result in me being burned at the stake by proper coders with triple 20" TFT's... I'm using FireFox 5.0, screen is 1024x768 so probably on a par with netbooks.
It's an unfortunate truth that sometimes with super-compliant modern HTML, old fashioned (and deprecated) tables are still the best way to make a layout that works reliably. My webdev friend really hates it when I point this out to him as he wrestles with DIVs
It's also unfair of me to remind him that the "design it for 800x600 VGA and a 14.4 modem" mantra has come back round to being entirely reasonable given the number of iPads/phones & netbooks out there now.
It's an unfortunate truth that sometimes with super-compliant modern HTML, old fashioned (and deprecated) tables are still the best way to make a layout that works reliably. My webdev friend really hates it when I point this out to him as he wrestles with DIVs
It's also unfair of me to remind him that the "design it for 800x600 VGA and a 14.4 modem" mantra has come back round to being entirely reasonable given the number of iPads/phones & netbooks out there now.
4
µTasker general / Great code, broken website
« on: August 10, 2011, 12:51:36 PM »
Bit of a picky one as I know Mark is a far better coder than I'll ever be, but it is a bit disconcerting that the uTasker website never seems to work properly 
Side menu doesn't scroll, main page doesn't fit my laptop screen, and if I scroll it this happens...
Side menu doesn't scroll, main page doesn't fit my laptop screen, and if I scroll it this happens...
5
NXPTM M522XX, KINETIS and i.MX RT / Re: M5225x starting problem at power on
« on: May 10, 2011, 07:24:24 PM »
Are the CLKMOD pins set correctly & have you initialised the clock registers to use the external oscillator? We made this mistake in the 1st version of our board, in the end we went back & looked at the M52259EVB schematic to spot the differences.
6
NXPTM M522XX, KINETIS and i.MX RT / Re: Adding uTasker_BM Bootloader to existing (non-uT) CW project
« on: May 10, 2011, 07:22:46 PM »
Thanks Mark!
7
NXPTM M522XX, KINETIS and i.MX RT / Adding uTasker_BM Bootloader to existing (non-uT) CW project
« on: May 03, 2011, 07:09:53 PM »
Hi all, this is my 1st post so please be gentle 
First off I must thank Mark for all his help on the Freescale forums, his posts have helped me sort out a lot of problems both of my own doing & some which are all Freescale's own
I have a large project on the MCF52259, all in C (using CW7.2) that I need to add a flash upgrade/bootloader routine to. Whilst looking round for info I found references to the uTasker "bare minimum" bootloader and it sounds almost perfect for what we need, with a few minor tweaks.
Our hardware is sat on an RS485 bus, which is how the firmware data will arrive (we already have routines to Rx & parse the .s19 data through the protocol we're using). We have an Atmel AT25DF081A SPI flash chip in it which we intend to read the data into before flashing the micro. I think the AT25 is compatible with the AT45 supported in the uTasker project.
The ideal situation is to end up with a single .s19 file which can be burnt to new boards which contains both bootloader & main app code.
I have registered & downloaded the latest uTasker project, and loaded uTaskerBootCW7.0.mcp into CodeWarrior. I've also read the two PDF's (http://www.utasker.com/docs/uTasker/BM-Booloader_for_M5223X.PDF & http://www.utasker.com/docs/uTasker/uTaskerBoot_003.PDF) but due to all the "extra" #defines and options in the code I'm having a bit of trouble understanding the basics of what I need to do to integrate this into an existing project - the main project is not using uTasker, and before anyone suggests it no we don't have time to port the entire project over!
My first steps have been to duplicate the bootloader project and then remove all the #defines which are not being used (EG for different processors) but that only gets me so far as the project links in a lot of files from the main uTasker project, which means a lot of stuff to look through to try and work out if we can remove them or not.
All we really need is a bootloader which starts up, checks for new data in the SPI Flash and then flashes the micro. Being able to fall back to a serial command line on some condition (EG spare pin held low) would be nice but not essential.
We do not want to use the uTaskerConvert.exe application if possible, as it would lead to extra work changing our legacy .s19-based RS485 uploader to support the different filetype.
So, the short version of all my rambling is:
- What can we strip out of the uTaskerBootCW7.0.mcp project to leave us with a bare-bones routine which only checks SPI Flash and either upgrades or continues to the main app?
- How do I build the uTaskerBoot project to give me code I can include in my main project without using uTaskerConvert.exe?
- How do I modify my existing project to include the compiled uTaskerBoot code? I understand modifying the start address in the project_FLASH.lcf as per the PDF:
[flash (RX) : ORIGIN = 0x0001000, LENGTH = 0x0003F000]
Is there some way to automatically include & place the bootloader code before the main app?
Apologies for the rambling newbie questions, I've come into the embedded programming lark sideways so there are some big blind-spots in my knowledge
First off I must thank Mark for all his help on the Freescale forums, his posts have helped me sort out a lot of problems both of my own doing & some which are all Freescale's own
I have a large project on the MCF52259, all in C (using CW7.2) that I need to add a flash upgrade/bootloader routine to. Whilst looking round for info I found references to the uTasker "bare minimum" bootloader and it sounds almost perfect for what we need, with a few minor tweaks.
Our hardware is sat on an RS485 bus, which is how the firmware data will arrive (we already have routines to Rx & parse the .s19 data through the protocol we're using). We have an Atmel AT25DF081A SPI flash chip in it which we intend to read the data into before flashing the micro. I think the AT25 is compatible with the AT45 supported in the uTasker project.
The ideal situation is to end up with a single .s19 file which can be burnt to new boards which contains both bootloader & main app code.
I have registered & downloaded the latest uTasker project, and loaded uTaskerBootCW7.0.mcp into CodeWarrior. I've also read the two PDF's (http://www.utasker.com/docs/uTasker/BM-Booloader_for_M5223X.PDF & http://www.utasker.com/docs/uTasker/uTaskerBoot_003.PDF) but due to all the "extra" #defines and options in the code I'm having a bit of trouble understanding the basics of what I need to do to integrate this into an existing project - the main project is not using uTasker, and before anyone suggests it no we don't have time to port the entire project over!
My first steps have been to duplicate the bootloader project and then remove all the #defines which are not being used (EG for different processors) but that only gets me so far as the project links in a lot of files from the main uTasker project, which means a lot of stuff to look through to try and work out if we can remove them or not.
All we really need is a bootloader which starts up, checks for new data in the SPI Flash and then flashes the micro. Being able to fall back to a serial command line on some condition (EG spare pin held low) would be nice but not essential.
We do not want to use the uTaskerConvert.exe application if possible, as it would lead to extra work changing our legacy .s19-based RS485 uploader to support the different filetype.
So, the short version of all my rambling is:
- What can we strip out of the uTaskerBootCW7.0.mcp project to leave us with a bare-bones routine which only checks SPI Flash and either upgrades or continues to the main app?
- How do I build the uTaskerBoot project to give me code I can include in my main project without using uTaskerConvert.exe?
- How do I modify my existing project to include the compiled uTaskerBoot code? I understand modifying the start address in the project_FLASH.lcf as per the PDF:
[flash (RX) : ORIGIN = 0x0001000, LENGTH = 0x0003F000]
Is there some way to automatically include & place the bootloader code before the main app?
Apologies for the rambling newbie questions, I've come into the embedded programming lark sideways so there are some big blind-spots in my knowledge
Pages: [1]