kendryte / k510_buildroot

Kendryte K510 SDK
BSD 2-Clause "Simplified" License
117 stars 57 forks source link

[Bug]: Both OS on emmc and tf-card boot not every time #460

Closed sevocrear closed 11 months ago

sevocrear commented 1 year ago

What happened

Hello everyone,

I have boot and connections problems with k510.

After powering on the kendryte K510, it boots not every time. I need to push K2 (reset) button several time in a row in order to make it work and boot successfully. Also, the same happens even if I boot not with emmc, but with tf-card.

I either get black screen of k510, or the broken logo screen.

Initially I thought that the problem is in the power supply, so I tried different adapters 15 W, 20 W, 25 W. But it didn't fix the issue.

Also, despite the fact that it struggles the boot, when it boots successfully, I can't work with the "screen". The terminal is slow and laggy (while having serial connection with k510). It's impossible to write commans or change the files with vim, for example.

k510 connection (power and UART): image

There are some photos of the bugs:

  1. Sometimes it stops loading the kernel and just stucks image

  2. Sometimes it show the errors: image

  3. It can also show either black screen or broken logo screen image

image

Rarely, it boots successfully and runs the program:

image

Reproduction steps

  1. Switch boot to emmc or tf-card

  2. Connect the board to power supply

  3. Connect the board to UART-USB

  4. Power-on the board

    • Connect to the board
sudo screen /dev/ttyUSB0 115200

or

picocom -b 115200 -f h /dev/ttyUSB0

Hardware board

k510 crb kit

Software version

2ce01d00b2d0f6925656ce207c84504d972a1b0f

Bug frequency

occurs 8 out of 10 times

Anything else

No response

MrThanlon commented 1 year ago

Can you try using another TF card? It's possible that the image file error was caused by a damaged TF card.

chenhb3 commented 11 months ago

@sevocrear please help to check info:Can you try using another TF card? It's possible that the image file error was caused by a damaged TF card.

ps:If there is no feedback on the results or situation for more than 7 days, the issue will be closed.If you have any questions later, please create it again, thank you!