Re: [M100] MVT100 update

[Greg Swallow]

Hey Steve,

Put me down for one as well.

GregS <><

Jul 17, 2020 3:27:51 PM Stephen Adolph :

> Hey all,
> 
> Just a quick note to say  I have some progress to report on the MVT100 video 
> adapter.  Boards are back finally and they look to be fine.
> 
> I have some work to do to sort out how to program the PIC correctly.
> 
> Once that is done I will be able to send out the kits to those who let me 
> know they were interested in such.
> 
> I'll post some pics of the finished product + additional info at the wiki.
> 
> cheers
> 
> Steve
> 

Re: [M100] MVT100 update

[Kevin Slater]

Steve,
Well of course I'm in for one of those as well!!

Looking forward to it!

Thanks,
Kevin

> On 07/17/2020 5:27 PM Stephen Adolph  wrote:
> 
> 
> Hey all,
> Just a quick note to say  I have some progress to report on the MVT100 
> video adapter.  Boards are back finally and they look to be fine.
> I have some work to do to sort out how to program the PIC correctly.
> 
> Once that is done I will be able to send out the kits to those who let me 
> know they were interested in such.
> 
> I'll post some pics of the finished product + additional info at the wiki.
> cheers
> Steve
> 
> 
> 

Re: [M100] PIC32MX (off topic but related!)

[B4 Me100]

One thing I forgotŠ If you are using the free/unlicensed version then there
is no optimization.  It could be the VT100 app was compiled with a licensed
version of the compiler with some level of optimization.

From:  M100  on behalf of Ken Pettit

Reply-To:  
Date:  Saturday, July 18, 2020 at 2:22 PM
To:  
Subject:  Re: [M100] PIC32MX (off topic but related!)

>   
>  Hey Steve,
>  
>  Configuration bits?  Are you setting those correctly to ensure the proper
> clock mode is selected, etc?
>  
>  Ken
>  
>  
> On 7/18/20 2:02 PM, Stephen Adolph wrote:
>  
>  
>> Well ok thanks guys.
>> In a nutshell,  ( long winded explanation of problem to follow)...
>>  
>> 
>>  
>>  
>> The Geoff VT100 page has both Geoffs source project files as well a binary
>> file that can be programmed.
>>  
>> 
>>  
>>  
>> The binary contains the application plus bootloader
>>  
>> 
>>  
>>  
>> When I try to build the project myself (unchanged) I get a different binary
>> that does not seem to include the bootloader.In any case I cannot see a
>> way to produce the same binary as what he provides.  I cant relplicate his
>> build.
>>  
>> 
>>  
>>  
>> As well, I cant see anything that seems to relate to the bootloader
>> functionality in the actual code.
>>  
>> 
>>  
>>  
>> Very confusing.
>>  
>> 
>>  
>>  
>> In any case, the code that MPLAB X produces can be programmed but it does not
>> work.  Meaning if I erase the part completely and then attempt to program my
>> application, the device does not start after the application  is loaded.
>>  
>> 
>>  
>>  
>> However I know my binary works because if I program it OVER TOP of an MCU
>> that has the original binary in it, I can thusly install my application and
>> see it run.
>>  
>> 
>>  
>>  
>> So it really seems like I can produce working application code .. but the
>> bootloader portion cant be generated from scratch. I must be already in there
>> by separate means for my application to work.
>>  
>> 
>>  
>>  
>> 
>>  
>>  
>> So I am a bit stuck.   The only way I can produce MVT100 processors is to
>> first program with the original code  and then overlay my code.
>>  
>> 
>>  
>>  
>> Strange.
>>  
>> 
>>  
>>  
>> Any thoughts?  I really am a newbie on these things.
>>  
>> 
>>  
>>  
>> Thabks Steve
>>  
 
  
  
>>>  
>>>  
>>  
>>  
>  
>  

Re: [M100] PIC32MX (off topic but related!)

[B4 Me100]

One problem I have found importing other projects is to make sure the
versions of MPLAB and the XC32 compiler are identical.  Not sure how old the
VT100 project might be but MPLAB and its associated libraries have changed a
lot, even the methods used to perform some operations have changed.  The
differences in the libraries could be causing a mismatch in the binary
files.  The USB libraries have changed quite a bit as new features have been
added.  

If you look at the project properties (right click on the project) check
that all the libraries are there and the linkers are correct, also check
that the programmer is set up correctly to use the memory space properly.
If a bootloader is being used then need to make sure the starting point for
the code is correct ­ it has to move to create the bootloader space.  The
bootloader used to be a separate part that had to be downloaded then the
application was loaded (IIRC), it should be available on the Microchip site.
I abandoned the bootloader because it caused too many issues.

Just opening a project sometimes does not set up all the config bits
properly that the original developer might of used ­ crazy I know, Atmel has
the same issue.  I found this problem just migrating my own project to a new
machine, I had to cross check the two configs to make sure they were
correct.  This included adding object libraries back into the new
configuration ­ I am using some very old libraries, the new libraries are
too buggy for some functions.

Not much of a direct point to a problem but areas to check.

Usually there is a config.h (or similar name) for the bit settings which
should come with the project, this will take care of all the settings.  The
32MX also allows the program to change some of those bits at run time,
mostly to help with debug or clock issues.

From:  M100  on behalf of Ken Pettit

Reply-To:  
Date:  Saturday, July 18, 2020 at 2:22 PM
To:  
Subject:  Re: [M100] PIC32MX (off topic but related!)

>   
>  Hey Steve,
>  
>  Configuration bits?  Are you setting those correctly to ensure the proper
> clock mode is selected, etc?
>  
>  Ken
>  
>  
> On 7/18/20 2:02 PM, Stephen Adolph wrote:
>  
>  
>> Well ok thanks guys.
>> In a nutshell,  ( long winded explanation of problem to follow)...
>>  
>> 
>>  
>>  
>> The Geoff VT100 page has both Geoffs source project files as well a binary
>> file that can be programmed.
>>  
>> 
>>  
>>  
>> The binary contains the application plus bootloader
>>  
>> 
>>  
>>  
>> When I try to build the project myself (unchanged) I get a different binary
>> that does not seem to include the bootloader.In any case I cannot see a
>> way to produce the same binary as what he provides.  I cant relplicate his
>> build.
>>  
>> 
>>  
>>  
>> As well, I cant see anything that seems to relate to the bootloader
>> functionality in the actual code.
>>  
>> 
>>  
>>  
>> Very confusing.
>>  
>> 
>>  
>>  
>> In any case, the code that MPLAB X produces can be programmed but it does not
>> work.  Meaning if I erase the part completely and then attempt to program my
>> application, the device does not start after the application  is loaded.
>>  
>> 
>>  
>>  
>> However I know my binary works because if I program it OVER TOP of an MCU
>> that has the original binary in it, I can thusly install my application and
>> see it run.
>>  
>> 
>>  
>>  
>> So it really seems like I can produce working application code .. but the
>> bootloader portion cant be generated from scratch. I must be already in there
>> by separate means for my application to work.
>>  
>> 
>>  
>>  
>> 
>>  
>>  
>> So I am a bit stuck.   The only way I can produce MVT100 processors is to
>> first program with the original code  and then overlay my code.
>>  
>> 
>>  
>>  
>> Strange.
>>  
>> 
>>  
>>  
>> Any thoughts?  I really am a newbie on these things.
>>  
>> 
>>  
>>  
>> Thabks Steve
>>  
>> 
>>  
>>  
>> 
>>  
>>  
>> 
 
  
  
>>>  
>>>  
>>  
>>  
>  
>  

Re: [M100] PIC32MX (off topic but related!)

[Ken Pettit]

Hey Steve,

Configuration bits?  Are you setting those correctly to ensure the 
proper clock mode is selected, etc?


Ken

On 7/18/20 2:02 PM, Stephen Adolph wrote:

Well ok thanks guys.
In a nutshell,  ( long winded explanation of problem to follow)...

The Geoff VT100 page has both Geoffs source project files as well a 
binary file that can be programmed.


The binary contains the application plus bootloader

When I try to build the project myself (unchanged) I get a different 
binary that does not seem to include the bootloader.   In any case I 
cannot see a way to produce the same binary as what he provides.  I 
cant relplicate his build.


As well, I cant see anything that seems to relate to the bootloader 
functionality in the actual code.


Very confusing.

In any case, the code that MPLAB X produces can be programmed but it 
does not work.  Meaning if I erase the part completely and then 
attempt to program my application, the device does not start after the 
application  is loaded.


However I know my binary works because if I program it OVER TOP of an 
MCU that has the original binary in it, I can thusly install my 
application and see it run.


So it really seems like I can produce working application code .. but 
the bootloader portion cant be generated from scratch. I must be 
already in there by separate means for my application to work.



So I am a bit stuck.   The only way I can produce MVT100 processors is 
to first program with the original code  and then overlay my code.


Strange.

Any thoughts?  I really am a newbie on these things.

Thabks Steve



On Saturday, July 18, 2020, B4 Me100 > wrote:


I have written quite a lot of code for the PIC32MX795 for use in
my DVI and Micro-DVI boards.  Please feel free to DM.

Although I do hate MPLAB – X :)

From: M100 mailto:m100-boun...@lists.bitchin100.com>> on behalf of Stephen
Adolph mailto:twospru...@gmail.com>>
Reply-To: mailto:m...@bitchin100.com>>
Date: Saturday, July 18, 2020 at 7:26 AM
To: mailto:m...@bitchin100.com>>
Subject: [M100] PIC32MX

anyone on the list have any experience with developing
applications for PIC32MX or similar?

thx Steve

Re: [M100] PIC32MX (off topic but related!)

[Stephen Adolph]

Well ok thanks guys.
In a nutshell,  ( long winded explanation of problem to follow)...

The Geoff VT100 page has both Geoffs source project files as well a binary
file that can be programmed.

The binary contains the application plus bootloader

When I try to build the project myself (unchanged) I get a different binary
that does not seem to include the bootloader.In any case I cannot see a
way to produce the same binary as what he provides.  I cant relplicate his
build.

As well, I cant see anything that seems to relate to the bootloader
functionality in the actual code.

Very confusing.

In any case, the code that MPLAB X produces can be programmed but it does
not work.  Meaning if I erase the part completely and then attempt to
program my application, the device does not start after the application  is
loaded.

However I know my binary works because if I program it OVER TOP of an MCU
that has the original binary in it, I can thusly install my application and
see it run.

So it really seems like I can produce working application code .. but the
bootloader portion cant be generated from scratch. I must be already in
there by separate means for my application to work.


So I am a bit stuck.   The only way I can produce MVT100 processors is to
first program with the original code  and then overlay my code.

Strange.

Any thoughts?  I really am a newbie on these things.

Thabks Steve



On Saturday, July 18, 2020, B4 Me100  wrote:

> I have written quite a lot of code for the PIC32MX795 for use in my DVI
> and Micro-DVI boards.  Please feel free to DM.
>
> Although I do hate MPLAB – X :)
>
> From: M100  on behalf of Stephen
> Adolph 
> Reply-To: 
> Date: Saturday, July 18, 2020 at 7:26 AM
> To: 
> Subject: [M100] PIC32MX
>
> anyone on the list have any experience with developing applications for
> PIC32MX or similar?
>
> thx Steve
>
>

Re: [M100] PIC32MX

[B4 Me100]

I have written quite a lot of code for the PIC32MX795 for use in my DVI and
Micro-DVI boards.  Please feel free to DM.

Although I do hate MPLAB ­ X :)

From:  M100  on behalf of Stephen Adolph

Reply-To:  
Date:  Saturday, July 18, 2020 at 7:26 AM
To:  
Subject:  [M100] PIC32MX

> anyone on the list have any experience with developing applications for
> PIC32MX or similar?
> 
> thx Steve

Re: [M100] PIC32MX

[Stephen Adolph]

Hi Ken, thanks!  This is relative to my adoption of the Geoff VT100
application.  I am having trouble understanding some basics around the
Microchip tools, and how the PIC is programmed.  If it is ok I will email
you off list.  Cheers



On Saturday, July 18, 2020, Ken Pettit  wrote:

> Hey Steve,
>
> How similar is "similar"?  I have developed on PIC18, Atmel SAM, MIPS,
> RISC-V, etc.  Was there something specific you were looking for help with?
>
> Ken
>
> On 7/18/20 7:26 AM, Stephen Adolph wrote:
>
>> anyone on the list have any experience with developing applications for
>> PIC32MX or similar?
>>
>> thx Steve
>>
>
>

Re: [M100] PIC32MX

[Ken Pettit]

Hey Steve,

How similar is "similar"?  I have developed on PIC18, Atmel SAM, MIPS, 
RISC-V, etc.  Was there something specific you were looking for help with?


Ken

On 7/18/20 7:26 AM, Stephen Adolph wrote:
anyone on the list have any experience with developing applications 
for PIC32MX or similar?


thx Steve

[M100] PIC32MX

[Stephen Adolph]

anyone on the list have any experience with developing applications for
PIC32MX or similar?

thx Steve

Re: [M100] MVT100 update

[Paco]

Hi Steve.

I'm interesting in one kit

El sáb., 18 jul. 2020 1:07, Joe Grubbs  escribió:

> Cool thanks! I look forward to this
> --
> *From:* M100  on behalf of Stephen
> Adolph 
> *Sent:* Friday, July 17, 2020 6:27:33 PM
> *To:* m...@bitchin100.com 
> *Subject:* [M100] MVT100 update
>
> Hey all,
> Just a quick note to say  I have some progress to report on the MVT100
> video adapter.  Boards are back finally and they look to be fine.
> I have some work to do to sort out how to program the PIC correctly.
>
> Once that is done I will be able to send out the kits to those who let me
> know they were interested in such.
>
> I'll post some pics of the finished product + additional info at the wiki.
> cheers
> Steve
>
>
>