Hello Ben,
I installed version 7.3.0.7 and after that I noticed this.
Best Regards,
Lagoda
A little cosmetic mistake. PIC32MZ (Solved)
Moderator: Benj
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: A little cosmetic mistake. PIC32MZ
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.
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.
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
-
- Posts: 170
- Joined: Fri Jul 15, 2016 9:51 pm
- Has thanked: 69 times
- Been thanked: 61 times
- Contact:
Re: A little cosmetic mistake. PIC32MZ
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. 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
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. 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
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: A little cosmetic mistake. PIC32MZ
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.
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.
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
-
- Posts: 170
- Joined: Fri Jul 15, 2016 9:51 pm
- Has thanked: 69 times
- Been thanked: 61 times
- Contact:
Re: A little cosmetic mistake. PIC32MZ
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
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