Pickle Wrote: ------------------------------------------------------- > Bodhi, seeing output is not the issue. im having > issues transmitting to break the boot to get the > uboot terminal. Seeing or not seeing output is a confirmation that the pins connection is correct or incorrect. So now the issue is the connection from your converter TX to the plug RX.by bodhi - Debian
cdlenfert, > it would fall back to Pogo OS as a rescue system > right? Right. > Would it be my current stock OS which > already has SSH enabled, or would I have to find a > way to enable SSH again (I did this initially via > serial cable). As far as SSH it should work as before with your current stock OS. > Or are you just saying that since > it'by bodhi - Debian
Bob, > That one seems to find my spi chip ok: > > dmesg | grep spi > [ 1.118436] m25p80 spi0.0: mx25l3205d (4096 > Kbytes) > That's is actually the same as what you got before (the 2nd line where the kernel determined the right chip after the 1st message). I just want to show you the confirmation.by bodhi - Debian
cdlenfert , Chailoading looks OK for booting. But it will not be running correctly as Pogo V4. Using stock tis way only as a rescue system is OK.by bodhi - Debian
Hi Bob, Rename the attached DTB to dove-wyse-t50.dtb and try booting with it.by bodhi - Debian
Pickle, +----+----+ | | | +----+----+----+----+----+ |3.3V| TX | RX | | GND| +----+----+----+ +----+ Try reverse TX and RX, if seeing no output.by bodhi - Debian
I've updated the u-boot release thread to add a link to where to download the SATA direct booting files. QuoteReferences: ... 3. SATA direct booting tarball.by bodhi - uBoot
> I know JoeyUniverse joined GitHub :-D. A few lucky > days and I should be coherent better. Good for you Joey :)by bodhi - Off-Topic
Hi Koen, > Some more info about mtd. It seems the chip in my > box is 8M while that in Bob's device is reported > to be only 4M although that may possibly be due to > different fw_env.config settings. No, it is not fw_env.config. The size of the mtd is recognized by the kernel when it probes the mtd. So the mtd sizes are correct as the kernel sees. What in the fw_env.conby bodhi - Debian
ElMariachi, I have not tried this compilation yet. However, here is my observation. > Makefile:606: arch/armv5tel/Makefile: No such file > or directory > oot@debian:~/rtl8192eu-linux-driver# make > make ARCH=arm CROSS_COMPILE= -C > /usr/src/linux-headers-4.18.4-kirkwood-tld-1/ > M=/root/rtl8192eu-linux-driver modules ARCH=arm is correct. > ./include/linux/by bodhi - Debian
Telmanager Wrote: ------------------------------------------------------- > Bodhi. > > Thank you very much. > I follow your guide and my system it runs very > well. > > You are excelent my friend. > > <root@debian:~# uname -a > Linux debian 4.12.1-kirkwood-tld-1 #1 PREEMPT Sat > Jul 15 21:40:50 PDT 2017 armv5tel GNU/Linux> Cool!by bodhi - Debian
Koen, > do you want me to try these latest dtb files as > well? I've had another response from Dell that > they will chase the technical team for the uboot > GPL sources of the T50. Sure, please try the latest DTB file (good to do regression test). Hope they will make GPL source available, that will solve the remaining issues for us. The fact that CRC error show up inby bodhi - Debian
That's right, should be either st or macronix. Here is another compilation using st.by bodhi - Debian
Here is the new DTB for Bob and Koen to check SPI flash.by bodhi - Debian
Telmanager, Your system is a mess right now! 1. You've installed U-Boot 2017.07-tld-1, but did not install the default envs image that comes with it. 2. Instead of creating a new USB rootfs using Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 from: https://forum.doozan.com/read.php?2,12096 You've used Jeff's old instruction. ========== So what you need to doby bodhi - Debian
Pickle, I would recommend going ahead and create a new rootfs Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 on USB: https://forum.doozan.com/read.php?2,12096 You need serial console to make sure you can recover if the system crashes while you install new u-boot. But if it is running long enough for you to complete u-boot installation then you can run with USB rootfs. And then come bacby bodhi - Debian
bodhi Wrote: > > Let me find the sector size. The definition in /etc/fw_env.config should be the same. Unless a different u-boot version is on Bob's box, therefore the location is different. I'm compiling a new DTB to see if Bob can use to eliminate that SPI chip variation.by bodhi - Debian
Bob Wrote: ------------------------------------------------------- > Hi bodhi and Koen > > I already tried that (default Ubuntu) config. It > just gives a bad CRC message. > > Perhaps the dtb needs to match my spi chip? I > edited the last dts with the details for my chip > but couldn't figure out how to compile it to a > dtb. Let me find the sectorby bodhi - Debian
Ok so QuoteBob output of cat /proc/mtd: dev: size erasesize name mtd0: 00400000 00001000 "spi0.0" QuoteKoen root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 00800000 00001000 "spi0.0" @Bob, Try using the same fw_env.config as Koen's root@debian:/etc# cat /etc/fw_env.config # MTD device offset sizeby bodhi - Debian
Koen Wrote: ------------------------------------------------------- > Ethernet is > working and the box powers off properly as well. Cool!by bodhi - Debian
Bob, I took a look. There is no envs in there that I can see.by bodhi - Debian
cdlenfert Wrote: ------------------------------------------------------- > One thing I caught in this thread is that you can > put rootfs on a USB, then clone that to and SD > card and swap them out? Is that correct? Yes. It is correct. Same for HDD. The u-boot env that make sure all 3 types of devices are scanned for booting is devices.by bodhi - Debian
AngryCoder, > Any chance you will ever take a look inside the > steam link anytime soon? If you don't plan to, I > might as well get rid of the 5 steam links I > stocked up. As usual, I don't really know when I will start looking at a new box.by bodhi - Off-Topic
Pickle Wrote: ------------------------------------------------------- > Yes that is basically the last line. In the dmesg > output i actually disconnected and reconnected. > > Actually i think might have misunderstood your > request. Did you want me to get the logs from NAS? Yes. > These were logs from attaching the drives to my > laptop. If you mount the driby bodhi - Debian
Bob, > I looked at the source code you mentioned a few > posts back and the mimas board .c file has offset > as 0 for the mtd device (if I'm reading that > right). That's incorrect. That code is the kernel code patch which does not have any info about boot loader. What we lack is the GPL for their boot loader version. And they also turned off input/ouput for this bby bodhi - Debian
Bob, Does your stock OS have the same /etc/fw_env.config as Koen’s?by bodhi - Debian
veriqster, > Now if someone could help me figure out how to > boot of SATA, .... > I've tried the instructions in the SATA thread, That's unescessary. What you saw in the SATA thread was a direct booting mechanism for Pogo V3. One we use for rescue purpose. Since you have installed new u-boot U-Boot 2015.10-tld-2 (Oct 21 2017 - 22:00:02 -0700) The booting procesby bodhi - uBoot
Pickle, Is this the last line in the log? [ 1104.970564] sd 4:0:0:0: Attached SCSI disk I was hoping to see some errors in the log before Quote(issue is that drives seem to drop and the nsa iteself seems unresponsive. Light for hd1 turns orangeby bodhi - Debian
Bob Wrote: ------------------------------------------------------- > Hi bodhi > > I see. I guess I didn't edit the config properly. > It doesn't help that the format is different from > the old Ubuntu version. > > contents of original Ubuntu fw_env.config: > > # MTD device offset size erase_size > /dev/mtd0 0xc0000 0x10000 0x10000 This locaby bodhi - Debian
Bob, > It's unable to read the chip with fw_printenv > after editing fw_env.config. Gives a bad CRC > message. That CRC error does not mean the chip is inaccesible. It means the envs are either at wrong location, or it was not initialized. To determine if the SPI chip was OK, and mtd partition(s) is on it: cat /proc/mtdby bodhi - Debian