This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Debugger Beacons Minew with TI CC Debugger

Other Parts Discussed in Thread: CC2541, CC-DEBUGGER

Hi guys i have some beacons manufactured by Minew.

Now i will be programmer my beacons and so i have buy the TI CC Programmer and Debugger.

like you can see, on my beacon i've 5 pin (jtag connector minimal) marked with green rectangle,

so i will interface that connector with cc debugger used the minimal connection for debugg

i don't added the pull-up resistor because it's included on cc2541.

I've done a custom connector for interface of the ccdebugger with my beacons, but when i connect beacon on cc-debugger e so at my notebook, the led on my cc debugger stay on RED and in the manual this means that there is a problem in the connection or the debugger not identifies chip (it's a cc2541 soc) on my beacon.

I've done two connection test.

In the first case i've connected pin 9 (connector target of  the debugger) to pin V of the beacon.

In the second test i've eliminated the connection between pin 9 and pin V and i've connected pin2 of connector target to pin V(beacon).

Iin both cases the debugger not work well, in the first case the led doesn't turn on, in the second case stay Red.

From Manual:

1)Note the concept with the target voltage sense signal. This signal is used by the level converters on the CC Debugger to handle different voltage levels on the target board and the debugger. Pin 2 on the target connector must be connected to VDD on the target board.

Where i made the mistake?

  • Hello Valerio,
    Have you powered the board?

    You should try to power it externally as well. The CC-debugger can only provide a limited amount of power.

    BTW:

    The debug interface is not based on JTAG, it's a custom debug interface.

  • Valerio,

    The pin you show as "Vdd" must be powered by the beacon.
    Alternatively you can connect pin 9 to pin 2 in addition to let the debugger power the beacon as well.

    Regards,
    Svend
  • hi,
    I have the same goal - installing my own firmware on a Minew board.
    I tried using the OAD function as described in the following link
    wiki.viewc.com/ibeacons-oad-upgrade-en.html
    with no success.

    after compiling the 2 bin images A,B (SimpleBLEPeripheral code sample) I am installing image B (since the current working image is A).
    I get a success message with information that the board is restarting and that i'll see Image type B running in the next step, however, this never happens - I am always having Image A running and not my newly installed firmware.

    1. did you try using the OAD function with that board?
    2. did you have success with your 'custom' installation of the cc debugger using the Minew JTag connectors?
    3. if anyone got any idea why OAD doesn't work or where should i look for answers, I will appreciate it.

    Thanks.
  • Hi,
    few answers... just to make it documented.
    I have used the second diagram - connecting 2 to 2 and it works just fine (including the light on the debugger).

    I use a different Minew board (circled one), but with the same chip.

    After installing my OAD firmware on that board it started working, probably Minew's factory firmware doesn't support the OAD (guessing they have a bug in the BIM part - always starting from imageA)

    Iddo
  • hi sorry for delay, i've used another connection scheme, i attached it below.

    I don't use the OAD profile or functionality.

    i've connected the Target Voltage to 3,3V pin.

  • Happy to hear that it worked for you using that connections and the Minew board you use.

    Just to let know others who use Minew board such as in the following link, your 2nd drawing is enough (2 to 2).