Linux - MobileThis forum is for the discussion of all topics relating to Mobile Linux. This includes Android, Tizen, Sailfish OS, Replicant, Ubuntu Touch, webOS, and other similar projects and products.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
WonderMedia Technologies, Inc.
W-Load Version : 0.17.00.00
ethaddr............found
U-Boot 1.1.4 (Apr 1 2010 - 16:26:54)
WonderMedia Technologies, Inc.
WMT U-Boot Version : 0.12.01.00.14
U-Boot code: 03F80000 -> 03FB9294 BSS: -> 040076AC
RAM Configuration:
Bank #0: 00000000 128 MB
boot from spi flash.
flash:
Bank1: FF800000 -- FFFFFFFF
Bank2: FF000000 -- FF7FFFFF
Flash: 16 MB
In: serial
Out: serial
Err: serial
### main_loop entered: bootdelay=1
bootcmd="mmcinit;fatload mmc 0 0 script/logo.bmp;cp.b 0 c300000 11ffff;logo show" THIS is where I screwed things up!
ATSMB Host 390KHz
SD2_0 : SDHC card!
Init : card selected !
SD:Four Bits Mode!
SD Card High Speed!
Initial SD Card OK!
ATSMB Host 25MHz
SD clock is 25Mhz
register mmc device
part_offset : 10, cur_part : 1
part_offset : 10, cur_part : 1
reading script/logo.bmp
Tina_Match: isdir 0x1######################
mydata :
Size of clusters in sectors : 8
The sector of the first cluster, can be negative : f40
Current FAT buffer : 03f4d704
fatbufnum : ffffffff
Length of FAT in sectors : 798
Size of FAT in bits : 20
Starting sector of the FAT : 20
Start sector of root directory : f50
1152054 bytes read
If ANYONE can help me 'clean' this thing up, I'd appreciate it!
EDIT (3-4-11) 'affecting' the BMP doesnt help, nor having the SD card out...
I fear I have another battery-operated paperweight. Ugh.
If I cannot find a way to sneak back in... I'll have to close this thread.
At least I learned ALOT... but it wouldnt be worth buying YET ANOTHER one to go again.
Workin' in da coal mine... goin' DOWN, down, down!
I have been unsuccessful in finding any other way to clear the stored 'oops' that I made...
So,
I am going to delve into the idea of removing/reprog-ing/replacing the SPI flash. X 2k!
This means tho, that I can 'experiment' with the 'hard brick',
(New name designation - original 'get-NOTHING-from-it' machine is the 'hard brick',
while the current 'gets-logo-loaded-and-sits-there' machine is the 'soft brick'.)
and, presuming I am successful with it,
will be able to replicate the process for the 'soft brick'.
Since BOTH are now setup for the serial I/O connection, I can then manipulate their innards to my heart's content!
(Are my eyes starting to look a bit 'slanted'? )
So, NO closing of the rabbit hole, please!
HEY ALICE!!! WAIT for ME!!
Oh happy day!
When I realized (last nite) that the 'soft brick' has a JTAG connector spot!
Now all I have to do is find a suitable connector/software to work with it!
It still leaves the problem of the 'hard brick' tho... Perhaps going with an actual SPI programmer and removing the chips (which would need done to the 'hard brick' anyway) would be the better 'long-term' bet.
Perhaps the 'soft brick' should become a programming station... Hmmmmmmm...
EDIT:
Im getting confused... everything Ive read claims that the 25040t (Edit: MAY be 25 Q 40) chip shown on the CPU board is a 4k (8M)-BIT SPI chip... meaning only 512(k) bytes...
NO WAY that thing can hold 16Mb of data as suggested by u-boot and the mtdblock info!
Is it being held INTERNALLY by the 8505?
IF that is true there is NOTHING I can do about the 'hard brick'... since it has no JTAG connectors (that I am aware of...)
Downer.
Last edited by justboo2u; 03-14-2011 at 07:32 PM.
Reason: lousy math! :/
Now all I have to do is find a suitable connector/software to work with it!
It still leaves the problem of the 'hard brick' tho... Perhaps going with an actual SPI programmer and removing the chips (which would need done to the 'hard brick' anyway) would be the better 'long-term' bet.
Perhaps the 'soft brick' should become a programming station... Hmmmmmmm...
EDIT:
Im getting confused... everything Ive read claims that the 25040t chip shown on the CPU board is a 4 k-BIT SPI chip... meaning only 512 bytes...
NO WAY that thing can hold 16Mb of data as suggested by u-boot and the mtdblock info!
Is it being held INTERNALLY by the 8505?
IF that is true there is NOTHING I can do about the 'hard brick'... since it has no JTAG connectors (that I am aware of...)
Downer.
It's maybe a sort of "ram-chip" soldered by the guys who made that "smartbook".
Tore the 'hard brick' apart again last nite...
(Amazing how easy it is when the screws are left out!)
The ONLY OTHER IC I could find that MIGHT POSSIBLY be an SPI flash was:
an SOIC-8 with
028L1
P3476
on it.... just like that, 2 lines. (Necessary cause the little SOB is so... little. )
As NONE of that looks close enuf to a production code,
I can only guess that it ALL is a 'number' of some sort...
But...
I cannot find any reference to any SPI 128Mbit (16MB) flash chips that come CLOSE
to this...
I fear Im gonna have a collection of these broken things soon... I already paid for a sylvania-type beast, and may be picking up more...
At least Ill have plenty of 'comparison' items... gawd.
The 'soft brick' still does exactly the same thing.
I found an ethernet cross cable... not that it does any good right now....
May have to break down and get that JTAG interface like I threatened to do...
A side note...
These ICs are so FREAKING SMALL I have to take my contacts OUT and THEN use the READING GLASSES to see what's on 'em!
Even THEN, I often need the Ultra-SUPER flashlight shining 'just so'...
While I dont know if it has been done before, I am attempting to create a 'memory map' of what this beast looks like before linux gets its paws on it...
Linux probably would show me what I want to know... but that will have to wait until it RUNS AGAIN!
Well, the Sylvania should be in the mailbox when I get home tonite...
It supposedly has a display issue, but as long as the u-boot hasnt been wiped out, I wont complain... Im sure the 'hard brick' can/will supply any (and I DO mean ANY) parts required/possible!)
While not officially the subject of this thread, I will include whatever useful info I can glean from it while oscillating about how/what to do with the 'soft brick'.
I am certain that the only way to correct its 'confusion' is to get the JTAG unit and learn how to use it.
Will likely order it from Ebay today... It is capable of directly programming SPIs as well as JTAG interfacing, so it will be more versatile than either/or.
1) The display is broken. (known issue)
.. No biggie - display from 'hard brick'. Problem fixed... all is good!
2) The version of CE-6 is better than the last one.
.. Unfortunately I didnt wait to make a copy of it.
.. Attempting to connect the Linux external messed things up as the internal NAND was not showing as /dev/sda
.. so the external drive did not show as /dev/sdb... and I lost the original CE in the process... Oh well.
3) Yet Another Version of the system board/CPU daughterboard...
.. This one has the NAND 'attached' like the 'hard brick'. It is also recognized as MTD bwo Linux.
4) The 2Gb NAND shows defects...
.. Wasnt expecting this... but am aware that it is somewhat common... perhaps the EXT2 transition will 'clear it up'... ? (hope, hope!)
5) NO JTAG connection!
.. I brick this one Im SCRWD!!!
Tonite I will 'serialize' it and talk directly to u-boot... With this unit I must relearn what I know to manipulate the internal NAND into EXT2, OR get into the idea of it being segmented (and learn how to re-segment it 'better')...
Once again, I get into a rush and mess things up. I thought I was going to brick this unit too... as I attempted to Android it, and it 'locked up' when trying to change w-boot!!! I had to power-off and feared the worst, but the Linux boot SD showed the 'slider-bar' so a SEVERE sigh of relief was heard!
I was able to confirm one thing... the attempt to load CE onto the 'soft brick' failed because the NAND was not configured as expected... this unit, even after the android failure, took the (inferior) CE reinstall just fine...
Going to play some here at work and see if it can be configured ext2 as the 'soft brick' was...
I think I like that arrangement better tho it will require more work with the logo/sysload/etc...
EDIT:
NO MORE ANDROID!!!! Not EVEN gonna try that again! Would rather have 'full-blown' Linux anyway!
Some interesting differences here, too.
Most notably, the SPI shows the INFO on it...
That it is 8.5Mb not 16...
That w-load AND u-boot are newer versions than Ive been working with.
Unknown what the ORIGINAL versions were in the 'hard' and 'soft brick's...
WonderMedia Technologies, Inc.
W-Load Version : 0.19.00.01 ** NEWER **
ethaddr............found
WMT # help
shutdown the board ** 'missing/defective?' **
? - alias for 'help'
autoscr - run script from memory
base - print or set address offset
bdinfo - print Board Info structure
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootm - boot application image from memory
bootp - boot image via network using BootP/TFTP protocol
cleanlcd - clean LCD screen
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
dhcp - invoke DHCP client to obtain IP/boot params
diskboot- boot from IDE device
dmacp - dma memory copy
echo - echo args to console
erase - erase FLASH memory
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
fatstore - store binary file to a dos filesystem
flinfo - print FLASH memory information
go - start application at address 'addr'
help - print online help
ide - IDE sub-system
iminfo - print header information for application image
imls - list all images found in flash
itest - return true/false on integer compare
lcdinit - initialize LCD
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
show -
loop - infinite loop on address range
md - memory display
mii - MII utility commands
mm - memory modify (auto-incrementing)
mmcinit - init mmc card
msleep - delay execution for some time
mtest - simple RAM test
mw - memory write (fill)
nand - NAND sub-system
nfs - boot image via network using NFS protocol
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
randmac - generate a random MAC address and save to "ethaddr" environment variable
rarpboot- boot image via network using RARP/TFTP protocol
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
sdwaitins - wait sd card inserted or removed
sdwaitins 0 -- waiting removed
sdwaitins 1 -- waiting inserted
setenv - set environment variables
shutdown the board
sleep - delay execution for some time
textout - show text to the screen
textout x y "str" color
color is 24bit Hex, R[23:16], G[15:8], B[7:0]
for example: textout 0 0 "hello world" FFFFFF
tftpboot- boot image via network using TFTP protocol
tmpt - execute Mass Production Tool
uploadfile- Transfer the spi flash image to the server.
version - print monitor version
WMT #
** Allowed to load linux system
.. ALL SORTS of 'interesting stuff' shows up when WinCE loads!
**
WonderMedia Technologies, Inc.
W-Load Version : 0.19.00.01
ethaddr............found
Got in thru serial last nite after work and found that the lcdinit had 'disappeared'...
So did the logo...
but that was a 'fairly easy' fix!
BUT!
I managed to copy the uzImage.bin (kernel) file to NAND at 0...
then was able to successfully CHANGE the BOOTCMD to use it!
Although it still needs the external HD (sda1) for the filesystem,
IT BOOTS without AN SD CARD!!!
All that needs done now is to figure where/how to place the filesystem,
and change the BOOTARGS to reflect /dev/mtdblock9/7/whatever...
Well, as of 1745h there is a filesystem on mtdblock9...
I'll have to wait till I get home to change to it & see if it works!
** nervous anticipation **
IT WORKS! I finally 'repair' something that WORKS!!! Now, to 'rearrange' the filesystem & 'populate it' to my liking!
EDIT:
Found another site that CONFIRMS that the 25Q40 chip (4Mbit=512Kbyte) IS the one I need to 'fix' for the 'hard brick', and if the JTAG method proves unsuccessful in cleaning up the 'soft brick' that device can also be used to clean/repair the SPI flash 'out-of-circuit'...
SOooooo,
Will de-solder the 'hard brick' and JTAG the 'soft brick' and finish up with 'the new guy'...
Late nite musings...
4Mbit = 512K Byte... seems so little... and yet CP/M runs in 64K... how spoiled we've become!
Now,
It appears that I will have to learn the 'programming script' IOT work with the 'soft brick' after I finish setting up the connector...
(The arrangement of the pins is 'a bit different' than the brick...)
It is unlikely to do anything 'useful' by simply plugging in. Apparently I expected something else...?
Like,
POOF!!! It's fixed!
Also ordered the adapter for the 'unconnected chip'...
Yet More Money!
Tonite I will get the connector finished and can start 'playing' with the programmer...
What kind you asked? Oh... sorry.
Got one of the BlackCat USBs off ebay. Decent price, seems to be ready to go (in Win7) except for the nasty-little-script-thing...
Soon I expect to put a banner here saying that the 'soft brick' is no longer a brick at all!
Ahhh... the daydreams of a solder-junkie!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.