when I plug in an ISP programmer to the PC, the board does not enumerate in win10-64. only the power led blinks, nothing connected.
any suggestions ?
after long searching it turned out that R6 had a dry joint. these board are apparently not tested ..
after touching R6 up, the board enumerates as com40 , but GP designer softwhere still does not recognize the board.
any suggestions ?
Device:
Device Number:
in circuit programmer
I managed to use the advanced platform as in circuit programmer by wiring the GND, SDA, SCL and VDD from the internal socket to the pins on the defective ISP board and then on to the to be programmed chip on the board via the 4 wire JST connector. the SW complains about a socket error , but they wisely added a skip option.
I ordered a new ISP board, hopefully that one is is tested ..
Hello,
I'm sorry to hear about your problems with the ISP board. In order to provide some help, can you answer a few quick questions?
- When you say that the GP designer software doesn't recognize the board, can you confirm that the "Emulation" and "Test Mode" buttons are "greyed" out and un-clickable?
- The "DB HW-FW:" portion at the bottom of the window should just have a "-" following it. Is this correct as well?
- If you have other GreenPAK designer windows open, can you make sure that none of them are also using the "Debug" tool?
Although I'm not sure if this is the issue, we often solve similar behavior by either unplugging and re-plugging in the ISP board or by closing and re-opening the "Debug" window. I've included a link to the guide for our ISP board for your reference.
//www.wsdof.com/sites/default/files/isp_board_quick...
Craig
greg,
there is onely one GP designer window,
no info on the board HW is given ( DB HW FW -) , no info on the connected device, I'm used to regularly plug and unplug the advanced programming platform.
emulation and test mode are greyed out.
it is clear to me that this ISP programmer never has been tested, given the tumbstoned resistor in the USB data path. it's just a DOA. I tried touching up the poorly soldered pads of the 2211 USB uart. wetting seems the problem.
there is no place where I can claim any defect or repair at the silego webshop..
我做了各种项目silego部分,mostly the 46620. this is my first ISP project soldering a blank device into the board, sofar donestuff with the advanced platform, and I have one more coming up.
I'll have one the team reach out to you offline to check on update here and to ensure we have solved teh problems for you. BR JE_DIalog
I am having the same issue of ISP not being initialized in the GreenPAK software.
I have used this same ISP device to program the same GreenPAK module 2 months ago so it's not an assembly issue. Since I updated the GreenPAK software last week, it has not worked. Restarting the program, computer, and unplugging the USB has not resolved it.
How was it resolved forkoen@weijand.nl?
Thank you,
Sarah
Both ISP V1.0 (new, first use) {SLG46826} and Universal Dev board (known good board) {SLG46620} are not found by GreenPak 6.22 "Debugging Controls". "Emulation" and "Test Mode" buttons are grayed out. System Information: Development Board is "N/D". Windows 10 Pro, 64bit x64 system. Tried both, one at a time. The ISP shows up as a USB input device (HID compliant) named "In-System Programmer" in Windows "Devices and Printers" Control Panel.
Hi CSeebruch,
Thank you for your appeal.
Regarding the ISP board, the problem could be in the software. For now, we have a fix. Please see the file in the attachment. You have to extract the appropriate file to the folder with GreenPAK Designer (typically it is in the folder C:\Program Files\Dialog Semiconductor\GreenPAK Designer v.6.22 (64-bit)) and replace the existing file. After you made it ISP board should work.
Regarding the DevBoards, I have additional questions:
1. Did the board work with the previous software revision?
2. Did you check all the connections like cable, USB port?
3. Could you check if USB input device appears in Device Manager (see Human Interface Device)
4. Please check if no other debug window is opened.
5. Could you please tell which LEDs are working on the AdvBoard in Debug Mode and without Debug Mode
6. Did you try to connect the AdvBoard to another PC? It is needed to exclude to PC issue
Best regards,
Oleh Sapiha
1. Yes, I was using the Dev Board on a different laptop. turned-in that laptop for repair, and loaded Greenpak on this laptop to continue development.
2. Yes, moved the connections to different ports. The Dev Board is enumerated by windows each time
3. Yes, The USB input device appears in the device Manager
4. No other debug window is open, rebooted the computer many times, Even Uninstalled greenpak and then reinstalled. After trying repair install.
5.The AdvBoard has a white LED that is ON (stays ON) when the USB cable is plugged in. That is the only LED that gets illuminated.
6. I have two different AdvBoards that worked with the other Laptop (in for repair). both do not work with this computer
CSeebruch,
Thanks for your responses.
Could you try one approach that can help you? Try to Uninstall Device in Device Manager (Human Interface Devices) to then plug in the Adv Board directly to your PC (without any USB hubs) and wait until the driver will be installed. GPAK designer must be closed. Then start the GPAK designer and open the debug mode.
By the way, do you have any software, that can block the driver proper work?
Best regards,
Oleh Sapiha
The Adv Board is now seen by GreenPak Debug! The USB cable is directly plugged into Laptop (not using hub). I'll try the ISP board later today to see if it works.
Thanks
CSeebruch,
I'm happy that I helped you with the issue. If you have any further questions about the GPAK designer, hardware, or chip itself please let me know.
Best regards,
Oleh Sapiha