Board halts at "HTLLC" after reset

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Board halts at "HTLLC" after reset

857 Views
william_oqvist
Contributor I

I'm running a Freescale iMX280 that, after upgrading the Linux kernel from 3.14 (Yocto Daisy) to 4.14 (Yocto Rocky), won't boot after resetting it manually in the terminal. When it's trying to boot, it prints HTLLC once and then hangs.

Since not even FSBL has time to load, I'm assuming the problem is a bit deeper than that. Maybe a problem with the flash?

This problem did not exist before the kernel upgrade. Is there perhaps a known problem with the Yocto Rocky?

Has anyone seen this and fixed this before?

Labels (2)
0 Kudos
4 Replies

694 Views
b36401
NXP Employee
NXP Employee

First please make sure that memory is initialized right.
I mean that the calibration is the same as with that 3.14 Linux.
It seems a bootlet (stream of boot image data) has been loaded to memory and called by the boot ROM but then got stuck.

By the way are you getting some error code after this "HTLLC" message?

0 Kudos

694 Views
william_oqvist
Contributor I

Thank you for the reply.

Maybe I wasn't clear, but shouldn't the memory initialization be OK since I can boot it by power resetting? The problem occurs only when I reboot it after it's fully booted, without a power reset.

The complete flow is like this:
1. Insert power cable
2. Boots completely

3. Types 'reboot' in the shell
4. Powers down, trying to boot, and freezes at HTLLC

5. Need to pull the plug and insert it for it to boot again

And no, no error codes after "HTLLC". It just freezes until I pull the plug.

0 Kudos

694 Views
b36401
NXP Employee
NXP Employee

Please note that in case of reboot you need to re-initialize all chips not only processor.
Typically the OS asks PMIC to power cycle everything with "reboot" command.
So I suppose in your case DDR was not re-initialized fine and then fails.

Have a great day,
Victor

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

694 Views
william_oqvist
Contributor I

Thank you for the advice. I solved it by patching spi_flash.h with:
int spi_flash_init(void);

0 Kudos