Hello al,
I am newbie about porting Linux on a ADS512101 Dev tool and I don't
know how to put the video display at work. The only thing that works
is the serial interface and I find no information to switch to the LCD
display.
Can some one help me please, thank you.
Best regards
Edgar
It is mentioned in the MPC8313E manual (4.2.2 step #10) that TRST must
not be asserted except when PORESET is asserted. The mpc8313erdb bug
was that the board was not complying with this.
ok, I see.
The board did not comply to the spec and as a side-effect PMC
registers could not be
On 01/18/2012 04:16 AM, Norbert van Bolhuis wrote:
Yes this is it!
You mentioned mpc8313erdb bug before, I guess you had to mention it
twice before
I looked at mpc8313erdb bug description.
The mpc8313erdb bug is described as follows:
3.5 Power management control (PMC) registers cannot be
On 01/17/12 23:09, Scott Wood wrote:
...
If CPU is stuck in sleep, JTAG will send HRESET or SRESET (i'm nor sure
which one it is) and u-boot is needed to reconfigure CPU and DDR2 SDRAM
ctrl.
Why is a reset needed in order to examine physical memory?
Because CPU is stuck in sleep and I
On 01/16/12 21:22, Scott Wood wrote:
On 01/13/2012 08:13 AM, Norbert van Bolhuis wrote:
I dumped SIPNR/SIMSR and uart IIR/EIR (since console triggers wake-up)
but they do not change just before entering standby (via
mpc6xx_enter_standby
which omits setting MSR_POW). uart IRQ is always enabled,
On 01/17/2012 10:56 AM, Norbert van Bolhuis wrote:
On 01/16/12 21:22, Scott Wood wrote:
On 01/13/2012 08:13 AM, Norbert van Bolhuis wrote:
I dumped SIPNR/SIMSR and uart IIR/EIR (since console triggers wake-up)
but they do not change just before entering standby (via
mpc6xx_enter_standby
On 01/13/2012 08:13 AM, Norbert van Bolhuis wrote:
I dumped SIPNR/SIMSR and uart IIR/EIR (since console triggers wake-up)
but they do not change just before entering standby (via
mpc6xx_enter_standby
which omits setting MSR_POW). uart IRQ is always enabled, unmasked and
not pending.
I
On 01/06/12 22:03, Scott Wood wrote:
On 01/06/2012 07:53 AM, Norbert van Bolhuis wrote:
On 01/05/12 19:22, Scott Wood wrote:
On 01/05/2012 09:58 AM, Norbert van Bolhuis wrote:
thanks for your response.
not setting MSR_POW gives same result.
OK, so you're not getting an interrupt
On 01/05/12 19:22, Scott Wood wrote:
On 01/05/2012 09:58 AM, Norbert van Bolhuis wrote:
thanks for your response.
not setting MSR_POW gives same result.
OK, so you're not getting an interrupt regardless of low-power state.
Check whether the interrupt is getting masked during standby
On 01/06/2012 07:53 AM, Norbert van Bolhuis wrote:
On 01/05/12 19:22, Scott Wood wrote:
On 01/05/2012 09:58 AM, Norbert van Bolhuis wrote:
thanks for your response.
not setting MSR_POW gives same result.
OK, so you're not getting an interrupt regardless of low-power state.
Check whether
On 01/04/12 22:08, Scott Wood wrote:
...
It's been a while since I've touched this, but IIRC the PMC events are
mainly important for deep sleep, and for normal sleep (standby) you can
wake from any interrupt other than core interrupts like timebase. I'm
not sure to what extent setting
On 01/05/2012 09:58 AM, Norbert van Bolhuis wrote:
thanks for your response.
not setting MSR_POW gives same result.
OK, so you're not getting an interrupt regardless of low-power state.
Check whether the interrupt is getting masked during standby preparation.
Does the interrupt handler run
after entering:
echo standby /sys/power/state
I'm unable to wake up the MPC8313 (on our custom designed
MPC8313 board).
I need it to wake up through GPIO IRQ.
I cause multiple GPIO interrupts (all properly handled by an isr),
but the MPC8313 does not wake up.
How should one wake up via
On 01/04/2012 10:19 AM, Norbert van Bolhuis wrote:
after entering:
echo standby /sys/power/state
I'm unable to wake up the MPC8313 (on our custom designed
MPC8313 board).
I need it to wake up through GPIO IRQ.
I cause multiple GPIO interrupts (all properly handled by an isr),
but
14 matches
Mail list logo
