Hey, real6410/te6410/ok6410 supports jlink V8 + rvds2.2 simulation debugging.

[Good News] hey, real6410/te6410/ok6410 support jlink V8 + rvds2.2 simulation debugging

At the beginning of the year, I tried jlink V8 in te6410/ok6410 and compiled it in rvds2.2. I can read the ID, but I have never tried single-step debugging like 2440 + ads, now, with the cooperation of many netizens and Fei Ling engineers, we have finally succeeded in a single step. Recently, real6410 has made another update, adding interfaces such as JTAG and VGA, Bluetooth, and 3G. Many netizens asked me to confirm whether real6410 can use jlink, because the streaking debugging before entering the OS is very necessary for these beginners. I tried it tonight and it was completely OK. I just found that after we started the jlink system for a long time, we could not find the problem that the kernel thought jlink was broken, this is true for real6410 today. After the system is started, no ID can be read and an error is prompted. Therefore, jlink users should pay attention to this issue in the future. The following figure shows how to read the real6410 ID.

Note:

I. IfArticleIf the title is not marked with [reprinted], gooogleman has original copyright. Do not delete any part of the article during reprinting, and the commercial website must be reprinted with gooogleman's consent.

2. The title of the article is marked with "reprinted". Please also indicate the original author's name and original address when reprinted, and respect the original author.