Re: [Usbpicprog-technical] loading PIC data from Piklab XML files

[Frans S. <fra...@gm...>]

Hi Francesco,
> Hi Frans,
>
> Frans Schreuder ha scritto:
>   
>>> PS: do you think it would be better to create a separate branch for 
>>> experimenting with the XML approach or should I commit the changes directly in 
>>> trunk?
>>>
>>>   
>>>       
>> Well, I think this is something we can do in the trunk version, with the 
>> threaded version I was afraid that it could maybe do something to the 
>> hardware stability, so I thought that would be safer.
>>     
> I've implemented most of the basic stuff... however the changes are quite big 
> and unfortunately I can't seem to get my PIC16F84A correctly programmed anymore now.
>
> Hardware::writeCode() returns -4 now and the programming operations fails with a 
> log message:
>     LogFromThread(wxLOG_Error, _("Verify error while writing code memory"));
>
>
> Unfortunately I'm not very confident with the Hardware class code and I don't 
> understand why it fails now. It must have something to do with the changes I did 
> to PicType class obviously; could it be something related to the fact that (at 
> least for now) the Pic::ConfigFlags[] array is simply set to zero in my local 
> copy (because those info are not in piklab XML files)?
>
> In any case I fear that committing my modifications in the trunk may result in 
> "programming failures" for many other PIC types; this also because some data in 
> the Piklab XML files seems not correct to me... e.g. PIC16F84A's config memory 
> is reported to start at 0x2007 and to end at 0x2007: I corrected it to report 
> the end at 0x2009, but other small details for other PICs may have to be fixed, too.
>
> So I think it would be better to create a new branch and commit there. Unless 
> you think we can fix the (new) bugs in trunk directly.
>   
I think that's a good idea, let's make a branch, also if small things 
are still missing and people want to use the latest snapshot, they can 
still co the trunk.
Though I think it could also be something which I did in the firmware.
I can't find a way how configflags could damage writing code memory.
Do you know whether the process quits immediately or that it programs 
well for some time?
>   
>> Do you know if there is something like an editor for those xml files? or 
>> will it just be a general text editor?
>>     
> I use the same text editor (Kate) I use for normal CPP/H files :)
> Nothing special is required ;)
>   
Ok, I'll just have to get used to the xml syntax then!

Frans