Re: hp49g+ -- Problem with bad libs in second port
- From: Jean-Yves Avenard <me@xxxxxxxxxxx>
- Date: Sat, 23 Jul 2005 10:04:18 +1000
awilpert wrote:
Thanks for the clarification Jean-Yves, I knew PINIT was used to solve some port problems, but I did not know exactly which, that is why I reported that PINIT was not working in my case.
I did what you adviced ( 1 4046 + 1 ->TAG DUP DETACH PURGE ), but
Sorry it should be: 1 4096 + 2 ->TAG DUP DETACH PURGE
In fact this should work for any library with a number < 256: [lib_number] 4096 + [port_number] ->TAG DUP DETACH PURGE
JY .
- Follow-Ups:
- Re: hp49g+ -- Problem with bad libs in second port
- From: awilpert
- Re: hp49g+ -- Problem with bad libs in second port
- References:
- hp49g+ -- Problem with bad libs in second port
- From: awilpert
- Re: hp49g+ -- Problem with bad libs in second port
- From: Veli-Pekka Nousiainen
- Re: hp49g+ -- Problem with bad libs in second port
- From: awilpert
- Re: hp49g+ -- Problem with bad libs in second port
- From: Veli-Pekka Nousiainen
- Re: hp49g+ -- Problem with bad libs in second port
- From: awilpert
- Re: hp49g+ -- Problem with bad libs in second port
- From: Jean-Yves Avenard
- Re: hp49g+ -- Problem with bad libs in second port
- From: awilpert
- hp49g+ -- Problem with bad libs in second port
- Prev by Date: Re: confused about ARM
- Next by Date: Re: To HPGCC team: a bug has been isolated
- Previous by thread: Re: hp49g+ -- Problem with bad libs in second port
- Next by thread: Re: hp49g+ -- Problem with bad libs in second port
- Index(es):