Could not enter programming mode

[Daniel-378]

Hi.

While I was programming my Ethernut 1.3 with stk500.exe, I had connected
SCK (SPI Bus Serial Clock) to GND. After that I read, that I must not do
that.
Now stk500.exe tells me, that the controller "Could not enter
programming mode".

Any advise how to fix it up?

Thanks,
Daniel
_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Andre Riesberg]

Daniel wrote:

>Hi.
>
>While I was programming my Ethernut 1.3 with stk500.exe, I had connected
>SCK (SPI Bus Serial Clock) to GND. After that I read, that I must not do
>that.
>Now stk500.exe tells me, that the controller "Could not enter
>programming mode".
>
>Any advise how to fix it up?
>
>Thanks,
>Daniel
>_______________________________________________
>http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>
>
>  
>

Hi Daniel,

do you pull the SCK signal to GND only on the programmer or on cpu or on
both?

Do you have disconnected all power supplys and start again?

Please make some tests:
First, disconnect programmer and CPU.

- Check the SCK signal at the programmer: In normal condition (no
programming) the signal must be on high level.
- Check the SCK signal at the CPU board. Normally you see a low level.
With a 10k resistor to +5V you can pull this signal to high level.
- With still disconnected board try to start programming (I use
avrdude). With a scope you can see (for a short time) a lot of pulse on
the SCK line.

Does this work?

Greeting
Andre






_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Daniel-378]

Andre Riesberg schrieb:

> Daniel wrote:
>
>  
>> Hi.
>>
>> While I was programming my Ethernut 1.3 with stk500.exe, I had connected
>> SCK (SPI Bus Serial Clock) to GND. After that I read, that I must not do
>> that.
>> Now stk500.exe tells me, that the controller "Could not enter
>> programming mode".
>>
>> Any advise how to fix it up?
>>
>> Thanks,
>> Daniel
>> _______________________________________________
>> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>>
>>
>>  
>>
>>    
> Hi Daniel,
>
> do you pull the SCK signal to GND only on the programmer or on cpu or on
> both?
>
> Do you have disconnected all power supplys and start again?
>
> Please make some tests:
> First, disconnect programmer and CPU.
>
> - Check the SCK signal at the programmer: In normal condition (no
> programming) the signal must be on high level.
> - Check the SCK signal at the CPU board. Normally you see a low level.
> With a 10k resistor to +5V you can pull this signal to high level.
> - With still disconnected board try to start programming (I use
> avrdude). With a scope you can see (for a short time) a lot of pulse on
> the SCK line.
>
> Does this work?
>
> Greeting
> Andre
>
>
>
>
>
>
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>
>  

Hi Andre, thanks for the answer.

Here are the results of the tests you mentioned:

- SP Duo 2 Programmer, only supported with Vcc & GND, not connected to
CPU: SCK (PB1) is low
    When I start programming, I see a short low voltage at SCK.
Unfortunately I doesn't have a scope, only a voltmeter.
    You say, the signal must be on high level. It's low. But I can
program my second Ethernut with this SP Duo without problems.

- CPU, not connected with SP Duo 2: SCK (PB1) is low
    Should I try to pull the SCK line high, when I connect the
programmer to the CPU?


Daniel
_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Andre Riesberg]

Daniel wrote:

>Andre Riesberg schrieb:
>  
>
>>Daniel wrote:
>>
>>  
>>    
>>
>>>Hi.
>>>
>>>While I was programming my Ethernut 1.3 with stk500.exe, I had connected
>>>SCK (SPI Bus Serial Clock) to GND. After that I read, that I must not do
>>>that.
>>>Now stk500.exe tells me, that the controller "Could not enter
>>>programming mode".
>>>
>>>Any advise how to fix it up?
>>>
>>>Thanks,
>>>Daniel
>>>_______________________________________________
>>>http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>>>
>>>
>>>
>>>
>>>    
>>>      
>>>
>>Hi Daniel,
>>
>>do you pull the SCK signal to GND only on the programmer or on cpu or on
>>both?
>>
>>Do you have disconnected all power supplys and start again?
>>
>>Please make some tests:
>>First, disconnect programmer and CPU.
>>
>>- Check the SCK signal at the programmer: In normal condition (no
>>programming) the signal must be on high level.
>>- Check the SCK signal at the CPU board. Normally you see a low level.
>>With a 10k resistor to +5V you can pull this signal to high level.
>>- With still disconnected board try to start programming (I use
>>avrdude). With a scope you can see (for a short time) a lot of pulse on
>>the SCK line.
>>
>>Does this work?
>>
>>Greeting
>>Andre
>>
>>
>>
>>
>>
>>
>>_______________________________________________
>>http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>>
>>  
>>    
>>
>
>Hi Andre, thanks for the answer.
>
>Here are the results of the tests you mentioned:
>
>- SP Duo 2 Programmer, only supported with Vcc & GND, not connected to
>CPU: SCK (PB1) is low
>    When I start programming, I see a short low voltage at SCK.
>Unfortunately I doesn't have a scope, only a voltmeter.
>    You say, the signal must be on high level. It's low. But I can
>program my second Ethernut with this SP Duo without problems.
>
>- CPU, not connected with SP Duo 2: SCK (PB1) is low
>    Should I try to pull the SCK line high, when I connect the
>programmer to the CPU?
>
>
>Daniel
>_______________________________________________
>http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>
>
>  
>

Hi Daniel,

see my commends:

- SP Duo 2 Programmer, only supported with Vcc & GND, not connected to
CPU: SCK (PB1) is low
** Could be ok. I have no schematics from this programmer.
    When I start programming, I see a short low voltage at SCK.
Unfortunately I doesn't have a scope, only a voltmeter.
** That's makes it a little complicated......
    You say, the signal must be on high level. It's low. But I can
program my second Ethernut with this SP Duo without problems.
** Ok. I think the programmer is no defect.

- CPU, not connected with SP Duo 2: SCK (PB1) is low
    Should I try to pull the SCK line high, when I connect the
** Try it with 10k! You have a second board, try to compare the signals on the two board.

programmer to the CPU?

Greetings
Andre





_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Daniel-378]

Daniel wrote:

>Andre Riesberg schrieb:
>  
>
>>Daniel wrote:
>>
>>  
>>    
>>
>>>Hi.
>>>
>>>While I was programming my Ethernut 1.3 with stk500.exe, I had
>>>connected SCK (SPI Bus Serial Clock) to GND. After that I read, that
>>>I must not do that.
>>>Now stk500.exe tells me, that the controller "Could not enter
>>>programming mode".
>>>
>>>Any advise how to fix it up?
>>>
>>>Thanks,
>>>Daniel
>>>_______________________________________________
>>>http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>>>
>>>
>>>
>>>
>>>    
>>>      
>>>
>>Hi Daniel,
>>
>>do you pull the SCK signal to GND only on the programmer or on cpu or
>>on both?
>>
>>Do you have disconnected all power supplys and start again?
>>
>>Please make some tests:
>>First, disconnect programmer and CPU.
>>
>>- Check the SCK signal at the programmer: In normal condition (no
>>programming) the signal must be on high level.
>>- Check the SCK signal at the CPU board. Normally you see a low level.
>>With a 10k resistor to +5V you can pull this signal to high level.
>>- With still disconnected board try to start programming (I use
>>avrdude). With a scope you can see (for a short time) a lot of pulse
>>on the SCK line.
>>
>>Does this work?
>>
>>Greeting
>>Andre
>>
>>
>>
>>
>>
>>
>>_______________________________________________
>>http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>>
>>  
>>    
>>
>
>Hi Andre, thanks for the answer.
>
>Here are the results of the tests you mentioned:
>
>- SP Duo 2 Programmer, only supported with Vcc & GND, not connected to
>CPU: SCK (PB1) is low
>    When I start programming, I see a short low voltage at SCK.
>Unfortunately I doesn't have a scope, only a voltmeter.
>    You say, the signal must be on high level. It's low. But I can
>program my second Ethernut with this SP Duo without problems.
>
>- CPU, not connected with SP Duo 2: SCK (PB1) is low
>    Should I try to pull the SCK line high, when I connect the
>programmer to the CPU?
>
>
>Daniel
>_______________________________________________
>http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>
>
>  
>

Hi Daniel,

see my commends:

- SP Duo 2 Programmer, only supported with Vcc & GND, not connected to
CPU: SCK (PB1) is low
** Could be ok. I have no schematics from this programmer.
    When I start programming, I see a short low voltage at SCK.
Unfortunately I doesn't have a scope, only a voltmeter.
** That's makes it a little complicated......
    You say, the signal must be on high level. It's low. But I can program
my second Ethernut with this SP Duo without problems.
** Ok. I think the programmer is no defect.

- CPU, not connected with SP Duo 2: SCK (PB1) is low
    Should I try to pull the SCK line high, when I connect the
** Try it with 10k! You have a second board, try to compare the signals on
the two board.

programmer to the CPU?

Greetings
Andre





_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

Hi Andre,

Both Ethernuts have a low SCK line. Both programmers I've tested have a low
SCK line. One Board and both programmers work. Only on one board, the
programmer cannot enter the programming mode.
Even with SCK, pulled to high via 10k it doesn't work.

Daniel

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Daniel-378]

Daniel schrieb:

> Daniel wrote:
>
>  
>> Andre Riesberg schrieb:
>>  
>>
>>    
>>> Daniel wrote:
>>>
>>>  
>>>    
>>>
>>>      
>>>> Hi.
>>>>
>>>> While I was programming my Ethernut 1.3 with stk500.exe, I had
>>>> connected SCK (SPI Bus Serial Clock) to GND. After that I read, that
>>>> I must not do that.
>>>> Now stk500.exe tells me, that the controller "Could not enter
>>>> programming mode".
>>>>
>>>> Any advise how to fix it up?
>>>>
>>>> Thanks,
>>>> Daniel
>>>> _______________________________________________
>>>> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>>>>
>>>>
>>>>
>>>>
>>>>    
>>>>      
>>>>
>>>>        
>>> Hi Daniel,
>>>
>>> do you pull the SCK signal to GND only on the programmer or on cpu or
>>> on both?
>>>
>>> Do you have disconnected all power supplys and start again?
>>>
>>> Please make some tests:
>>> First, disconnect programmer and CPU.
>>>
>>> - Check the SCK signal at the programmer: In normal condition (no
>>> programming) the signal must be on high level.
>>> - Check the SCK signal at the CPU board. Normally you see a low level.
>>> With a 10k resistor to +5V you can pull this signal to high level.
>>> - With still disconnected board try to start programming (I use
>>> avrdude). With a scope you can see (for a short time) a lot of pulse
>>> on the SCK line.
>>>
>>> Does this work?
>>>
>>> Greeting
>>> Andre
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>>>
>>>  
>>>    
>>>
>>>      
>> Hi Andre, thanks for the answer.
>>
>> Here are the results of the tests you mentioned:
>>
>> - SP Duo 2 Programmer, only supported with Vcc & GND, not connected to
>> CPU: SCK (PB1) is low
>>    When I start programming, I see a short low voltage at SCK.
>> Unfortunately I doesn't have a scope, only a voltmeter.
>>    You say, the signal must be on high level. It's low. But I can
>> program my second Ethernut with this SP Duo without problems.
>>
>> - CPU, not connected with SP Duo 2: SCK (PB1) is low
>>    Should I try to pull the SCK line high, when I connect the
>> programmer to the CPU?
>>
>>
>> Daniel
>> _______________________________________________
>> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>>
>>
>>  
>>
>>    
> Hi Daniel,
>
> see my commends:
>
> - SP Duo 2 Programmer, only supported with Vcc & GND, not connected to
> CPU: SCK (PB1) is low
> ** Could be ok. I have no schematics from this programmer.
>     When I start programming, I see a short low voltage at SCK.
> Unfortunately I doesn't have a scope, only a voltmeter.
> ** That's makes it a little complicated......
>     You say, the signal must be on high level. It's low. But I can program
> my second Ethernut with this SP Duo without problems.
> ** Ok. I think the programmer is no defect.
>
> - CPU, not connected with SP Duo 2: SCK (PB1) is low
>     Should I try to pull the SCK line high, when I connect the
> ** Try it with 10k! You have a second board, try to compare the signals on
> the two board.
>
> programmer to the CPU?
>
> Greetings
> Andre
>
>
>
>
>
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>
> Hi Andre,
>
> Both Ethernuts have a low SCK line. Both programmers I've tested have a low
> SCK line. One Board and both programmers work. Only on one board, the
> programmer cannot enter the programming mode.
> Even with SCK, pulled to high via 10k it doesn't work.
>
> Daniel
>
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>
>  

Hello again.

Any hints what to do now? Is the board broken? Should I send it back to
egnite?

Daniel
_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Ethernut]

Hi Daniel,

Daniel wrote:

> Any hints what to do now? Is the board broken? Should I send it back to
> egnite?

Sorry, because of the quoting style this thread was hard to read. While
being short in time I chose to ignore it. Thanks to Andre for jumping
in. Andre is not egnite, but I am. Looks like I have to respond now. ;-)

However, I'm still not sure what may have happened. Let me try to give a
summary:

1. You connected the SP Duo 2 to Ethernut 1.3.
2. During programming you noticed, that you had PB1 connected to ground
by accident
3. After removing the PB1 to GND connection, programming still fails.
4. Following the advice from Andre, you noticed that PB1 is always low
in idle mode

In fact PB1 and the SP Duo's are both high impedance in idle mode.
Depending on your equipment, you may measure anything.

The shortcut to ground may have damaged the SP Duo. To compensate your
frustration a bit, egnite will send you a free replacement. Just mail
your shipping address to info at egnite dot de. If it still fails,
egnite may ask you to send in both, the programmer and your Ethernuts.

Btw. stk500.exe is probably OK and a good choice with ICCAVR. If not
using ImageCraft, I'd consider using avrdude. It is much better
supported and works very well.

Harald

P.S.: For good quoting please read
http://www.gweep.ca/~edmonds/usenet/ml-etiquette.html#SECTION00090000000000000000
_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Daniel-378]

Hi Harald,
> 1. You connected the SP Duo 2 to Ethernut 1.3.
> 2. During programming you noticed, that you had PB1 connected to ground
> by accident
> 3. After removing the PB1 to GND connection, programming still fails.
> 4. Following the advice from Andre, you noticed that PB1 is always low
> in idle mode
>  
This was exactly the way it happens.
> The shortcut to ground may have damaged the SP Duo. To compensate your
> frustration a bit, egnite will send you a free replacement. Just mail
> your shipping address to info at egnite dot de. If it still fails,
> egnite may ask you to send in both, the programmer and your Ethernuts.
>  
The programmer works fine. I have 2 Ethernuts with 2 programmers. Both
programmers work with my other Ethernut. Only the Ethernut were PB1 was
pulled to GND is not programmable.

> P.S.: For good quoting please read
> http://www.gweep.ca/~edmonds/usenet/ml-etiquette.html#SECTION0009000000000000000
Better now? ;-)


Thanks for reply,
Daniel
_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Daniel-378]

Hi Harald,

Harald Kipp schrieb:
> Btw. stk500.exe is probably OK and a good choice with ICCAVR. If not
> using ImageCraft, I'd consider using avrdude. It is much better
> supported and works very well.
>  
I tried to use avrdude but when I choose "stk500" as programmer type,
then I get the apparently well-know error "not in sync: resp=0x00". The
programmer shows SW Version 2.3. When I use choose "avr910" as
programmer type, then there is no sync error, but avrdude exits, because
"the ATMega 128 is not supported". Which programmer type should I use?

By the way, on the page "http://www.ethernut.de/de/isp/spduo.html" the
files for spduo22.enc and spduo23.enc are not correctly linked I think.


Daniel
_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Matthias Ringwald]

isn't there an stk500v2 or avrispv2? try these.

matthias

On Sep 25, 2009, at 6:15 PM, Daniel wrote:

> Hi Harald,
>
> Harald Kipp schrieb:
>> Btw. stk500.exe is probably OK and a good choice with ICCAVR. If not
>> using ImageCraft, I'd consider using avrdude. It is much better
>> supported and works very well.
>>
> I tried to use avrdude but when I choose "stk500" as programmer type,
> then I get the apparently well-know error "not in sync: resp=0x00".  
> The
> programmer shows SW Version 2.3. When I use choose "avr910" as
> programmer type, then there is no sync error, but avrdude exits,  
> because
> "the ATMega 128 is not supported". Which programmer type should I use?
>
> By the way, on the page "http://www.ethernut.de/de/isp/spduo.html" the
> files for spduo22.enc and spduo23.enc are not correctly linked I  
> think.
>
>
> Daniel
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Ethernut]

Daniel wrote:

> The programmer works fine. I have 2 Ethernuts with 2 programmers. Both
> programmers work with my other Ethernut. Only the Ethernut were PB1 was
> pulled to GND is not programmable.

Oh, I missed that one. In that case it is quite obvious that the
Ethernut board is broken. Please send it to egnite for repair. Make sure
to use proper ESD packing.

Harald

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion