A little cosmetic mistake. PIC32MZ (Solved)

An area to discuss 32-bit PIC specific problems and examples

Moderator: Benj

Lagoda
Posts: 147
Joined: Fri Jul 15, 2016 9:51 pm
Has thanked: 62 times
Been thanked: 56 times
Contact:

A little cosmetic mistake. PIC32MZ (Solved)

Postby Lagoda » Mon Feb 26, 2018 8:51 pm

Hello Ben,

I installed version 7.3.0.7 and after that I noticed this.
The names of the ports are incorrect.jpg
The names of the ports are incorrect.jpg (137 KiB) Viewed 1391 times

Best Regards,

Lagoda
Last edited by Lagoda on Wed Feb 28, 2018 2:55 pm, edited 1 time in total.

User avatar
Benj
Matrix Staff
Posts: 14219
Joined: Mon Oct 16, 2006 10:48 am
Location: Matrix TS Ltd
Has thanked: 4361 times
Been thanked: 4096 times
Contact:

Re: A little cosmetic mistake. PIC32MZ

Postby Benj » Wed Feb 28, 2018 11:08 am

Hi Lagoda,

I've just tried 7.3.0.6 here with that target chip and it looks the same to me, what were you expecting to see? The Input and Output icons can only use the ports in 8-bit mode. The full 16-bit ports can be accessed via the port functions in the calculation icon.

Lagoda
Posts: 147
Joined: Fri Jul 15, 2016 9:51 pm
Has thanked: 62 times
Been thanked: 56 times
Contact:

Re: A little cosmetic mistake. PIC32MZ

Postby Lagoda » Wed Feb 28, 2018 12:31 pm

Hi Ben,

I think this tag is more logical for 16-bit ports (H and L) than the PIC32 example.
That's why I wrote a cosmetic mistake.
PORTS.jpg
PORTS.jpg (82.8 KiB) Viewed 1371 times

If the ports of the PIC32 family are deliberately marked on this way, this is fine for me.
But why do you use two types of marking within Flowcode?

Best Regards,

Lagoda
These users thanked the author Lagoda for the post:
Benj (Wed Feb 28, 2018 12:55 pm)
Rating: 5.26%
 

User avatar
Benj
Matrix Staff
Posts: 14219
Joined: Mon Oct 16, 2006 10:48 am
Location: Matrix TS Ltd
Has thanked: 4361 times
Been thanked: 4096 times
Contact:

Re: A little cosmetic mistake. PIC32MZ

Postby Benj » Wed Feb 28, 2018 12:57 pm

Hi Lagoda,

I think it's because Flowcode is treating it as a 32-bit device and assumes 32-bit ports. So L and H don't cut it and instead they are numbered 0-3 for the 4 bytes. 0 being the L byte.

I'll have a look and see if this is easy to fix as the ports on PIC32 are 16-bit max.

Maybe we need a separate processor bit depth and port bit depth options in the definition file.
These users thanked the author Benj for the post:
Lagoda (Wed Feb 28, 2018 1:42 pm)
Rating: 5.26%
 

Lagoda
Posts: 147
Joined: Fri Jul 15, 2016 9:51 pm
Has thanked: 62 times
Been thanked: 56 times
Contact:

Re: A little cosmetic mistake. PIC32MZ

Postby Lagoda » Wed Feb 28, 2018 1:42 pm

Hi Ben,

Once you have a lot of time ... :)

I just wanted to report it, it does not cause any problems.

Thank you very much for the answer.

Best Regards,

Lagoda
These users thanked the author Lagoda for the post:
Benj (Wed Feb 28, 2018 2:29 pm)
Rating: 5.26%