DiyLightAnimation
Hardware => Lynx Smart String => Topic started by: sebjsan on October 16, 2012,
-
Trying to program my sshub, but dont know which pic to use.
-
Can you be more specific about what exactly you are doing, and what exactly the issue is? Also, have you referenced these links?
http://www.diylightanimation.com/wiki/index.php?title=FAQ#PIC_.28micro-controller.29
-
For example, the etherdongle requires the following (Select "PIC32MX795F512L" from the "Device:" drop down list.). What is the pic for the sshub?
-
For example, the etherdongle requires the following (Select "PIC32MX795F512L" from the "Device:" drop down list.). What is the pic for the sshub?
This chart shows them all:
http://www.diylightanimation.com/wiki/index.php?title=J1SYS_boards_jumper_chart (http://www.diylightanimation.com/wiki/index.php?title=J1SYS_boards_jumper_chart)
-
Fantastic! Thanks Steve
-
I've stuggled with this before too, because you don't need the jumpers for many of the boards, so I don't look there. Could this information be added to the wiki or the assembly manual for each board, so it is easier to find?
-
I've stuggled with this before too, because you don't need the jumpers for many of the boards, so I don't look there. Could this information be added to the wiki or the assembly manual for each board, so it is easier to find?
Sure the info can be added. Here is the real problem. With the pickit2 program it identifies the correct pic (of course it won't work with the etherdongle pic). So why can't microchip get the pickit3 program to identify the pic?? Maybe we could ask a member who also works for microchip that question.
I guess the short term answer is to add the info.
Rick R.
-
I just look on my order from Mouser or hte bom in the wiki if the printing on the chip itself isn't very clear. But yes it would be nice for the pickit 3 to auto identify, it can tell when you've got the wrong one as it is.
-
If you can get at least the first part of the PIC address correct, it will come up with an error message and the correct, full PIC ID for you. (like PIC24F...... and just pick the first one).
Though I like the chart listed above. I was always going back to the BOM.
-
I added the PIC info to the equipment page of each current active item.
Hope that helps
Rick R.
-
Thanks.
-
I've stuggled with this before too, because you don't need the jumpers for many of the boards, so I don't look there. Could this information be added to the wiki or the assembly manual for each board, so it is easier to find?
Sure the info can be added. Here is the real problem. With the pickit2 program it identifies the correct pic (of course it won't work with the etherdongle pic). So why can't microchip get the pickit3 program to identify the pic?? Maybe we could ask a member who also works for microchip that question.
I guess the short term answer is to add the info.
Rick R.
It doesn't identify them becauseit isn't the same device. Don't tink that the Pickit-3 is an advanced Pickit-2, it isn't. The Pickit-2 is a PIC programmer and the Pickit-3 is a combination device that incorporates the ability to program PIC's like the Pikit-2 and the inline diagnostic capability of one of there big dollar devices.
-
It doesn't identify them becauseit isn't the same device. Don't tink that the Pickit-3 is an advanced Pickit-2, it isn't. The Pickit-2 is a PIC programmer and the Pickit-3 is a combination device that incorporates the ability to program PIC's like the Pikit-2 and the inline diagnostic capability of one of there big dollar devices.
So you now work for microchip?
Still the program is Beta and it doesn't fully work. Its been in beta for a while now and it sure would be nice if they updated the program. Microchip lists both devices as a debugger
I never said that I "tink" what the pickit3 was an advanced pickit2.
Rick R.
-
Not once in this thread did I see a mention that this was an active hub. Probably a safe assumption, but let's not forget that there are multiple types of sshubs and only one has a microchip.
-
and only one has a microchip.
...
-
At least I am not the only one who thinks the pickit 3 program should recognize the pic. One of my pet peeves is having to scroll and find it, every time...
-
At least I am not the only one who thinks the pickit 3 program should recognize the pic. One of my pet peeves is having to scroll and find it, every time...
+1
-
or at least give me the ability to remove all the items in the list except what I work with...
-
So you now work for microchip?
Still the program is Beta and it doesn't fully work. Its been in beta for a while now and it sure would be nice if they updated the program. Microchip lists both devices as a debugger
I never said that I "tink" what the pickit3 was an advanced pickit2.
Rick R.
No, I don't work for MicroChip but I do know how to read and when the Pickit-3 came out and people were complaining about how much harder it seemed to be to use than the Pickit-2, I did some research on it.
Attacking me on a typo is a bit childish, don't ya think. I was not attacking you or really even directing that comment toward just you. Because the Pickit-3 looks so much like the Pickit-2, many may think that it's just an upgrade of it and MicroChip says that it isn't. It is a whole new device.
As for the program still being in beta, while true, that may have nothing to do with the Pickit-3 not identifying the PIC it is connected to. It could simply be that the design of these newer advanced PIC's that this unit was designed to work with don't have a consistant method of identification. Since this would prevent the Pickit-3 from identifying the PIC's in this family of chips or probably the newer ones yet to come, why bother to add the feature at all, especially for PIC's that are approaching their end of life.
I agree with Chris that it would be a good idea to limit the list to the PIC's that you are working with but since this is just a low level utility and not MPLAB, they probably didn't think of it or think that it was worth the time to include. Perhaps if we email them and request that feature, they may include it in a future release of the utility, especially if the work needed to add it is not cost prohibitive.