[U-Boot-Users] BDI2000 and MPC8260

[U-Boot-Users] BDI2000 and MPC8260

[Alex Zeffertt]

Hi,

I hope this isn't considered off topic here....

I am trying to load u-boot.bin into the flash device on my PM828 board using a BDI2000 and the
config file ftp://ftp.denx.de/pub/BDI2000/pm826.cfg.  On the PM828 platform the HRW - hard reset
configuration word- is loaded into the CPU from bottom of the flash device on CS0.

The problem I am seeing is that the bdi2000 cannot communicate with the PM828 if the HRW is not
present in the flash device.  I.e. you need u-boot.bin already loaded into flash in order to load
u-boot.bin into flash!

At the moment I can work around this problem by setting some jumpers on the board to remap CS0 to a
PROM device containing u-boot, writing the HRW into flash, and returning the jumpers so that CS0 is
mapped to the flash again.  Unfortunately I will not be able to do this on our custom hardware as
there will only be a flash device and no PROM.

Here is the output from the BDI2000 session when the flash on CS0 is erased (i.e. the HRW is
0xffffffff):


- TARGET: waiting for target Vcc
- TARGET: waiting for target Vcc
- TARGET: waiting for target Vcc

	[ PM828 is switched on ]
	
- TARGET: processing power-up delay
- TARGET: processing user reset request
- BDI asserts HRESET
- Reset JTAG controller passed
- Bypass check: 0x00000001 => 0x00000001
- JTAG exists check passed
- COP status is 0x01
- Check running state passed
- BDI scans COP freeze command
- BDI removes HRESET
- Target PVR is 0x80822011
- COP status is 0x05
- Check stopped state passed
- Check LSRL length passed
- BDI sets breakpoint at 0xFFF00100
- BDI resumes program execution
- Waiting for target stop passed
- TARGET: Target PVR is 0x80822011
- TARGET: resetting target passed
- TARGET: processing target startup ....
- TARGET: processing target startup passed

	[ 10 second gap ]

*** TARGET: reset detected, restarting target
- BDI asserts HRESET
- Reset JTAG controller passed
- Bypass check: 0x00000001 => 0x00000001
- JTAG exists check passed
- COP status is 0x05
- Check running state failed
- TARGET: Target PVR is 0x80822011
*** TARGET: resetting target failed
# PPC: unexpected response from target
- TARGET: target will be restarted in 10 sec
- TARGET: processing user reset request

	[ the above repeats indefinitely ]


Does anybody have any idea how to work around this circular dependency?

Regards,

Alex

[U-Boot-Users] BDI2000 and MPC8260

[Dan Malek]

On Sep 1, 2005, at 6:43 AM, Alex Zeffertt wrote:

> The problem I am seeing is that the bdi2000 cannot communicate with 
> the PM828 if the HRW is not
> present in the flash device.

That doesn't sound quite right, but worst case all you need to do
is pull RSTCONF to ground and the 82xx will use an internal
configuration word to get you going.

Thanks.

	-- Dan

[U-Boot-Users] BDI2000 and MPC8260

[Pantelis Antoniou]

On Thursday 01 September 2005 20:42, Dan Malek wrote:
> On Sep 1, 2005, at 6:43 AM, Alex Zeffertt wrote:
> > The problem I am seeing is that the bdi2000 cannot communicate with
> > the PM828 if the HRW is not
> > present in the flash device.
>
> That doesn't sound quite right, but worst case all you need to do
> is pull RSTCONF to ground and the 82xx will use an internal
> configuration word to get you going.
>
> Thanks.
>
> 	-- Dan
>
>

Yes, that's absolutely true.

If your boot flash is not written correctly, you'd better
have a way to pull RSTCONF low. Different BDI settings are
required however, beware.

Regards

Pantelis

[U-Boot-Users] BDI2000 and MPC8260

[Rune Torgersen]

> -----Original Message-----
> From: Pantelis Antoniou
> Sent: Thursday, September 01, 2005 13:44

> > That doesn't sound quite right, but worst case all you need to do
> > is pull RSTCONF to ground and the 82xx will use an internal
> > configuration word to get you going.

> If your boot flash is not written correctly, you'd better
> have a way to pull RSTCONF low. Different BDI settings are
> required however, beware.

Eh.. According to the 8260 Users manual it is excactly opposite...
(8260UM ch 5.4)
RSTCONF should be tied to GND for reading HRCW from EPROM. RSTCONF
should 
be tied to VCC for slave configuration or if you want to use the default

all 0 HRCW.

[U-Boot-Users] BDI2000 and MPC8260

[Rune Torgersen]

> -----Original Message-----
> From: Wolfgang Denk
> Sent: Thursday, September 01, 2005 10:50
> In message 
> <20050901111214.457804dc.ajz@cambridgebroadband.com> you wrote:
> > 
> > The problem I am seeing is that the bdi2000 cannot 
> communicate with the PM828 if the HRW is not
> > present in the flash device.  I.e. you need u-boot.bin 
> already loaded into flash in order to load
> > u-boot.bin into flash!
> 
> This is normal; with an erased flash, the processor will read a  HRCW
> which  sets external bus arbitration and CPU core disabled - there is
> nothing left for the BDI to communicate with.

We have anoter solution working here. To initally program the HRCW into
flash we use another JTAG device (a Corellis JTAG interface) to wiggle
th pins on the 8260 to program the flash. This works, but is fairly
slow. To program 256 bytes of HRCW takes 10 - 15 seconds.

After this we switch to BDI2000 and program U-Boot.

This way we don't need yet another piece of HW on the board.

[U-Boot-Users] BDI2000 and MPC8260

[Jerry Van Baren]

Rune Torgersen wrote:
>>-----Original Message-----
>>From: Wolfgang Denk
>>Sent: Thursday, September 01, 2005 10:50
>>In message 
>><20050901111214.457804dc.ajz@cambridgebroadband.com> you wrote:
>>
>>>The problem I am seeing is that the bdi2000 cannot 
>>
>>communicate with the PM828 if the HRW is not
>>
>>>present in the flash device.  I.e. you need u-boot.bin 
>>
>>already loaded into flash in order to load
>>
>>>u-boot.bin into flash!
>>
>>This is normal; with an erased flash, the processor will read a  HRCW
>>which  sets external bus arbitration and CPU core disabled - there is
>>nothing left for the BDI to communicate with.
> 
> 
> We have anoter solution working here. To initally program the HRCW into
> flash we use another JTAG device (a Corellis JTAG interface) to wiggle
> th pins on the 8260 to program the flash. This works, but is fairly
> slow. To program 256 bytes of HRCW takes 10 - 15 seconds.
> 
> After this we switch to BDI2000 and program U-Boot.
> 
> This way we don't need yet another piece of HW on the board.

You realize of course that the HRCW is in the first 32 bytes of flash 
and you actually only need 4 bytes (offsets 0,8,16,24).  If you 
optimized your load, you could get the 10-15 seconds down to probably 1 
second.  Since it only needs to be done once in a board's lifetime, this 
may be a "don't care."

Other thoughts:
* Has anyone ever asked Abatron for an ability to use it as a raw JTAG 
accelerator?  It should be unnecessary to have a separate Corellis JTAG 
accelerator to do this.

* Freescale seems to have stopped providing unfettered access to the 
BSDL (Boundary Scan Description Language) interface to their processors. 
  For instance, the MPC8260 is not in the list:
<http://www.freescale.com/webapp/sps/site/overview.jsp?nodeId=0162468rH3bTdGZj9NtRjM>

* JTAG can be bit-banged with a PC parallel port extremely cheaply 
although it is also very slow.

gvb

[U-Boot-Users] BDI2000 and MPC8260

[Dan Malek]

On Sep 6, 2005, at 11:44 AM, Jerry Van Baren wrote:

> Other thoughts:
> * Has anyone ever asked Abatron for an ability to use it as a raw JTAG 
> accelerator?  It should be unnecessary to have a separate Corellis 
> JTAG accelerator to do this.

Newer versions of the BDI2000 have raw JTAG commands that will
provide this access.  A proper 'expect' script should work.

> * Freescale seems to have stopped providing unfettered access to the 
> BSDL

Even with the BSDL, it is a time consuming process :-)

> * JTAG can be bit-banged with a PC parallel port extremely cheaply 
> although it is also very slow.

I usually do this with an 8xx and it's IO pins.


	-- Dan

[U-Boot-Users] BDI2000 and MPC8260

[Wolfgang Denk]

In message <431DB954.9030803@smiths-aerospace.com> you wrote:
>
> * Freescale seems to have stopped providing unfettered access to the 
> BSDL (Boundary Scan Description Language) interface to their processors. 
>   For instance, the MPC8260 is not in the list:
> <http://www.freescale.com/webapp/sps/site/overview.jsp?nodeId=0162468rH3bTdGZj9NtRjM>

We were never able to pass their NDA roadblocks when we asked for the
necessary information to extend the BDM4GDB adapter for 82xx... :-(

> * JTAG can be bit-banged with a PC parallel port extremely cheaply 
> although it is also very slow.

Be careful about the voltages, though.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Brain fried - Core dumped

[U-Boot-Users] BDI2000 and MPC8260

[Jerry Van Baren]

Wolfgang Denk wrote:
> In message <431DB954.9030803@smiths-aerospace.com> you wrote:
> 
>>* Freescale seems to have stopped providing unfettered access to the 
>>BSDL (Boundary Scan Description Language) interface to their processors. 
>>  For instance, the MPC8260 is not in the list:
>><http://www.freescale.com/webapp/sps/site/overview.jsp?nodeId=0162468rH3bTdGZj9NtRjM>
> 
> We were never able to pass their NDA roadblocks when we asked for the
> necessary information to extend the BDM4GDB adapter for 82xx... :-(

Slightly different question, different answer ;-).  The BSDL is 
describing the processor I/O ring shift register, allowing the JTAG to 
wiggle pins.  What you are referring to is the COP (?) debugger 
interface which is also accessed via JTAG but is proprietary.  The BSDL 
_is_ available as Rune pointed out.  This allows you to program memory 
(very slowly) by shifting an {address, data, chip select}, toggle the 
write line, repeat ad nausium.

Note that you have to be careful with wiggling pins via JTAG: if you 
inadvertantly set two pins that are connected together to be "output" 
and set them to fighting, one of them will lose (generally the 
processor).  I would never do that, but know someone who did ;-).

[snip]

> Best regards,
> Wolfgang Denk

Thanks,
gvb

[U-Boot-Users] BDI2000 and MPC8260

[Wolfgang Denk]

In message <431DF2A9.6020301@smiths-aerospace.com> you wrote:
>
> Slightly different question, different answer ;-).  The BSDL is 
> describing the processor I/O ring shift register, allowing the JTAG to 
> wiggle pins.  What you are referring to is the COP (?) debugger 
> interface which is also accessed via JTAG but is proprietary.  The BSDL 

I know the difference. The result was the same :-(

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
You young'uns. That was *long* before AltaVista,  DejaNews,  or  even
(gasp) the *Web*! In fact, we typed that thread on steam-powered card
punchers, and shipped it around via Pony Express.
            -- Randal Schwartz in <8cwww1cd0d.fsf@gadget.cscaper.com>

[U-Boot-Users] BDI2000 and MPC8260

[Alex Zeffertt]

Hi,

I hope this isn't considered off topic here....

I am trying to load u-boot.bin into the flash device on my PM828 board using a BDI2000 and the
config file ftp://ftp.denx.de/pub/BDI2000/pm826.cfg.  On the PM828 platform the HRW - hard reset
configuration word- is loaded into the CPU from bottom of the flash device on CS0.

The problem I am seeing is that the bdi2000 cannot communicate with the PM828 if the HRW is not
present in the flash device.  I.e. you need u-boot.bin already loaded into flash in order to load
u-boot.bin into flash!

At the moment I can work around this problem by setting some jumpers on the board to remap CS0 to a
PROM device containing u-boot, writing the HRW into flash, and returning the jumpers so that CS0 is
mapped to the flash again.  Unfortunately I will not be able to do this on our custom hardware as
there will only be a flash device and no PROM.

Here is the output from the BDI2000 session when the flash on CS0 is erased (i.e. the HRW is
0xffffffff):


- TARGET: waiting for target Vcc
- TARGET: waiting for target Vcc
- TARGET: waiting for target Vcc

	[ PM828 is switched on ]
	
- TARGET: processing power-up delay
- TARGET: processing user reset request
- BDI asserts HRESET
- Reset JTAG controller passed
- Bypass check: 0x00000001 => 0x00000001
- JTAG exists check passed
- COP status is 0x01
- Check running state passed
- BDI scans COP freeze command
- BDI removes HRESET
- Target PVR is 0x80822011
- COP status is 0x05
- Check stopped state passed
- Check LSRL length passed
- BDI sets breakpoint at 0xFFF00100
- BDI resumes program execution
- Waiting for target stop passed
- TARGET: Target PVR is 0x80822011
- TARGET: resetting target passed
- TARGET: processing target startup ....
- TARGET: processing target startup passed

	[ 10 second gap ]

*** TARGET: reset detected, restarting target
- BDI asserts HRESET
- Reset JTAG controller passed
- Bypass check: 0x00000001 => 0x00000001
- JTAG exists check passed
- COP status is 0x05
- Check running state failed
- TARGET: Target PVR is 0x80822011
*** TARGET: resetting target failed
# PPC: unexpected response from target
- TARGET: target will be restarted in 10 sec
- TARGET: processing user reset request

	[ the above repeats indefinitely ]


Does anybody have any idea how to work around this circular dependency?

Regards,

Alex

[U-Boot-Users] BDI2000 and MPC8260

[Wolfgang Denk]

In message <20050901111214.457804dc.ajz@cambridgebroadband.com> you wrote:
> 
> The problem I am seeing is that the bdi2000 cannot communicate with the PM828 if the HRW is not
> present in the flash device.  I.e. you need u-boot.bin already loaded into flash in order to load
> u-boot.bin into flash!

This is normal; with an erased flash, the processor will read a  HRCW
which  sets external bus arbitration and CPU core disabled - there is
nothing left for the BDI to communicate with.

> At the moment I can work around this problem by setting some jumpers on the board to remap CS0 to a
> PROM device containing u-boot, writing the HRW into flash, and returning the jumpers so that CS0 is
> mapped to the flash again.  Unfortunately I will not be able to do this on our custom hardware as
> there will only be a flash device and no PROM.

Install a RCFG jumper... The PM82x modules  have  a  RCFG  jumper  to
bring up the CPU in internal default configuration.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Reader, suppose you were an idiot. And suppose you were a  member  of
Congress. But I repeat myself.                           - Mark Twain

[U-Boot-Users] BDI2000 and MPC8260

[Alex Zeffertt]

Thanks for replying Wolfgang,

Actually I'd figured this out.  I would have sent an update, but I thought my
original email had got lost by the server because it didn't send me back a copy.

Alex 

On Thu, 01 Sep 2005 17:50:14 +0200
Wolfgang Denk <wd@denx.de> wrote:

> In message <20050901111214.457804dc.ajz@cambridgebroadband.com> you wrote:
> > 
> > The problem I am seeing is that the bdi2000 cannot communicate with the PM828 if the HRW is not
> > present in the flash device.  I.e. you need u-boot.bin already loaded into flash in order to
> > load u-boot.bin into flash!
> 
> This is normal; with an erased flash, the processor will read a  HRCW
> which  sets external bus arbitration and CPU core disabled - there is
> nothing left for the BDI to communicate with.
> 
> > At the moment I can work around this problem by setting some jumpers on the board to remap CS0
> > to a PROM device containing u-boot, writing the HRW into flash, and returning the jumpers so
> > that CS0 is mapped to the flash again.  Unfortunately I will not be able to do this on our
> > custom hardware as there will only be a flash device and no PROM.
> 
> Install a RCFG jumper... The PM82x modules  have  a  RCFG  jumper  to
> bring up the CPU in internal default configuration.
> 
> Best regards,
> 
> Wolfgang Denk
> 
> -- 
> Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> Reader, suppose you were an idiot. And suppose you were a  member  of
> Congress. But I repeat myself.                           - Mark Twain