| Author |
Message |
|
|
Posted: Oct 30, 2009 - 05:26 PM |
|


Joined: Jun 15, 2008
Posts: 1762
Location: North Carolina USA
|
|
|
peret wrote:
This topic came up elsewhere recently, in connection with AT890USB1287 devices. They are shipped with the boot loader installed and the lock bits set, and if you erase to clear the lock bits, you lose the boot loader.
I have access to it from JTAG and here is the configuration:
Code:
JAVAN firmware as received:
Fuses:
BOD at Vcc=2.6 V
HWBE
SPIEN
BOOTSZ=4096 start $F000
Ext. Crystal Osc 8.0- MHz Startup 258 CK+65 ms
Extended 0xF3 High 0x99 Low 0xDE
Lockbits 0xFF (no locks)
OSCAL 0x9F
VTarget=4.9 Volts
JTAG-ICE mk2 HW Info Rev 0x01 Firmware 0606 0606
So no lockbits are set. Flip should work? What is this "reset" it refers to? |
|
|
| |
|
|
|
|
|
Posted: Oct 30, 2009 - 08:36 PM |
|


Joined: May 26, 2004
Posts: 2538
Location: Las Vegas, Nevada
|
|
| Ah, well you cleared the lock bits already, otherwise you couldn't use JTAG, and that presumably wasted the boot loader at the same time. FLIP won't work unless you reprogram the boot loader. The "reset" in FLIP just drops out of the boot loader and starts execution at 0x0000. |
|
|
| |
|
|
|
|
|
Posted: Oct 30, 2009 - 09:48 PM |
|


Joined: Jun 15, 2008
Posts: 1762
Location: North Carolina USA
|
|
I didn't intentionally erase anything, and the .hex file I saved from flash has code starting at 0x1E000 which I take to be $F000 in word addressing.
The bootloader must be running since FLIP gets the signature bytes. But it obstinately says "Device protection is set" in red letters at the bottom, and won't let me read or write flash or eeprom. It's FLIP 3.3.4. Here's the start and end of the bootloader flash:
Code:
:10E000000C94B3F6FFFFFFFFFFFFFFFFFFFFFFFFD3
:10E01000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF10
:10E02000FFFFFFFFFFFFFFFF0C94BBF5FFFFFFFFAC
:10E03000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0
:10E04000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFE0
:10E05000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFD0
:10E06000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFC0
:10E07000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFB0
:10E08000FFFFFFFFFFFFFFFFFFFFFFFF00007CF62A
:10E0900008006BF66EF670F672F674F676F678F6A1
:10E0A0007AF6A7010001000000FF12BD01BDF89A39
:10E0B00000B5089501E00895F999FECF12BD01BDA4
:10E0C00020BDFA9AF99AF6CFF999FECF0C9455F043
:10E0D000F8012BBF069108952297F8012BBF4691B6
:10E0E0004983319606910883142F22960895A895A6
:10E0F00007EF04BFE0E6F0E0008108610083F083F1
...
:10F1600003010902120001010080320904000000BD
:10F17000000000000C03410054004D0045004C000D
:10F180001E03410054003900300055005300420076
:10F1900031003200380020004400460055000C03C6
:10F1A00031002E0030002E00300004030904FFFF60
:10F1B000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF5F
|
|
|
| |
|
|
|
|
|
Posted: Nov 01, 2009 - 04:27 PM |
|


Joined: Jun 15, 2008
Posts: 1762
Location: North Carolina USA
|
|
| I like the set-only fuses and can see how they would be useful to indicate abuse in the field, e.g. overvoltaging or undervoltaging a cell in a battery pack. But they are not so useful for recording number of uses. Setting a fuse after a prescale in EEPROM has an obvious defeat method. How about a 16 bit increment-only counter in a future version? |
|
|
| |
|
|
|
|
|
Posted: Nov 03, 2009 - 11:55 PM |
|


Joined: Aug 13, 2006
Posts: 6702
Location: Bellingham, WA - USA
|
|
Things are starting to make more sense as I read through the various documentation, but I'm still pining for Smiley's Dummies article. One thing I would mention is the inconsistency of the product names in the pdf files - sometimes it's AT88SA###, sometimes it's ATSA88###, and sometimes it's ATSA###. Not too hard to figure out, but something you might want to fix.
It's nice how the daughter board plugs onto an STK500. Overall the big picture is still elusive, but maybe in a few days, and a little more reading... |
_________________ Chuck Baird
"It's better to catch the trapeze than test the safety net" -- RPi book
http://www.cbaird.org
|
| |
|
|
|
|
|
Posted: Nov 05, 2009 - 05:48 PM |
|

Joined: Apr 01, 2009
Posts: 19
|
|
|
|
|
|
|
Posted: Nov 05, 2009 - 07:34 PM |
|


Joined: Aug 13, 2006
Posts: 6702
Location: Bellingham, WA - USA
|
|
Thanks for the URLs, Chris. I had actually already found, printed, and read those, plus 5 or 6 others. Lots of details about trees, but I'm still missing the overall forest view. It's coming - it's just a matter of keeping focused, drawing myself some pictures, and not getting interrupted with the thousand other things wanting my attention.
Smiley's soon-to-be-famous article is mentioned on page 1 of this thread, where he wonders whether it's worth his time and effort to write an introductory article for Circuit Cellar or Nuts and Volts. I hope he does. |
_________________ Chuck Baird
"It's better to catch the trapeze than test the safety net" -- RPi book
http://www.cbaird.org
|
| |
|
|
|
|
|
Posted: Nov 08, 2009 - 10:47 PM |
|


Joined: Nov 01, 2005
Posts: 6324
Location: Hilversum - the Netherlands
|
|
Got my package 2 days ago. Thanks for that Chris/Atmel.
I will take the dive this week I guess. Lots of reading to do. And not being a C-guy, my ride may be a rough one
To all:
If you need to post large files, like Smiley hopefully will .... given she finds the time, there is a gmail-group for this.
Drop me a PM if you wish to join.
And to the members of that group: if you post something important, and want all members to notice, click the "Share"-button in the upper right corner of the gmail-doc, drop down menu, click "Send a message to collaborators ... "
Nard |
_________________ Dragon broken ? Or problems with the Parallel Port Programmer ? Scroll down on my projects-page http://www.aplomb.nl/TechStuff/TechStuff.html for tips
|
| |
|
|
|
|
|
Posted: Nov 09, 2009 - 05:52 AM |
|


Joined: Mar 28, 2001
Posts: 20384
Location: Sydney, Australia (Gum trees, Koalas and Kangaroos, No Edelweiss)
|
|
Hyppee just got mine too. Thank you very much.
Now off to buy a few spare neurons to try and get my brain around things. |
_________________ John Samperi
Ampertronics Pty. Ltd.
www.ampertronics.com.au
* Electronic Design * Custom Products * Contract Assembly
|
| |
|
|
|
|
|
Posted: Nov 09, 2009 - 06:20 AM |
|


Joined: Jul 02, 2005
Posts: 5946
Location: Melbourne, Australia
|
|
Ahha ... mine arrived this afternoon also. Thanks Chris.
Now to find a clear space on the workbench and some time ...
Cheers,
Ross |
_________________ Ross McKenzie
ValuSoft
Melbourne Australia
|
| |
|
|
|
|
|
Posted: Nov 09, 2009 - 08:08 AM |
|


Joined: Mar 28, 2001
Posts: 20384
Location: Sydney, Australia (Gum trees, Koalas and Kangaroos, No Edelweiss)
|
|
Ok enough for the day. I got FLIP to talk to the chip, downloaded all necessary info and code that I can think of.
Got CryptoAuth Utilities to see the kit.
I know that one needs a AT88SA10HS for a host and either a AT88SA100S or a AT88SA102S on the "other side" (client).
Have not messed around with JTAG yet but may have some time tomorrow and try the Dragon's new found power with the USB1287 chip. So far it has worked well if, very sluggishly (try and say that sober) with the Xmega.
Never seen sot23 ZIF sockets in my life.
edit and what's the story with FLIP saying that the "Device protection is set"? |
_________________ John Samperi
Ampertronics Pty. Ltd.
www.ampertronics.com.au
* Electronic Design * Custom Products * Contract Assembly
|
| |
|
|
|
|
|
Posted: Nov 10, 2009 - 06:11 PM |
|


Joined: Apr 25, 2004
Posts: 3809
Location: Denmark
|
|
@js
Are you using the new Studio "Beta" that gives Dragon Xmega support ?
I'm still on Studio 4.13 , on my main XP machine.
I was scared a bit by the "666 - beast version"
Do i need to upgrade to something newer ?
Btw; Is there anywhere else i "Officialy" can get the Atmel SW , i'm getting a bit tired of registering for the 118' time.
Wonder when they make a "login system"
Hope FedEX pays me a visit tomorrow (Thanx Chris/Atmel)
Edit: Yes FedEX was here
/Bingo |
Last edited by Bingo600 on Nov 11, 2009 - 08:59 PM; edited 1 time in total
|
| |
|
|
|
|
|
Posted: Nov 10, 2009 - 08:27 PM |
|


Joined: Mar 28, 2001
Posts: 20384
Location: Sydney, Australia (Gum trees, Koalas and Kangaroos, No Edelweiss)
|
|
|
|
|
|
|
Posted: Nov 13, 2009 - 03:19 PM |
|

Joined: Apr 06, 2008
Posts: 415
Location: Singapore
|
|
Just got my javan kit. I don't have a Windows box at home, so I can't run the demo app. Also, is there no documentation on the comms protocol that the demo firmware uses?
I'm implementing a quick test application with the LUFA libraries, enough to implement the desired 1 wire interface. Let's see how far we get this weekend. |
|
|
| |
|
|
|
|
|
Posted: Nov 17, 2009 - 02:33 PM |
|

Joined: Apr 01, 2009
Posts: 19
|
|
Hi everyone,
We posted a new version of the CryptoAuthentication Utility and firmware for the Utility on our website. Please upgrade to this version as the last had some “features” that have been upgraded.
Link: http://www.atmel.com/dyn/products/tools ... ily_id=699
P.S. we will have Firmware libraries posted in the next few days. I will put up another post when these are up.
Chris |
|
|
| |
|
|
|
|
|
Posted: Nov 30, 2009 - 08:17 PM |
|


Joined: Jun 15, 2008
Posts: 1762
Location: North Carolina USA
|
|
Although the 11/09 download is called "version 3" the properties tag shows version 1.0.0.2
Most of the pictures in the CAU_help.pdf have a "SA100" tab, but some don't. I don't get that tab on Vista. A possibly related problem, the software SHA-256 can't duplicate the example in the AT88SA100S.pdf data sheet because specifying SA100S doesn't use opcode 01 in the challenge string. That seems stuck at opcode 08 for the SA102S (consequently the SA102S.pdf example does work).
Keyboard shortcuts for cut and paste would speed up key testing. |
|
|
| |
|
|
|
|
|
Posted: Dec 08, 2009 - 10:21 PM |
|

Joined: Apr 01, 2009
Posts: 19
|
|
|
Quote:
Most of the pictures in the CAU_help.pdf have a "SA100" tab
The CryptoAuthentication Utility was developed with a tab to support the SA100S device. The current version did not have SA100S support complete so the SA100S tab was disabled for the release. We hope to have this support (and the tab) restored to the Utility in later versions.
Quote:
SHA-256 can't duplicate the example in the AT88SA100S.pdf data sheet because specifying SA100S doesn't use opcode 01 in the challenge string. That seems stuck at opcode 08 for the SA102S (consequently the SA102S.pdf example does work).
This is also a known issue; we are working diligently to incorporate 100% support for the SA100S for the calculation tab as well as” hardware setup” and “hardware operations” tabs.
Thank you for your comments; I will keep you posted on updates.
Chris |
|
|
| |
|
|
|
|
|
Posted: Dec 11, 2009 - 04:29 PM |
|

Joined: Apr 01, 2009
Posts: 19
|
|
All,
We have posted “CryptoAuthentication Firmware Library Version 1.0.5a” this package is the entire embedded source code content for the libraries to communicate with the CryptoAuthentication device.
There are two versions of code in the download, a bit-banged version designed to work on the AT88CK109STK kit and a template version with the physical layer stubbed out. The template version can be used with any development environment as long as the physical layer is implemented for that platform.
Download “CryptoAuthentication Firmware Library Version 1.0.5a” from the following link, extract all files, and open the Redme.htm file to begin.
http://www.atmel.com/dyn/products/tools.asp?family_id=699
Good luck and once again please post any comments you have.
Chris |
|
|
| |
|
|
|
|
|
Posted: Dec 11, 2009 - 04:35 PM |
|

Joined: Apr 01, 2009
Posts: 19
|
|
|
Quote:
Although the 11/09 download is called "version 3" the properties tag shows version 1.0.0.2
Sorry I missed this question: this version number is the version number related to the library used in the CryptoAuthentication Uility firmware binary.
The binary for the CAU matches version 3 of the CAU and thus is labeld version 3. However the version of the library used in the binary is 1.0.0.2.
The current library version is 1.0.5a which I posted a link to in my last comment.
Chris |
|
|
| |
|
|
|
|
|
Posted: Feb 01, 2010 - 11:36 PM |
|

Joined: Apr 01, 2009
Posts: 19
|
|
Hello All,
Its been a while since I posted, Any comments on the AT88CK109STK3 kits.
Chris |
|
|
| |
|
|
|
|
|