• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 101 subscribers
  • Views 208 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

PROCESSOR-SDK-AM437X: AM437x-HS:Kernel warning Logs at boot up after rootfs upgrade.

PROCESSOR-SDK-AM437X: PROCESSOR-SDK-AM437X: AM437x-HS:Kernel warning Logs at boot up after rootfs upgrade.

Bhavesh Shah
Prodigy 60 points
Part Number: PROCESSOR-SDK-AM437X

Tool/software:

Hi there,

as discussed in below ticket 

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1377318/processor-sdk-am437x-am437x-hs-kernel-warning-logs-at-boot-up-after-rootfs-upgrade/5265204#5265204

I was taking task forward, while doing some testing I have observed same error in am437x-hs-evm board even though the firmware upgrade is not taking place.

Below are some observations 

  1. Once we created a fresh SD card and placed on board the board got booted. after log in once we do soft reboot we are able to see the same warning messages. it was not generated after that
  2. Once we are doing soft reboot and stop at uboot play with some env variable using setenv and after booting we are seeing this same warning messages. It was random behavior after that.

Based on above observation we can say that the issue is related to the firmware upgrade process but due to some firewall security checks at the start of kernel. 

I hope you can provide some more input related to  this issue 

Regards,

Bhavesh

  • 0
    TI__Guru**** 155901 points

    Hi Bhavesh,

    Can you please disable the &gpmc node in kernel device tree to see if the warning still happens?

  • 0 in reply to Bin Liu
    Prodigy 60 points

    HI Bin

    I tried as you suggested to disable the GPMC from the kernel it self but it was not allowing us to do that. Also tried to enable the CONFIG_OMEP_GPMC_DEBUG kernel config and do some testing. But did not help with the result. 

    it seems that some driver is trying to access the GPMC before it is getting initialized

  • 0 in reply to Bhavesh Shah
    TI__Guru**** 155901 points

    Hi Bhavesh,

    Bhavesh Shah said:
    I tried as you suggested to disable the GPMC from the kernel it self

    Please provide patch or log to show what exactly you did.

    Bhavesh Shah said:
    but it was not allowing us to do that

    Please provide log to show what you meant by "was not allowing".