Hi dialog,
I have a basic kit. I have set up the environment as per the document ( jlink, pack installer, keil, target options etc). The settings are also proper, but when I run the code in the debug mode, the code seems to be malfunctioning. I ran the basic blinky project, the LED is blinking at a variable rate and the prints coming are non-readable (with symbols and all) even though I've set the baud rate perfectly. I haven't changed anything in the code. How should I proceed?
Thanks in advance
Device:
Hi sanjayp93,
If you see the led blinking and that data are comming out on steady intervals on your terminal, you either set the baudrate wrong, or something is wrong with the UART of the ATMEL processor that acts as a jlink. What you can try besides rechecking your baudrare and make sure that is set in 115200, remove the jumpers that connect the UART TX/RX from the ATMEL and place an FTDI chip and try again to print out characters. Also have a look at the Device Manager on your PC and check if the basic kit is seen as JLink CDC UART Port.
Thanks MT_dialog
I have a pro kit too, tried with the same, still getting the same scenario. What should I make of this? And the LED is not actually "blinking", It's kind of more or less like flickering. The baud rate is 115200.
Hi sanjayp93,
I dont have any reasonable explanation for this (if you haven't tested it on two different devices i would say that something is wrong with the board), are certain that you altered the sw of the blinky in any way or perhaps have you misplaced any jumper on the boards that you are using ? Please try to use a fresh copy of the SDK and the blinky example. Also regarding the fact that you are getting different kind of symbols on your UART, can you please try to hit the reset button and check if the symbols and the output rate are the same when the program is executing. When reset is hit, the bootloader runs and prints some symbols on the UART (junk data), i am just trying to understand if the program runs and prints junk data or if the downloading fails and you get the bootloader's junk data on your UART. Also as a last resort check a different USB port or a different pc perhaps.
Thanks MT_dialog