From: Eugen.Hristev at microchip.com <Eugen.Hristev@microchip.com>
To: u-boot@lists.denx.de
Subject: SAMA5D3 Xplained: SPL broken after panic added to /lib/time.c:94
Date: Mon, 5 Apr 2021 12:44:41 +0000 [thread overview]
Message-ID: <c3c32aff-7635-4ceb-bcbb-ce113519c3fd@microchip.com> (raw)
In-Reply-To: <8AS1RQ.LLEADDUOJVBP2@gmail.com>
On 4/4/21 7:25 PM, Manuel Reis wrote:
> Hi again,
>
> I guess I misunderstood things a bit. Apologies for that.
> Nevertheless, timer_init in board_init_f is pointing to the weak
> timer_init in /lib/time.c, which is empty.
>
> Is there a way we can force start the pit timer?
> Any pointer would be very helpful. Let me know if you'd like me to do
> something in particular.
>
> Thanks
>
>
>
> On sex, 2 abr, 2021 at 18:15, Manuel Lu?s Reis <mluis.reis@gmail.com>
> wrote:
>> FYI:
>>
>> the output from serial port:
>> <debug_uart>
>> board_init_f spl_atmel.c 130 mem_init 182 ddr2_init mpddr.c 66udelay
>> lib time.c 196__udelay lib time.c 177Could not initialize timer (err
>> -11)
>>
>> udelay lib time.c 196__udelay lib time.c 177Could not initialize
>> timer (err -11)
>>
>> udelay lib time.c 196__udelay lib time.c 177Could not initialize
>> timer (err -11)
>> ...
>>
>>
>>
>>
>> On Fri, 2 Apr 2021 at 18:12, Manuel Lu?s Reis <mluis.reis@gmail.com>
>> wrote:
>>>
>>> ?> As it seems from the dump of dm_dump_all() the atmel_pit_timer is
>>> not
>>> ?> probed. I did a bit of debug and the dm_timer_init() ->
>>> ?> uclass_first_device() -> uclass_find_first_device() found zero
>>> timers
>>> ?> registered for UCLASS_TIMER. The driver is compiled.? Also
>>> checked that
>>> ?> atmel_pit_timer probe function is not called at all. The question
>>> should be
>>> ?> why it is not probed at all?
>>>
>>> ?Hi,
>>>
>>> ?So, I put objdump and puts to some good use and could backtrace the
>>> ?initial error to a udelay call in ddr2_init function on mpddr.c
>>> file.
>>> ?This function is called from mem_init on
>>> ?sama5d3_xplained/sama5d3_xplained.c, which in turn is called from
>>> ?board_init_f on spl_atmel.c.
Hi Manuel,
As Sean Anderson pointed out : the call to timer must have not worked at
all before this change that now breaks things.
Have you tried removing the call to the timer from this mem_init, to see
if this makes the board boot correctly ?
In mem_init I guess there are multiple calls to this timer function.
>>> ?I couldn't, however, find which timer_init function is being called
>>> ?here. I still have a few to try, but disassembly gives me a pretty
>>> ?empty function:
>>>
>>> ?00303690 <timer_init>:
>>> ?? 303690:?????? e3a00000??????? mov???? r0, #0
>>> ?? 303694:?????? e12fff1e??????? bx????? lr
>>>
>>> ?This work didn't give me many answers, but I got a couple of newbie
>>> questions:
>>>
>>> ?Why is it calling board_init_f from spl_atmel.c and not spl_at91.c?
>>> ?Isn't the latter the appropriate architecture for this board?
>>> ?Do you know which timer_init function it is getting here?? Could
>>> this
>>> ?be the reason timer isn't getting probed?
>>>
>>> ?Cheers,
>
>
next prev parent reply other threads:[~2021-04-05 12:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 11:06 SAMA5D3 Xplained: SPL broken after panic added to /lib/time.c:94 Manuel Luís Reis
2021-03-23 11:14 ` Eugen.Hristev at microchip.com
2021-03-23 11:28 ` Manuel Luís Reis
2021-03-23 11:38 ` Eugen.Hristev at microchip.com
2021-03-23 13:20 ` Manuel Luís Reis
2021-03-23 16:08 ` Manuel Luís Reis
2021-03-23 16:26 ` Eugen.Hristev at microchip.com
2021-03-23 16:54 ` Manuel Luís Reis
2021-03-24 0:34 ` Sean Anderson
2021-03-25 10:25 ` Claudiu.Beznea at microchip.com
2021-04-02 17:12 ` Manuel Luís Reis
2021-04-02 17:15 ` Manuel Luís Reis
2021-04-04 16:25 ` Manuel Reis
2021-04-05 12:44 ` Eugen.Hristev at microchip.com [this message]
2021-04-05 12:47 ` Manuel Luís Reis
2021-04-05 13:58 ` Eugen.Hristev at microchip.com
2021-04-05 15:42 ` Manuel Luís Reis
2021-04-05 16:00 ` Eugen.Hristev at microchip.com
2021-04-05 17:50 ` Manuel Luís Reis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c3c32aff-7635-4ceb-bcbb-ce113519c3fd@microchip.com \
--to=eugen.hristev@microchip.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox