An erronous checksum was detected

Go To Last Post
12 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Looks like myself and a few none English forums have report this error so I imagine its not related to my issue but here is hopping.

Error:
Timestamp: 2014-05-31 00:33:39.253
Severity: ERROR
ComponentId: 20100
StatusCode: 1
ModuleName: TCF command: Modules:writeToMemory failed.

An error occured while executing command with ID 0x13. Timed out waiting for a response. An erronous checksum was detected 1 time(s).

Info:
I have a stk-500 and set it all up on a win7 box. I'm able to read the chip and set my fuses. I have never used this board before and its possible I have something wrong.

my com port is a usb converter and I didnt set the baud stuff. Not sure if that my issue or not.

I was able to set my fuse bits with no external osc. but after I set my chip to 8mhz I needed to change the jumper to use an external 8mhz osc. Guessing this is normal?

At this point I was able to set fuses and start to write but that errors comes up before the first block of code is written. The erase does work ok.

I'm writing to a atmega328 chip with these fuses.
ext:FD
Hi: DA
Lo: DF

setting the isp clock does not help high or low.

Edit: if I write small code it works, just troubles with large hex files.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I presume that you have a genuine Atmel STK500 board.
Which version of Atmel Studio 6 are you using ?

It sounds as if the COM port has been opened as a brain-dead MSDOS port. i.e. it treats "\r\n" as "\n" or "\r" as "\n" or simply removes "\r" characters.

In other words it is not passing all bytes.

This seems to be unlikely from Atmel's side. Are you using some weird USB-RS232 driver ?

David.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I use 6.2 and yes this is atmels board.

Are you using some weird USB-RS232 driver ? - yes, is there a known driver that works?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Some of those are not my issue, some seem related and some indicate slow or bad connections as well. Does anyone here use a usb to com port adapter? They are all pretty much the same hardware but there are lots of drivers around. I'll try a few others I guess.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

No, they are NOT "pretty much the same hardware".

There are the ones with prolific chips and ones with FTDI chips. The FTDI are much better, both for the hardware and the driver. prolific has had a problem with "counterfeit" drivers, to add to difficulties.

Jim

Jim Wagner Oregon Research Electronics, Consulting Div. Tangent, OR, USA http://www.orelectronics.net

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I saw the FTDI drivers and tried it out, they dont work with this chip so I must have the prolific version. I found a few drivers that work but they all have the same timeout issues. Also its not just large files its just hit and miss so big files have a better chance of failing. At at least I can get my boot loader on there.

If I run the prolific check utility it says pl-2303 xa / hxa

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The counterfeit PL2303 chips don't work very well.

Mind you, they are ever so cheap!
Most of the $1 or $1.50 USB->RS232 cables use counterfeits.

The genuine PL2303 works ok.

David.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

ill just pick up a FTDI and try it out. Thx for the great info!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

One of the major brands that has FTDI chip is TrippLite.

Jim

Jim Wagner Oregon Research Electronics, Consulting Div. Tangent, OR, USA http://www.orelectronics.net

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

my new adapter works like a charm thx all.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Sorry for coming late to the discussion, but here are my cents...

Quote:

An error occured while executing command with ID 0x13. Timed out waiting for a response. An erronous checksum was detected 1 time(s).

This is a stk500v2 protocol error, meaning that the framing of the protocol detected an issue. Either timeout or scrambling, causing the command checksum to be wrong. As said, we usually see this with those 'special' usb-rs232 converters. We do not see these issues using FTDI or real Prolific devices, or other converters that behaves correctly...

Quote:

Try reading the first hits in Google search results for "ComponentId: 20100 "?

Unfortunately, 20100 is basically the 'backend' of Atmel Studio, the part that does the programming and debugging. New in 6.2 is that the messages in the details dropdown in the error box has been massively improved from just a generic message to actually showing the internal error. Might look a bit greek to some, but should make it easier to track down the issue.

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)