Part Number: EVMK2G
Hi Rahul,
could you please reopen the following thread: https://e2e.ti.com/support/processors/f/791/p/808046/2996417#2996417?
Thank you,
Adam
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.
Part Number: EVMK2G
Hi Rahul,
could you please reopen the following thread: https://e2e.ti.com/support/processors/f/791/p/808046/2996417#2996417?
Thank you,
Adam
Part Number: EVMK2G
Hi,
We have been developing with K2G EVM for some time with a lot of problems with the HW. Two out of three EVMs we bought proved to be defective and we lost a lot of engineering time doing all the checks recommended in https://e2e.ti.com/support/processors/f/791/p/767695/2845004?tisearch=e2e-sitesearch&keymatch=we%20have%20bought%20a%20second%20K2G%20EVM%20and%20I%20have%20thought%20we%20could%20try%20it%20without%20anything#2845004.
Is there anything seriously wrong with this EVM?
I also noticed that the documentation of AK66K2G02 has disappeared from the TI website. Is this related?
I have just received this information from Customer Support: "Thank you for contacting TI Customer Support and choosing TI product as part of your project. Regarding your inquiry, I do apologize that you are facing this situation of not able to access the technical documents of 66AK2G02. The device is now "OBSOLETE" in status, with this status all links together with technical documents relevant to this device are being removed from our website. I also wanted to extend my apologies that even in our archive accessing these documents is strictly prohibited."
Best regards,
Adam
Hi Adam,
The 66AK2G02 devices were replaced with the 66AK2G12, so you can refer to this device documentation.
As for your other question:
Is there anything seriously wrong with this EVM?
I am not aware of any major problems with the K2G EVMs.
Best Regards,
Yordan
Hi Yordan
Thank you for your answer. Yes, I know there is the new model but because the previous model documentation has been removed I am unable to check what are the differences that affect the development with K2G EVM and Linux and RTOS SDKs. Could you please refer me to where I can find those differences? Thank you.
Best regards,
Adam
Hi Adam,
66AK2G02 and 66AK2G12 should be identical when it comes to functionality & memory mapping (they should share common TRM & Datasheet). You should be able to use the 66AK2G12 documentation for your EVM having 66AK2G02.
Best Regards,
Yordan
Dear Yordan,
thank you for your answer. Frankly, I am not very much convinced of using a TRM and datasheet for a different, probably similar, but after all, not the same product without being sure that there are no differences affecting my development. EVM K2G is an active product, so I do not understand why there is no access to the documentation of the processor that the EVM uses? Thank you.
Best regards,
Adam
Hi Yordan,
We have bought the fourth EVM, which has just arrived, and it behaves like the previous one: it prints character "▒" to the serial console and then continues booting. The previous EVM worked for a few times and then only printed the character "▒" and stopped booting, so I expect the new board will die soon too. So this will be 3 defective boards out of 4 we have bought. Could you please look into it, as we are spending the time on buying, testing and shipping back the defective EVMs. Thank you.
Best regards,
Adam
Hi Adam
Yordan highlighted this thread to us.
I am sorry to hear that you are facing issues with the K2G EVM. As Yordan mentioned we have not heard of any quality issues with the EVM.
I could not figure out from the previous post you highlighted - whether it was concluded that it was a software issue or a defective board.
Can you please clearly describe how you setup the board out of the box and if the issue is only seen if you have the hdmi monitor hook up?
Do you have emulator, to be able to run simpler JTAG based board tests , that can tell you whether the board is ok or not?
If you strongly feel that it is a defective board , you can also initiate a return
http://www.ti.com/support-quality/resources/customer-returns.html
This covers the case if a you purchased through distribution or through the TI store.
If you purchased through the TI store, you can proceed directly to:
I would still recommend that you work with us on E2E to see if we can isolate if it is a hardware/board problem or a software issue.
Regards
Mukul
Hi Adam,
All EVMs are tested by the third party vendor before they are placed in to the TI store so your experience is troubling. The K2G EVM includes a Board Management Controller (BMC) which controls the bootmodes, reset and power for the K2G. It also writes to the display which you reported is not updating correctly. The console port for the BMC is connected to the UARTtoUSB circuit. If you connect a USB cable to J23 you should be able to capture the BMC monitor output using a terminal program. It would be helpful to have that information for the boards that are failing to understand if the BMC software has been corrupted.
Regards, Bill
Hi Mukul,
Thank you for your reply. The problem with the monitor blocking the boot process was a software issue and we solved it by using an older SDK.
The hardware problem is that the second EVM we bought did not boot at all the Linux part, it just it printed the character "▒" on the serial console. The BMC was booting. The third EVM we bought used to print the character "▒" to the serial console and then continued booting, but only for a few times. Then it started behaving like the second board: it only printed the character "▒" on the serial console. I did not check the BMC part. The fourth EVM, which has just arrived, behaves like the third EVM: it prints character "▒" to the serial console and then continues booting. My worry is it will quickly die as the third board did. I have the third and fourth board here.
My connection was minimal in all cases: power and the serial console through USB.
Apart from the EVM onboard emulator I have none other.
Best regards,
Adam
Hi Bill,
Thank you for your reply.
3rd EVM had two of the orange SoC_LED blinking, I think it was 0 and 1, on the last few power ups.
3rd EVM BMC Boot:
BMC VERSION 0.6.1.0
BUILT Apr 11 2016 12:19:52
---------------------
[00:00:00] BMC Init Begin
[00:00:00] BMC Version 0.6.1.0
[00:00:00] K2G-EVM
[00:00:00] Rev 1.2.D
[00:00:00] S/N:15164P540206
[00:00:00] Dip Switches read: 0x7
[00:00:00] BMC Init Complete
[00:00:00] Main PWR Start Begin
[00:00:00] Main PWR Start Complete
[00:00:00] SOC PWR Start Begin
[00:00:00] PMIC Init Begin
[00:00:00] PMIC Init Complete
[00:00:00] SOC PWR Start Complete
[00:00:00] Setup Clk Generation
[00:00:00] Clock Source: INTERNAL
[00:00:00] ClkGen Start Begin
[00:00:00] ClkGen Start Complete
[00:00:00] CDCM ClkGen Start Begin
[00:00:00] Testing register 0 of clock 1... 0x0045, got 0x0045 Passed.
[00:00:00] Testing register 1 of clock 1... 0x0000, got 0x0000 Passed.
[00:00:00] Testing register 2 of clock 1... 0x0018, got 0x0018 Passed.
[00:00:00] Testing register 3 of clock 1... 0x00F9, got 0x00F9 Passed.
[00:00:00] Testing register 4 of clock 1... 0x30EF, got 0x30EF Passed.
[00:00:00] Testing register 5 of clock 1... 0x0001, got 0x0001 Passed.
[00:00:00] Testing register 6 of clock 1... 0x0018, got 0x0018 Passed.
[00:00:00] Testing register 7 of clock 1... 0x0122, got 0x0122 Passed.
[00:00:00] Testing register 8 of clock 1... 0x0004, got 0x0004 Passed.
[00:00:00] Testing register 9 of clock 1... 0x4002, got 0x4002 Passed.
[00:00:00] Testing register 10 of clock 1... 0x0180, got 0x0180 Passed.
[00:00:00] Testing register 11 of clock 1... 0x0000, got 0x0000 Passed.
[00:00:00] Testing register 12 of clock 1... 0x40D2, got 0x40D2 Passed.
[00:00:00] Testing register 13 of clock 1... 0x0180, got 0x0180 Passed.
[00:00:00] Testing register 14 of clock 1... 0x0000, got 0x0000 Passed.
[00:00:00] Testing register 15 of clock 1... 0x0002, got 0x0002 Passed.
[00:00:00] Testing register 16 of clock 1... 0x0010, got 0x0010 Passed.
[00:00:00] Testing register 17 of clock 1... 0x0000, got 0x0000 Passed.
[00:00:00] Testing register 18 of clock 1... 0x001B, got 0x001B Passed.
[00:00:00] Testing register 19 of clock 1... 0x0040, got 0x0040 Passed.
[00:00:00] Testing register 20 of clock 1... 0x0000, got 0x0000 Passed.
[00:00:00] Reading register 21 of clock 1... 0x0005
Clock Ref is SECONDARY of clock 1
[00:00:00] Clock 1
[00:00:00] Reading register 21 of clock 1... 0x0001
[00:00:00] Passed
[00:00:00] CDCM ClkGen Start Complete
[00:00:00] BootMode : MMC/SD Boot
[00:00:00] BOOTMODE ON set to 0 Begin
[00:00:00] SOC RST Begin
[00:00:01] SOC RST Complete
[00:00:01] BOOTMODE ON set to 1 Complete
[00:00:01] BOOT COMPLETE
Performed another test: The GPIO Led Blink Application works and prints nothing to the serial console. The LEDs blink.
--------------------------------------------------------------------------------------------------
4th EVM BMC boot:
BMC VERSION 0.6.1.0
BUILT Apr 11 2016 12:19:52
---------------------
[00:00:00] BMC Init Begin
[00:00:00] BMC Version 0.6.1.0
[00:00:00] K2G-EVM
[00:00:00] Rev 1.2.D
[00:00:00] S/N:15164P540170
[00:00:00] Dip Switches read: 0x7
[00:00:00] BMC Init Complete
[00:00:00] Main PWR Start Begin
[00:00:00] Main PWR Start Complete
[00:00:00] SOC PWR Start Begin
[00:00:00] PMIC Init Begin
[00:00:00] PMIC Init Complete
[00:00:00] SOC PWR Start Complete
[00:00:00] Setup Clk Generation
[00:00:00] Clock Source: INTERNAL
[00:00:00] ClkGen Start Begin
[00:00:00] ClkGen Start Complete
[00:00:00] CDCM ClkGen Start Begin
[00:00:00] Testing register 0 of clock 1... 0x0045, got 0x0045 Passed.
[00:00:00] Testing register 1 of clock 1... 0x0000, got 0x0000 Passed.
[00:00:00] Testing register 2 of clock 1... 0x0018, got 0x0018 Passed.
[00:00:00] Testing register 3 of clock 1... 0x00F9, got 0x00F9 Passed.
[00:00:00] Testing register 4 of clock 1... 0x30EF, got 0x30EF Passed.
[00:00:00] Testing register 5 of clock 1... 0x0001, got 0x0001 Passed.
[00:00:00] Testing register 6 of clock 1... 0x0018, got 0x0018 Passed.
[00:00:00] Testing register 7 of clock 1... 0x0122, got 0x0122 Passed.
[00:00:00] Testing register 8 of clock 1... 0x0004, got 0x0004 Passed.
[00:00:00] Testing register 9 of clock 1... 0x4002, got 0x4002 Passed.
[00:00:00] Testing register 10 of clock 1... 0x0180, got 0x0180 Passed.
[00:00:00] Testing register 11 of clock 1... 0x0000, got 0x0000 Passed.
[00:00:00] Testing register 12 of clock 1... 0x40D2, got 0x40D2 Passed.
[00:00:00] Testing register 13 of clock 1... 0x0180, got 0x0180 Passed.
[00:00:00] Testing register 14 of clock 1... 0x0000, got 0x0000 Passed.
[00:00:00] Testing register 15 of clock 1... 0x0002, got 0x0002 Passed.
[00:00:00] Testing register 16 of clock 1... 0x0010, got 0x0010 Passed.
[00:00:00] Testing register 17 of clock 1... 0x0000, got 0x0000 Passed.
[00:00:00] Testing register 18 of clock 1... 0x001B, got 0x001B Passed.
[00:00:00] Testing register 19 of clock 1... 0x0040, got 0x0040 Passed.
[00:00:00] Testing register 20 of clock 1... 0x0000, got 0x0000 Passed.
[00:00:00] Reading register 21 of clock 1... 0x0005
Clock Ref is SECONDARY of clock 1
[00:00:00] Clock 1
[00:00:00] Reading register 21 of clock 1... 0x0001
[00:00:00] Passed
[00:00:00] CDCM ClkGen Start Complete
[00:00:00] BootMode : MMC/SD Boot
[00:00:00] BOOTMODE ON set to 0 Begin
[00:00:00] SOC RST Begin
[00:00:01] SOC RST Complete
[00:00:01] BOOTMODE ON set to 1 Complete
[00:00:01] BOOT COMPLETE
---
Performed another test: The GPIO Led Blink Application works and prints this to the serial console:
▒▒
**** PDK SBL ****
SBL Revision: 01.00.09.02 (Dec 20 2018 - 04:24:20)
Begin parsing user application
GPIO Led Blink Application
The LEDS blink
Best regards
Adam
Adam,
There are few things from SW perspective that we typically like to check out on the EVM with regards to UART:
1. In UART boot mode do you see the pin character "C" on the serial terminal. The ROM on the K2G SOC configures the UART peripheral and sets baud rate as 115.2kbps and tries to read image using XMODEM protocol. In the process, when it doesn`t get an image it sends ping character "C" periodically over a time internal
2. We provide the diagnostic tests that our board manufacturer runs on the EVM in the Processor SDK RTOS which also includes a test for UART2USB. HAve you run the diagnostics. You can run them using SD boot using instructions here:
3. Can you also confirm that on the EVM where UART is working vs not working the SYSCLK_SEL setting (J15) on the EVM matches and has jumper on pin1 and 2
4. When booting GPIO example when the application fails to print anything, have to connect to A15 core using on board emulator and checked the Program counter?
Regards,
Rahul
Hi Rahul,
thanks a lot for your reply.
1. I do not boot from UART.
2. I ran diagonstic tests on the partially working board (fourth EVM):
▒
**** PDK SBL ****
SBL Revision: 01.00.09.01 (Jul 27 2018 - 03:12:32)
Begin parsing user application
SD Boot - file open completed successfully
DIAGNOSTIC TEST FRAMEWORK
Command options:
help - displays this help menu again
run - run a diagnostic application
status - prints the test status
[Diag Menu]:
Select test number (1 - 16): 16
Parsing uart2usb_TEST
Running uart2usb_TEST
Testing UART print to console at 115.2k baud rate
Press 'y' to verify pass: y
▒
Please notice the "▒" character before the PDK app prints its message and during the uart2usb test.
The non-working board (third EVM) just prints the "▒" character and the diagnostic application does not show up.
The fully working board (the first EVM) does not print the "▒" character when PDK diagnostics start, but it DOES so when running the uart2usb test, i.e. the output is exactly as the one from the fourth EVM.
3. I confirm that on both EVMs (third and fourth): the non-working and the working, the SYSCLK_SEL setting (J15) on the EVM has jumper on pin 1 and 2.
4. I am not sure if I did it correctly. I powered up the EVM, then in CCS launched the Target configuration and connected, but then the GEL is run. The Program Counter is at 0x00000124.
Best regards,
Adam
Adam,
I am discussing this internally with our EVM team and will get back to you next week for further guidance.
Regards,
Rahul
Adam,
Sorry for the delay in getting back to you. We have reached out to the program manager and out EVM manufacturer to check on how to analyze the non-working board since the issue is consistently reproduced and not recoverable. No internal users or customers have reported such issues with these boards so it is a little perplexing to see that you have 2-3 boards that behave in this manner. We think that there is something specific to your setup that is causing the issue:
With Sd booting failing the possible reasons for failure are many ranging from boot switch is not setting SD boot correctly, issues with the SD card connector and UART connector or the FTDI UART2USB circuitry not printing the debug logs, etc. So we should try and isolate SD connector and boot from this setup and focus purely on the scenarios where the UART fails after a period of time even when code is loaded over the on board emulator.
Can you please provide a picture of your power adapter with its voltage and current rating and a small video of your setup with the same connections and setup with which the issue is observed on the non working board. Also, please confirm that you are using the Mini USB cables provided in the EVM kit and connecting to standard USB port on the host without any hub/adapter. Also, indicate during the time when you have used the EVM was there any additional daughter cards or connections that you have made to the EVM. For Example, USB host/device connections. HDMI connections to display, PCIe connection to host, etc?
Regards,
Rahul
Adam,
I have merged the older thread with this new E2E that you have opened so all of the discussion is consolidated in the E2E post. Can you share what issue do you need our help with. Are you still having issues with the K2G EVMs as you indicated in the previous posts from last year.
Regards,
Rahul
Hi Rahul,
thank you for reopening the thread.
Yes, with the problems we faced and the three out of four EVMs not working, we eventually had no other option but to switch to different manufacturer both for the signal processing part and for the microphone array. Now that we have sucessfully finished the project with the other hardware I wanted to return to the EVMs and do the tests you suggested. I will be back here with the results next week.
Best regards,
Adam
Yes, we will keep the thread open and wait for your results. The thread gets locked after two weeks on no activity so I will check back at the end of next week to see if you any new findings to share.