1
ATMELTM AT91SAM7X and AVR32 / Re: on board Can interface
« on: February 17, 2010, 05:15:12 PM »
Mark,
I will have a look at it certainly
Mike
I will have a look at it certainly
Mike
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
ATMELTM AT91SAM7X and AVR32 / on board Can interface
« on: February 17, 2010, 09:56:59 AM »
Hello Mark,
I see that the CAN interface on the sam7x is not supported (yet!), and I would be interested in using it. I have implemented CAN (before uTasker) on a sam7s with an MCP2515 spi based controller. I would be interested in implementing your interface on the 7X, and wondered if the m2553x.c code would be s useful starting point?
If so, could you point me at a download for it please?
Regards Mike
I see that the CAN interface on the sam7x is not supported (yet!), and I would be interested in using it. I have implemented CAN (before uTasker) on a sam7s with an MCP2515 spi based controller. I would be interested in implementing your interface on the 7X, and wondered if the m2553x.c code would be s useful starting point?
If so, could you point me at a download for it please?
Regards Mike
3
ATMELTM AT91SAM7X and AVR32 / Re: SAM7X IAR5.4 Project configuration
« on: February 15, 2010, 09:11:15 AM »
OK, the next step.
Using EWARM 5.41, I can get reliable downloads using the $TOOLKIT_DIR$\config\flashloader\Atmel\AT91SAM7X256-EK\flash-at91sam7x256.flash flash loader by specifying the correct device (Atmel AT91SAM7X256 for example) in the Project/Options/General Options/Target rather than the appropriate core (ARM7TDMI).
Also in the Project/Options/Debugger/Download/Edit, ensure that --boot parameter is shown. Without this, the chip seems to be left with ram mapped at 0.
I don't understand (yet) why I cannot build for the ARM7TDMI core, as the identical binary file is produced, and the download should be defined by the files used, not the processor settings but...
Regards
Mike
Using EWARM 5.41, I can get reliable downloads using the $TOOLKIT_DIR$\config\flashloader\Atmel\AT91SAM7X256-EK\flash-at91sam7x256.flash flash loader by specifying the correct device (Atmel AT91SAM7X256 for example) in the Project/Options/General Options/Target rather than the appropriate core (ARM7TDMI).
Also in the Project/Options/Debugger/Download/Edit, ensure that --boot parameter is shown. Without this, the chip seems to be left with ram mapped at 0.
I don't understand (yet) why I cannot build for the ARM7TDMI core, as the identical binary file is produced, and the download should be defined by the files used, not the processor settings but...
Regards
Mike
4
ATMELTM AT91SAM7X and AVR32 / Re: AT91SAM7 Device Overview
« on: February 15, 2010, 08:56:07 AM »
Hello Mark, the SAM7X512 has 128k of RAM according to the Atmel site, as has the 7XC.
5
ATMELTM AT91SAM7X and AVR32 / Re: SAM7X IAR5.4 Project configuration
« on: February 12, 2010, 08:40:03 PM »
Hello Mark.
This project setup is for ewarm 5.30.1 (This does by default install into directory 5.40).
Latest version 5.4 (latest version is 5.41) has a different setup for the flash loaders.
When running the project in 5.30.1, it downloads OK using either the sam7x or 7xc flash load tools. Transfering the settings to 5.41, using the settings here it will only download using 7xc. Using 7x (which should work) the code ends up running in addresses in RAM (0x20xxxx), and does not flash the lights. This is independant of the parts that are enabled. downloading the entire setup (with serial, usb, ethernet anyway) it works file.
Downloading using sam7xc downloaders works.
I will keep looking.
Mike
This project setup is for ewarm 5.30.1 (This does by default install into directory 5.40).
Latest version 5.4 (latest version is 5.41) has a different setup for the flash loaders.
When running the project in 5.30.1, it downloads OK using either the sam7x or 7xc flash load tools. Transfering the settings to 5.41, using the settings here it will only download using 7xc. Using 7x (which should work) the code ends up running in addresses in RAM (0x20xxxx), and does not flash the lights. This is independant of the parts that are enabled. downloading the entire setup (with serial, usb, ethernet anyway) it works file.
Downloading using sam7xc downloaders works.
I will keep looking.
Mike
6
ATMELTM AT91SAM7X and AVR32 / Re: SAM7X IAR5.4 Project configuration
« on: February 11, 2010, 02:07:49 PM »
Thanks for your help. Can you explain why you need to use the sam7XC downloader files, as its a sam7X processor?
I have tried the (what I think are correct) files, and the download completes, but the result will not run!
I have downloaded many SAM7X systems, and always used the 7X files OK so...
Looking forward to your thoughts
Mike
I have tried the (what I think are correct) files, and the download completes, but the result will not run!
I have downloaded many SAM7X systems, and always used the 7X files OK so...
Looking forward to your thoughts
Mike
7
µTasker general / Re: Finding device with DHCP IP address
« on: February 09, 2010, 01:09:40 PM »
I don't know about the Lantronix method, but while trying to solve the same problem (with the difference that I may have several devices on my network segment, I came across
http://kelley.ca/wordpress/2008/10/24/digi-connect-me-discovery/ and
http://qbeukes.blogspot.com/2009/11/advanced-digi-discovery-protocol.html
which describes the protocol used by Digi for their modules. It essentially is a broadcast message to port 2362 containing identifier bytes 'D' 'I' 'G' 'I' as the first four. The rest of the packet can set up ip addresses etc.
Worth a thought
Mike
http://kelley.ca/wordpress/2008/10/24/digi-connect-me-discovery/ and
http://qbeukes.blogspot.com/2009/11/advanced-digi-discovery-protocol.html
which describes the protocol used by Digi for their modules. It essentially is a broadcast message to port 2362 containing identifier bytes 'D' 'I' 'G' 'I' as the first four. The rest of the packet can set up ip addresses etc.
Worth a thought
Mike
Pages: [1]