⚠️ Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
Dialog recommends to use an interface board (CIB board, please check the UM-B-065 Bluetooth Smart Communication Interface Board) in order to program a DUT, but theoretically you can program a DUT using the JTAG from a pro dev kit.
Already tried using the connections from the jumper j14 but cant get it to detect our device. But using a 583 basic dev kit i can program the device using tms and tck pins ont he basic dev kit. What am I doing wrong with the pro devkit?
As i ve mentioned its better to use the CIB board for programming various custom boards this is what dialog recommends, by using the pro motherboard can be hard to operate due to the level translator that cannot drive long lines and can cause different kind of issues.
Hi mutahir,
Dialog recommends to use an interface board (CIB board, please check the UM-B-065 Bluetooth Smart Communication Interface Board) in order to program a DUT, but theoretically you can program a DUT using the JTAG from a pro dev kit.
Thanks MT_dialog
Already tried using the connections from the jumper j14 but cant get it to detect our device. But using a 583 basic dev kit i can program the device using tms and tck pins ont he basic dev kit.
What am I doing wrong with the pro devkit?
Hi mutahir,
As i ve mentioned its better to use the CIB board for programming various custom boards this is what dialog recommends, by using the pro motherboard can be hard to operate due to the level translator that cannot drive long lines and can cause different kind of issues.
Thanks MT_dialog