Bug#387185: picprog: Fails to detect programmer in amd64

[Jan Wagemakers]

Jaakko Hyvätti schreef:

> The default is changed now.
> 
> --nordtsc  is the default
> --rdtsccan be used for speed
> 
> Jaakko

I have created a debian-package for picprog 1.8.3. It can be found at
. I hope it will be uploaded to the
Debian repository soon.


-- 
Met vriendelijke groetjes - Jan Wagemakers -

... Boy, everyone is stupid except me.  --Homer Simpson


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#387185: picprog: Fails to detect programmer in amd64

[Jaakko Hyvätti]

The default is changed now.

--nordtsc  is the default
--rdtsccan be used for speed

Jaakko

On Thu, 28 Sep 2006, Steinar H. Gunderson wrote:


On Mon, Sep 25, 2006 at 10:49:59PM +0200, Jan Wagemakers wrote:

When I try to download this file I get an error:

| Forbidden
|
| You don't have permission to access /~jaakko/pic/picprog-1.8.2.tar.gz on this 
server.
| Apache/2.2.2 (Fedora) Server at hyvatti.iki.fi Port 80


It should be OK now, it seems.

So, essentially we need an upload of the new upstream version? I'm somewhat
disappointed --disable-rdtsc isn't the default, but OK, upstream obviously
seems to think otherwise...

/* Steinar */




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#387185: picprog: Fails to detect programmer in amd64

[Jaakko Hyvätti]

Good point, I'll switch that default the other way, and will re-release 
1.8.2 today, or 1.8.3.  I have no time for this to research this fully, so 
the working defaults make sense and I'll put --enable-rdtsc for those in 
need for speed.


On Thu, 28 Sep 2006, Steinar H. Gunderson wrote:


On Mon, Sep 25, 2006 at 10:49:59PM +0200, Jan Wagemakers wrote:

When I try to download this file I get an error:

| Forbidden
|
| You don't have permission to access /~jaakko/pic/picprog-1.8.2.tar.gz on this 
server.
| Apache/2.2.2 (Fedora) Server at hyvatti.iki.fi Port 80


It should be OK now, it seems.

So, essentially we need an upload of the new upstream version? I'm somewhat
disappointed --disable-rdtsc isn't the default, but OK, upstream obviously
seems to think otherwise...

/* Steinar */




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#387185: picprog: Fails to detect programmer in amd64

[Jan Wagemakers]

Steinar H. Gunderson schreef:

>> When I try to download this file I get an error:
>> | Forbidden You don't have permission to access
>> | /~jaakko/pic/picprog-1.8.2.tar.gz on this server. Apache/2.2.2 (Fedora)
>> | Server at hyvatti.iki.fi Port 80
> It should be OK now, it seems.

Yes, Jaakko has fixed this.

> So, essentially we need an upload of the new upstream version?

Yesterday, I have created a new debian-package. At the moment it is
available at . I'll
contact my previous sponsor (Aníbal Monsalve Salazar) to ask if he can
upload it to Debian.


-- 
Met vriendelijke groetjes - Jan Wagemakers -

... Wij zijn allemaal stripfiguren getekend door het leven


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#387185: picprog: Fails to detect programmer in amd64

[Steinar H. Gunderson]

On Mon, Sep 25, 2006 at 10:49:59PM +0200, Jan Wagemakers wrote:
> When I try to download this file I get an error:
> 
> | Forbidden
> | 
> | You don't have permission to access /~jaakko/pic/picprog-1.8.2.tar.gz on 
> this server.
> | Apache/2.2.2 (Fedora) Server at hyvatti.iki.fi Port 80

It should be OK now, it seems.

So, essentially we need an upload of the new upstream version? I'm somewhat
disappointed --disable-rdtsc isn't the default, but OK, upstream obviously
seems to think otherwise...

/* Steinar */
-- 
Homepage: http://www.sesse.net/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#387185: picprog: Fails to detect programmer in amd64

[Jan Wagemakers]

Jaakko Hyvätti schreef:

> I implemented --nordtsc and --slow options, and put out 1.8.2 version..
> http://www.iki.fi/hyvatti/pic/picprog.html

When I try to download this file I get an error:

| Forbidden
| 
| You don't have permission to access /~jaakko/pic/picprog-1.8.2.tar.gz on this 
server.
| Apache/2.2.2 (Fedora) Server at hyvatti.iki.fi Port 80


-- 
Met vriendelijke groetjes - Jan Wagemakers -

 - Debian GNU/Linux testing/unstable - Up : 74 days 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#387185: picprog: Fails to detect programmer in amd64

[Jaakko Hyvätti]

Hi,

Thanks Jan for collecting feedback on this and debugging things, as well 
as thanks for all users for interest in getting it to work.


I guess any variable clockrates very common in laptops and recent 
AMD64 cpu's will also not work.


I implemented --nordtsc and --slow options, and put out 1.8.2 version..

http://www.iki.fi/hyvatti/pic/picprog.html

I just tested them once, so .. they may not work well.  Simple changes 
though.


I hope maybe next summer I'll have more time to use on this :-)  As it is, 
when it works it is a good enough solution for many, and a starting point 
to microcontroller hobby.


Jaakko


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#387185: picprog: Fails to detect programmer in amd64

[Jan Wagemakers]

Jaakko,

I have recently received this bug-report about picprog (Debian).


Let me summerize what we have found so far.

- When asking around various people have confirmed that picprog fails on the
  64-bit amd64 platform.
- Altering the delay-routines so that picprog thinks the CPU is ten times
  faster seems to solve the problem.
- Disabling the use of the RDTSC-instruction also seems to solve the
  problem, but not for everybody.
- On my old laptop, picprog works at 600Mhz, but not at 750Mhz. By disabling
  the use of RDTSC, picprog works without a problem at 750Mhz on my laptop.
  (Note, my laptop is not an amd64 ;-) )

To me it seems that disabling the use of RDTSC is a good idea. Any comments?
Also, maybe we can try to add an extra "delay"-option to picprog so that
when picprog fails to run on some hardware, people can use this option to
make picprog run more slowy.


-- 
Met vriendelijke groetjes - Jan Wagemakers -

... Fidonet : 2:292/100.19 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#387185: picprog: Fails to detect programmer in amd64

[Steinar H. Gunderson]

On Sun, Sep 17, 2006 at 01:25:01AM +0200, Jan Wagemakers wrote:
> Normally picprog use the RDTSC instruction on x86_64/i386 platforms. By
> disabling this, picprog makes use of the delay-routines for platforms that
> don't have this RDTSC instruction.

This should be done regardless of platform; RDTSC is a _very_ _poor_ choice
for reliable timing and should not be used except in very controlled
environments. The most important reason is that you might have CPU frequency
scaling going on; suddenly your CPU frequency can move from 150 MHz to 1.4
GHz, and in that case, timing on the number of cycles is not a very good
idea...

/* Steinar */
-- 
Homepage: http://www.sesse.net/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#387185: picprog: Fails to detect programmer in amd64

[Fernando M. Maresca]

On Sun, Sep 17, 2006 at 01:25:01AM +0200, Jan Wagemakers wrote:
> Fernando M. Maresca schreef:
> 
> > Yes, it works. Thank you both,
> 
> Ok, I have taken a closer look to the source of picprog and think that I
> have found a good solution.
> 
> Can you test if the following works for you?
> 
> In the file picport.h at 53 you find:
> 
> #if defined(__x86_64__) || defined(__i386__)
> #define RDTSC_WORKS
> #endif
> 
> Change this to:
> 
> //#if defined(__x86_64__) || defined(__i386__)
> //#define RDTSC_WORKS
> //#endif
> 
> Normally picprog use the RDTSC instruction on x86_64/i386 platforms. By
> disabling this, picprog makes use of the delay-routines for platforms that
> don't have this RDTSC instruction.
> 
> Maarten Blomme has test this on his slackware amd64 box and it fixes the
> problem. It also fixes the problem that I have on my laptop¹.
> 
> So, I plan to create a new package with RDTSC disabled, but before doing
> that I like to know if it also fix your problem.

Please forgive about the delay in this answer, there was some trouble
qith mt isp.

With this patch, it seems to randomly detects the pic and read, but for
the most time it fails:

homero:/usr/src/picprog-1.8.1# ./picprog -o /tmp/o.hex --pic /dev/ttyS2
Picprog version 1.8.1, Copyright © 2006 Jaakko Hyvätti
<[EMAIL PROTECTED]>
Picprog comes with ABSOLUTELY NO WARRANTY; for details
type `picprog --warranty'.  This is free software,
and you are welcome to redistribute it under certain conditions;
type `picprog --copying' for details.

/dev/ttyS2: id 0x0560: detected pic16f84a version 0x00
Device pic16f84a, program memory: 1024, data memory: 64.
Reading program memory,
/dev/ttyS2:PIC programmer missing or chip fault
0007:unable to read pic

With the previous patch works fine all the times.
Regards,



-- 
Fernando M. Maresca
- - - - - - - - - - - - -
Cel: 221 15 545 8196
Tel: 221 489 0466

Bug#387185: picprog: Fails to detect programmer in amd64

[Jan Wagemakers]

Fernando M. Maresca schreef:

> Yes, it works. Thank you both,

Ok, I have taken a closer look to the source of picprog and think that I
have found a good solution.

Can you test if the following works for you?

In the file picport.h at 53 you find:

#if defined(__x86_64__) || defined(__i386__)
#define RDTSC_WORKS
#endif

Change this to:

//#if defined(__x86_64__) || defined(__i386__)
//#define RDTSC_WORKS
//#endif

Normally picprog use the RDTSC instruction on x86_64/i386 platforms. By
disabling this, picprog makes use of the delay-routines for platforms that
don't have this RDTSC instruction.

Maarten Blomme has test this on his slackware amd64 box and it fixes the
problem. It also fixes the problem that I have on my laptop¹.

So, I plan to create a new package with RDTSC disabled, but before doing
that I like to know if it also fix your problem.


[1]

 
-- 
Met vriendelijke groetjes - Jan Wagemakers -

 - Debian GNU/Linux testing/unstable - Up : 65 days 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#387185: picprog: Fails to detect programmer in amd64

[Fernando M. Maresca]

On Sat, Sep 16, 2006 at 09:35:16AM +0200, Jan Wagemakers wrote:
> Jan Wagemakers schreef:
> [...]
> Can you compile picprog yourself with this patch² to test if this solves
> your problem? I'll contact Jaakko (upstream) when this patch solves your
> problem to ask for a real solution.
> 
> [1] 
> [2] 
> In picport.cc change the line:
> 
> mhz = tmp; 
> 
> by
> 
> mhz = tmp * 10;
Yes, it works.
Thank you both,

-- 
Fernando M. Maresca
- - - - - - - - - - - - -
Cel: 221 15 545 8196
Tel: 221 489 0466

Bug#387185: picprog: Fails to detect programmer in amd64

[Jan Wagemakers]

Jan Wagemakers schreef:

> I will ask around on some pic-related mailingslist to check if others with
> an amd64 see the same problem. 

I have received an interesting mail¹ from "Maarten Blomme". I'll summerize
it here because it is written in the dutch language.

Maarten says that when he tries to use picprog on his amd64 64bit-mode
slackware box it most of the time fails but sometimes it works.

Maarten also says that when he alter one line in picport.cc² which makes
picprog think that his PC is ten times faster and makes picprog running at a
very slow rate the problem disappears and it works without a problem.

Can you compile picprog yourself with this patch² to test if this solves
your problem? I'll contact Jaakko (upstream) when this patch solves your
problem to ask for a real solution.



[1] 
[2] 
In picport.cc change the line:

mhz = tmp; 

by

mhz = tmp * 10; 


-- 
Met vriendelijke groetjes - Jan Wagemakers -

... When we speak of free software, we are referring to freedom, not price.
  -- GNU GENERAL PUBLIC LICENSE Version 2, June 1991


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#387185: picprog: Fails to detect programmer in amd64

[Jan Wagemakers]

Fernando M. Maresca schreef:

>>> picprog does not detect the chip in the programmer in my amd64 unstable
>>> box. I'm using the programmer from the package docs.
>> [...]
>>> In another box running 32bit unstable picprog works fine:
>> Are you sure that the problem is amd64 related?
>> Can you check the voltage of your serial port? JDM-style programmers don't
>> work on 'low-voltage' serial ports.
> There are three serial ports in my amd64 box; the integrated one, and a
> two port pci card. picprog does not work with anyone of them, and all of
> them have similar voltages.

> In both cases, the pulses in the DTR line are about 12v of amplitud;

Ok, the voltage of your serial port is not the problem. 

I will ask around on some pic-related mailingslist to check if others with
an amd64 see the same problem. 


-- 
Met vriendelijke groetjes - Jan Wagemakers -

... To alcohol, the cause of, 
and solution to, all of life's problems.  --Homer Simpson


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#387185: picprog: Fails to detect programmer in amd64

[Fernando M. Maresca]

On Wed, Sep 13, 2006 at 05:59:13PM +0200, Jan Wagemakers wrote:
> Fernando M. Maresca schreef:
> 
> > picprog does not detect the chip in the programmer in my amd64 unstable
> > box. I'm using the programmer from the package docs.
> 
> [...]
> 
> > In another box running 32bit unstable picprog works fine:
> 
> Are you sure that the problem is amd64 related?
> Can you check the voltage of your serial port? JDM-style programmers don't
> work on 'low-voltage' serial ports.
There are three serial ports in my amd64 box; the integrated one, and a
two port pci card. picprog does not work with anyone of them, and all of
them have similar voltages.
> 
> For example here picprog works without a problem on my normal PC, but
> doesn't work on my laptop because the voltage of the serial port of my
> laptop¹ is not high enough.
I've examined the programmer with the osciloscope, and the amplitude of 
the pulses are about the same with both boxes (the amd64 and the 32bit
one).
In both cases, the pulses in the DTR line are about 12v of amplitud;
there area burst in the read operation from the 32bit box, but only two
or three pulses with amd64.
The difference between ports voltages are about 0.5v in the worst case.

Let me know if I can help you in any way.
Thank you,

-- 
Fernando M. Maresca
- - - - - - - - - - - - -
Cel: 221 15 545 8196
Tel: 221 489 0466

Bug#387185: picprog: Fails to detect programmer in amd64

[Jan Wagemakers]

Fernando M. Maresca schreef:

> picprog does not detect the chip in the programmer in my amd64 unstable
> box. I'm using the programmer from the package docs.

[...]

> In another box running 32bit unstable picprog works fine:

Are you sure that the problem is amd64 related?
Can you check the voltage of your serial port? JDM-style programmers don't
work on 'low-voltage' serial ports.

For example here picprog works without a problem on my normal PC, but
doesn't work on my laptop because the voltage of the serial port of my
laptop¹ is not high enough.

> Can anyone check this?

I can not test it because I don't have a amd64 PC.


[1] 

-- 
Met vriendelijke groetjes - Jan Wagemakers -

... I'm no missionary! I don't even believe in Jebus!--Homer Simpson


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#387185: picprog: Fails to detect programmer in amd64

[Fernando M. Maresca]

Package: picprog
Version: 1.8.1-3
Severity: grave
Justification: renders package unusable


picprog does not detect the chip in the programmer in my amd64 unstable
box. I'm using the programmer from the package docs.


homero:~# picprog --pic /dev/ttyS0 --output o.hex
Picprog version 1.8.1, Copyright © 2006 Jaakko Hyvätti
<[EMAIL PROTECTED]>
Picprog comes with ABSOLUTELY NO WARRANTY; for details
type `picprog --warranty'.  This is free software,
and you are welcome to redistribute it under certain conditions;
type `picprog --copying' for details.

CPU clock speed: 1800 MHz
/dev/ttyS0:PIC programmer missing or chip fault
/dev/ttyS0:2006:unable to read pic device id

In another box running 32bit unstable picprog works fine:

[EMAIL PROTECTED]:~$ picprog --output o.hex --pic /dev/ttyS0
Picprog version 1.8.1, Copyright ? 2006 Jaakko Hyv?tti
<[EMAIL PROTECTED]>
Picprog comes with ABSOLUTELY NO WARRANTY; for details
type `picprog --warranty'.  This is free software,
and you are welcome to redistribute it under certain conditions;
type `picprog --copying' for details.

CPU clock speed: 908 MHz
/dev/ttyS0: id 0x0560: detected pic16f84a version 0x00
Device pic16f84a, program memory: 1024, data memory: 64.
Reading program memory,
reading data memory,
reading id words,
reading fuses,
done.

Can anyone check this?
Thanks,

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-fer
Locale: LANG=es_AR, LC_CTYPE=es_AR (charmap=ISO-8859-1)

Versions of packages picprog depends on:
ii  libc62.3.6.ds1-4 GNU C Library: Shared libraries
ii  libgcc1  1:4.1.1-13  GCC support library
ii  libstdc++6   4.1.1-13The GNU Standard C++ Library v3

picprog recommends no packages.

-- no debconf information