Page 1 of 1

Can't see all chip pins

Posted: Wed May 23, 2018 6:16 pm
by markavo
maybe this is something i'm missing.

I do not see all the chip pins.

When i try to select a pin i see the bottom half of the chip
When i click view / chip i see the top half

i'm using ARM NUCLEO-144 F746ZG

Update checked flowcode 7 and it’s the same
But connected to 4K tv and I can see all the pins.

Is it not possible please to be able to scroll the box with the chip pins so I can run at a lower resolution on my laptop.

Thanks

Re: Can't see all chip pins

Posted: Thu May 24, 2018 6:37 am
by Steve
I've checked and this seems to be working ok for me, so I suspect it is something to do with your PC's DPI settings. I'll pass this on to the development team to look at.

Re: Can't see all chip pins

Posted: Thu May 24, 2018 9:56 am
by markavo
Thank you.

If i connect a second display (4k tv) and use as a second monitor drag the properties over to the second screen i see all the pins but not on the laptop with a resolution of 1366 x 768

Re: Can't see all chip pins

Posted: Thu May 24, 2018 1:01 pm
by EtsDriver
Are you using display scaling on the 1366x768?

https://youtu.be/NF210WeR9C8

Re: Can't see all chip pins

Posted: Thu May 24, 2018 9:04 pm
by markavo
Thank you, just tested but no luck no matter what setting i choose i still miss the top half of the ic when selecting the pins for the 32F746 i see from pin 9 downwards arduino mega is fine its square shaped when selecting the pins this one for some reason is shaped as a dil packaged ic but in reality its square.

Re: Can't see all chip pins

Posted: Fri May 25, 2018 8:42 am
by LeighM
for some reason is shaped as a dil packaged ic but in reality its square.
The pinout of the Nucleo and Disco boards were intended to represent the pin header of the board, rather than the raw chip device.
I think for some extra pins were needed to support things like onboard display, so some inconsistency has crept in :roll:

If anyone has any particular chip requirement, let us know and we will add it to our pending list and endeavour to create an FCD descriptor for it