gnupic: Thread: Looking for suggestions on adding enhanced 16F instructions to gpsim

I'm moving into working with microchip's enhanced 16F chips such as the
16F1939 and the 12F1822. The enhanced architecture has a double handful of
new features:

- 32 banks
- 14 new instructions
- Linear address space for general purpose ram
- Program address space addressibility from the FSR/INDF registers
- A pair of FSR/INDF registers instead of one

It looks like a tactical backpatch of the 16F architecture with some 18F
features.

The question is what is the most expedient way to add this set of features
to gpsim?

Any suggestions welcome.

BAJ

-- 
Byron A. Jeff
Department Chair: IT/CS/CNET
College of Information and Mathematical Sciences
Clayton State University
http://cims.clayton.edu/bjeff

Is it really needed to work on GNU version?
Microchip is publishing for free MPLabX that contains support for ALL chips
and on ALL platforms with their excellent simulator and all hardware debug
support.
I don’t see myself need Gpasm and GxxTools anymore !!!

Regards

-----Message d'origine-----
De : Byron Jeff ####@####.#### 
Envoyé : mercredi 5 janvier 2011 17:42
À : ####@####.####
Objet : Looking for suggestions on adding enhanced 16F instructions to gpsim

I'm moving into working with microchip's enhanced 16F chips such as the
16F1939 and the 12F1822. The enhanced architecture has a double handful of
new features:

- 32 banks
- 14 new instructions
- Linear address space for general purpose ram
- Program address space addressibility from the FSR/INDF registers
- A pair of FSR/INDF registers instead of one

It looks like a tactical backpatch of the 16F architecture with some 18F
features.

The question is what is the most expedient way to add this set of features
to gpsim?

Any suggestions welcome.

BAJ

--
Byron A. Jeff
Department Chair: IT/CS/CNET
College of Information and Mathematical Sciences Clayton State University
http://cims.clayton.edu/bjeff

---------------------------------------------------------------------
To unsubscribe, e-mail: ####@####.####
For additional commands, e-mail: ####@####.####

I have not installed and I will not install MPLAB X, the problems I see
are many.

http://ww1.microchip.com/downloads/mplab/X_Beta/installer.html

a - using java ... too heavy and owner.
b - there is no source code is proprietary and closed source installer
is a. bin "mplabxidebeta32.bin"
c - to install this. bin is supposed to be root and be installed in
/usr/bin so it is a security risk for the entire system.

For now use MPLAB under wine, this mplab only lives in my home and
install it with wine it does not take root.
I dream of something made in python for all platforms .... shame that
just a dream of mine.

Greetings
Néstor A. Marchesini

El 08/01/11 05:38, Support, Pocket MicroTechnics escribió:
> Is it really needed to work on GNU version?
> Microchip is publishing for free MPLabX that contains support for ALL chips
> and on ALL platforms with their excellent simulator and all hardware debug
> support.
> I don’t see myself need Gpasm and GxxTools anymore !!!
>
> Regards
>
> -----Message d'origine-----
> De : Byron Jeff ####@####.#### 
> Envoyé : mercredi 5 janvier 2011 17:42
> À : ####@####.####
> Objet : Looking for suggestions on adding enhanced 16F instructions to gpsim
>
> I'm moving into working with microchip's enhanced 16F chips such as the
> 16F1939 and the 12F1822. The enhanced architecture has a double handful of
> new features:
>
> - 32 banks
> - 14 new instructions
> - Linear address space for general purpose ram
> - Program address space addressibility from the FSR/INDF registers
> - A pair of FSR/INDF registers instead of one
>
> It looks like a tactical backpatch of the 16F architecture with some 18F
> features.
>
> The question is what is the most expedient way to add this set of features
> to gpsim?
>
> Any suggestions welcome.
>
> BAJ
>
> --
> Byron A. Jeff
> Department Chair: IT/CS/CNET
> College of Information and Mathematical Sciences Clayton State University
> http://cims.clayton.edu/bjeff

Of course it is still necessary. At least as long as the Microchip software
is not released as open source.

For "ALL platforms" is a bold statement for something that is not distributed
as source. My system for example is a LFS system: http://www.linuxfromscratch.org/
I dont think that Microchip supports this platform.

On Saturday 08 January 2011, Support, Pocket MicroTechnics wrote:
> Is it really needed to work on GNU version?
> Microchip is publishing for free MPLabX that contains support for ALL chips
> and on ALL platforms with their excellent simulator and all hardware debug
> support.
> I don’t see myself need Gpasm and GxxTools anymore !!!
> 
> Regards
> 
> -----Message d'origine-----
> De : Byron Jeff ####@####.#### 
> Envoyé : mercredi 5 janvier 2011 17:42
> À : ####@####.####
> Objet : Looking for suggestions on adding enhanced 16F instructions to gpsim
> 
> I'm moving into working with microchip's enhanced 16F chips such as the
> 16F1939 and the 12F1822. The enhanced architecture has a double handful of
> new features:
> 
> - 32 banks
> - 14 new instructions
> - Linear address space for general purpose ram
> - Program address space addressibility from the FSR/INDF registers
> - A pair of FSR/INDF registers instead of one
> 
> It looks like a tactical backpatch of the 16F architecture with some 18F
> features.
> 
> The question is what is the most expedient way to add this set of features
> to gpsim?
> 
> Any suggestions welcome.
> 
> BAJ
> 
> --
> Byron A. Jeff
> Department Chair: IT/CS/CNET
> College of Information and Mathematical Sciences Clayton State University
> http://cims.clayton.edu/bjeff
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 
> 



-- 
Holger Oehm ####@####.####
KeyID: B50E51A9, 1024bit at http://www.holger-oehm.de/public-key.asc
Fingerprint: E92A 5C2C 497A 44ED 23C0  DB66 1DD9 3EF7 B50E 51A9

Is there a way to use the tools (especially the assembler) without the
silly IDE environment?

Support, Pocket MicroTechnics writes:
>Is it really needed to work on GNU version?
>Microchip is publishing for free MPLabX that contains support for ALL chips
>and on ALL platforms with their excellent simulator and all hardware debug
>support.
>I don’t see myself need Gpasm and GxxTools anymore !!!
>
>Regards
>
>-----Message d'origine-----
>De : Byron Jeff ####@####.#### 
>Envoyé : mercredi 5 janvier 2011 17:42
>À : ####@####.####
>Objet : Looking for suggestions on adding enhanced 16F instructions to gpsim
>
>I'm moving into working with microchip's enhanced 16F chips such as the
>16F1939 and the 12F1822. The enhanced architecture has a double handful of
>new features:
>
>- 32 banks
>- 14 new instructions
>- Linear address space for general purpose ram
>- Program address space addressibility from the FSR/INDF registers
>- A pair of FSR/INDF registers instead of one
>
>It looks like a tactical backpatch of the 16F architecture with some 18F
>features.
>
>The question is what is the most expedient way to add this set of features
>to gpsim?
>
>Any suggestions welcome.
>
>BAJ
>
>--
>Byron A. Jeff
>Department Chair: IT/CS/CNET
>College of Information and Mathematical Sciences Clayton State University
>http://cims.clayton.edu/bjeff
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
>

-- 
As we enjoy great advantages from the inventions of others, we should
be glad of an opportunity to serve others by any invention of ours;
and this we should do freely and generously. (Benjamin Franklin)

> For now use MPLAB under wine, this mplab only lives in my home and
> install it with wine it does not take root.
> I dream of something made in python for all platforms .... shame that
> just a dream of mine.
> 
> Greetings
> Néstor A. Marchesini
> 

Hi Nestor,

which programmer/debugger do you use ? Some time ago I tried that but my Pickit2 did not work under Wine.

Regards,
Vasek

On Sun, Jan 09, 2011 at 07:35:49AM -0500, Vaclav Peroutka wrote:
> > For now use MPLAB under wine, this mplab only lives in my home and
> > install it with wine it does not take root.
> > I dream of something made in python for all platforms .... shame that
> > just a dream of mine.
> > 
> > Greetings
> > Néstor A. Marchesini
> > 
> 
> Hi Nestor,
> 

> which programmer/debugger do you use ? Some time ago I tried that but my
> Pickit2 did not work under Wine.

I'm back with some comments.

- MPLabX is only in beta along with the other issues outlined. As a Linux
  user, I haven't used an actual Microchip product in over 15 years.
  The gputils tools along with DIY programmers, software, and bootloaders
  have been quite sufficient for all of my development needs. 

- You Pickit2 can be programmed using pk2cmd, which is a native Linux/Mac
  application for programming.

- I don't use Wine because Wine simply cannot keep up with all of the
  changes Microsoft keeps introducing. I've tried on and off for well
  over 15 years to run various applications under Wine. Rarely does it
  "just work". 

- gpsim is an excellent simulator. In some respects it is better than the
  MPLAB simulator because it works very hard to capture every aspect of the
  chip including I/O and external peripherals. It is a tool that I have
  used successfully in the past, so why would I want to switch?

- Also there is a different mindset between Unix style and Windows type
  applications. Windows apps have an extremely heavy GUI focus. Much of
  the time it gets in the way and inhibits scripting or automation of
  tasks. gpsim does it right offering both GUI and CLI access so that
  the developer can choose the appropriate level for the task at hand. 
  Another difference is that virtually every Windows style development
  tool is in the IDE model, where every possible tool and the kitchen
  sink are all rolled up into one humongous application. I took a look
  at MPLabX and it looks like the Titanic. The Unix approach of single
  tools for single tasks facilitates mix and match. I can use my editor
  my assembler, my linker, my simulator, instead of being coerced into
  the tools the IDE developer thinks that I should use. I've been a
  Unix guy for most of my adult life. I do actually know why I'm not
  a Windows user.

- Finally I did come across a post in the gpsim development mailing list,
  which on second thought is where my query should have gone in the first
  place, that describes the process of adding new processors to the 
  simulator. For posterity it can be found here:

  http://sourceforge.net/mailarchive/message.php?msg_id=19542298

Hope this helps,

BAJ

> 
> Regards,
> Vasek
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 

-- 
Byron A. Jeff
Department Chair: IT/CS/CNET
College of Information and Mathematical Sciences
Clayton State University
http://cims.clayton.edu/bjeff

On 1/9/2011 8:17 AM, Byron Jeff wrote:

> - Finally I did come across a post in the gpsim development mailing list,
>   which on second thought is where my query should have gone in the first
>   place, that describes the process of adding new processors to the
>   simulator. For posterity it can be found here:
>
>   http://sourceforge.net/mailarchive/message.php?msg_id=19542298

I keep wanting to get back to gpsim, but life seems to get in the way...

Adding new instructions is relatively straight forward. Sometimes the
intricacies of the interaction between the processor registers can make
testing and validation challenging. So the hard part is creating thorough 
regression tests.

Scott

To program I uso pk2cmd.

$ eix -Ic pk2cmd
[I] dev-embedded/pk2cmd (1.20@01/12/10): An application for working with
the Microchip PicKit2 PIC programmer

I'm using wine at the moment because I'm in a development with a 18F6520
which is not supported by gpsim.

$ eix -Ic wine
[I] app-emulation/wine (1.3.6@01/12/10): free implementation of
Windows(tm) on Unix

Of course, with gentoo testing amd64 for here.

Regards
Néstor A. Marchesini

El 09/01/11 09:35, Vaclav Peroutka escribió:
>> For now use MPLAB under wine, this mplab only lives in my home and
>> install it with wine it does not take root.
>> I dream of something made in python for all platforms .... shame that
>> just a dream of mine.
>>
>> Greetings
>> Néstor A. Marchesini
> Hi Nestor,
>
> which programmer/debugger do you use ? Some time ago I tried that but my Pickit2 did not work under Wine.
>
> Regards,
> Vasek

For programming, it is quite clear. I use pk2cmd, too. But what about debugging ? I did not find any tool which does debugging of PICs on Linux...

That is main reason why I am silently moving to Cortex core.

Regards,
Vasek

> ----------------------------------------
> To program I uso pk2cmd.
> 
> $ eix -Ic pk2cmd
> [I] dev-embedded/pk2cmd (1.20@01/12/10): An application for working with
> the Microchip PicKit2 PIC programmer
> 
> I'm using wine at the moment because I'm in a development with a 18F6520
> which is not supported by gpsim.
> 
> $ eix -Ic wine
> [I] app-emulation/wine (1.3.6@01/12/10): free implementation of
> Windows(tm) on Unix
> 
> Of course, with gentoo testing amd64 for here.
> 
> Regards
> Néstor A. Marchesini
> 
> El 09/01/11 09:35, Vaclav Peroutka escribió:
> >> For now use MPLAB under wine, this mplab only lives in my home and
> >> install it with wine it does not take root.
> >> I dream of something made in python for all platforms .... shame that
> >> just a dream of mine.
> >>
> >> Greetings
> >> Néstor A. Marchesini
> > Hi Nestor,
> >
> > which programmer/debugger do you use ? Some time ago I tried that but my
> Pickit2 did not work under Wine.
> >
> > Regards,
> > Vasek