Robin Mallinson
|
Re: RE: Issue using BDI2000 cheat sheet with BDI3000
|
Robin Mallinson
10/19/2010 5:10 AM
post71187
|
Re: RE: Issue using BDI2000 cheat sheet with BDI3000
Thanks. I don't know what's happened to the I/O. The target has uboot configured with a 10 second bootdelay. In my
setup the bdi stops the target 3 seconds after reset, which stops it during this bootdelay.
I've confirmed that when I interrupt the bootdelay to get to the uboot prompt I can read and write all addresses that
the BDI is trying to write to: (0x100180 to 0x7685b0). Here's a memory test in uboot of that area:
=> mtest 0x100180 0x7685b0 0xaaaaaaaa 1
Pattern AAAAAAAA Writing... Reading...Tested 1 iteration(s) without errors.
=> mtest 0x100180 0x7685b0 0x55555555 1
Pattern 55555555 Writing... Reading...Tested 1 iteration(s) without errors.
=>
This is a pretty crude test, but I've run QNX from this memory before at this location, as uboot normally tftps QNX
there, so I'm confident the memory is good, and that uboot can read/write it. For example here's uboot loading an image
from the same build there, and booting it (note the QNX prompts at the end):
=> tftp $loadaddr $bootfile
Speed: 1000, full duplex
Using eTSEC1 device
TFTP from server 192.168.0.101; our IP address is 192.168.0.102
Filename 'image.ifs'.
Load address: 0x100000
Loading: T T T T #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
###
done
done
Bytes transferred = 6719036 (66863c hex)
=> go $loadaddr
## Starting application at 0x00100000 ...
Board is P2020RDB
board_smp_init: 2 cpu
Looking for Config EEPROM on i2c,0 @ I2C address 0x00000050 ... found
Validating contents ... Error, no signature
Cpu_clk=1000000000, Sys_clk=100000000, CCB=500000000
System page at phys:0000b000 user:0000b000 kern:0000b000
Starting next program at v0015383c
Welcome to QNX Neutrino 6.5.0 on the PowerPC P2020RDB board
fs-etfs-p2020rdb512: readtrans BADBLK on cluster 0
Starting audit service...Interface 0 configured.
Starting I2C driver for I2C interface 1...
Set or Get the Time from Real Time Clock DS3232
rtc get: current RTC time is 2010/10/19 9:3:7 (UTC)
#
# uname -a
QNX localhost 6.5.0 2010/06/23-02:08:13EDT P2020RDB ppcbe
#
So my confusion now stems from the memory appearing to be writeable, but the BDI being unable to write to it. Do you
have any ideas as to what could be preventing the BDI from writing to the same place?
regards,
Robin
|
|
|