Re: [Usbpicprog-technical] config word programming

[Gábor H. <gab...@gm...>]

Hi Frans.

Thanks for the hint, to check this, I will have to build a charge pump, as
you did in usbpicprog.

Regards,
Gabor

On Wed, Oct 17, 2012 at 10:47 AM, Frans Schreuder
<fra...@gm...>wrote:

>  Hi Gabor,
>
> It could also be the MCLRE bit, disabling the MCLR pin, this requires
> another programming mode entry.
>
> Regards,
>
> Frans
>
> On 10/17/2012 09:00 AM, Gábor Hornyák wrote:
>
> Hi,
>
>  I will check the specs, but I am afraid this is something different,
> because I can not even read the config words, including the device ID,
> which I assume should be readable even with code protection enabled.
>
>  Thanks,
> Gabor
>
> On Wed, Oct 17, 2012 at 8:07 AM, Frans Schreuder <fra...@gm...
> > wrote:
>
>> Hi,
>>
>> You probagbly haven't bricked the pic but programmed the code proteection
>> bits by accident. With these bits enabled it is also more difficult to eras
>> the pic, check the programming specification for the procedure.
>>
>> Regards,
>>
>> Frans
>>
>>  Op 16 okt. 2012 23:04 schreef "Gábor Hornyák" <gab...@gm...>
>> het volgende:
>>
>> >
>> > Hi Everyone,
>> >
>> > My question is not strictly related to usbpicprog, but I am hoping that
>> someone here has faced similar issue.
>> > As a 'side' project of an other project, I thought I create a simple
>> programmer to PIC18F46K22 (I have a demo board with PIC18F45K22 equipped
>> with bootloader, which I am using for programming). Everything went fine -
>> I was able to read/write program memory and read config words - until I
>> reached the point where config words had to be written. After I created it
>> and tested with a PIC, it seems that I bricked the mcu, because from that
>> point, I can not do anything with the PIC (always read zeroes for all
>> addresses).
>> > I don't know what could have went wrong, since config word programming
>> differs only in a few things from program memory programming (which works
>> fine, and the fact is that I actually seem to have bricked two PICs
>> already). My concrete question is: could this problem have been caused by
>> trying to write config BYTES separately (not as words)? Has anyone faced
>> similar problem?
>> >
>> > Thanks and Regards,
>> > Gabor
>> >
>>  >
>> ------------------------------------------------------------------------------
>> > Everyone hates slow websites. So do we.
>> > Make your web apps faster with AppDynamics
>> > Download AppDynamics Lite for free today:
>> > http://p.sf.net/sfu/appdyn_sfd2d_oct
>> > _______________________________________________
>> > Usbpicprog-technical mailing list
>> > Usb...@li...
>> > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_sfd2d_oct
>> _______________________________________________
>> Usbpicprog-technical mailing list
>> Usb...@li...
>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>>
>>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:http://p.sf.net/sfu/appdyn_sfd2d_oct
>
>
>
> _______________________________________________
> Usbpicprog-technical mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>
>