Actions
Forum Thread Details
  • State Verified Answer
  • Replies 5 replies
  • Subscribers 318 subscribers
  • Views 963 views
  • Users 0 members are here
Related

Picozed Not Booting sometimes

nithinsteffy

Hi Team, 

I've my new Picozed FMC Carrier Card Gen 2 equiped with Picozed 7015/7030 SOC on it.

I've successfully done booting through SD card with a prebuilt petalinux image.

Now most of the time, board is not booting up properly

it's showing kernal panic error and getting stuck during booting process

Because of this i even can't access the root directory.

Any solution for this?

Warm regards

NITHINkernel errorimage

Parents
  • 0

    I don't know the answer, I have not used this board, but it looks like the issue could be anything, from flaky (or underpowered) power supply, to hardware fault to misconfiguration or faulty image. On the (kind of) positive side, you've got two unrelated errors occurring, since the second screenshot shows an EEPROM-related issue which is completely different to what occurred for the kernel panic screenshot, so that might point to (say) a power supply issue.

    If it were me, I'd want to have some diagnostic test suite created (could be Linux based or bare metal) that would exercise all the memory and storage repeatedly, and all your board peripherals like EEPROM etc., and then run that under all the conditions you expect. I've done that on other computer hardware, it obviously takes time to create that, but proved to be extremely handy to either find design faults, or weed out faulty hardware units.

  • 0 in reply to shabaz

    second screenshot is not error, you can see that i've accessed root by logging in successfully. 

    I posted it to make it clear that , the issue occurs frequently but not all time.

  • 0 in reply to nithinsteffy

    It doesn't significantly change the suggestions unfortunately. It could still be a power-supply related issue or faulty hardware or memory configuration which may be 'on the edge'. If this is for a commercial use-case, then it would be worth writing code to exercise the entire board, including presenting a processor load and reading/writing to all memories and storage cards if present. Or you could try to swap out things (e.g. PSU, PSU cable, PicoZed board, memory card (if that's what you're using), and so on, but that won't identify all issues. That's why a suite of tests that you can run are important, and test the board and configuration under different conditions (e.g. hot and cold temperatures) if this is a commercial project. Otherwise, it's almost as good as guaranteed there will be problems in the field.

Reply
  • 0 in reply to nithinsteffy

    It doesn't significantly change the suggestions unfortunately. It could still be a power-supply related issue or faulty hardware or memory configuration which may be 'on the edge'. If this is for a commercial use-case, then it would be worth writing code to exercise the entire board, including presenting a processor load and reading/writing to all memories and storage cards if present. Or you could try to swap out things (e.g. PSU, PSU cable, PicoZed board, memory card (if that's what you're using), and so on, but that won't identify all issues. That's why a suite of tests that you can run are important, and test the board and configuration under different conditions (e.g. hot and cold temperatures) if this is a commercial project. Otherwise, it's almost as good as guaranteed there will be problems in the field.

Children
No Data