Hi Bodhi, Will it be possible to port u-boot to dove platform?by wildhem - uBoot
Thank you so much Koen! Can you check what markings have probably mosfets marked in red? If you can read them, my green ones are MM6 C7, yours are the same? My board doesn't have all the red ones.by wildhem - Debian
karrelax Wrote: ------------------------------------------------------- > Hi there! > @wildhem but that means you have perfectly > functional screen? lucky guy! :) Mine can only > show 3/4 parts of the screen and only one > avaialable mode. Unfortunately, my screen does not show anything after starting debian. Try to use the wloader from the OS_Merlin_v8.6_B013_3020_T10D_by wildhem - Debian
I have another boot log from the launch of the pendrive prepared by dell usb imagging. Uncompressing Linux.................................................................................................................................................................................................. done, booting the kernel. Linux version 2.6.32-206-mimas (buildd@cushaw) (gcc version 4.4.3by wildhem - Debian
in logread on debian it displays the missing dtb entry Nov 2 15:29:53 debian user.warn kernel: [ 3.239507][ T1] dove-pinctrl f10d0200.pin-ctrl: falling back to hardcoded PMU resource Nov 2 15:29:53 debian user.warn kernel: [ 3.239847][ T1] dove-pinctrl f10d0200.pin-ctrl: : Missing pinctrl regs in DTB. Please update your firmware. Nov 2 15:29:53 debian user.info kernel: [ 3.by wildhem - Debian
Bodhi, what do we need to compile some other bootloader for this device?by wildhem - Debian
bodhi Wrote: ------------------------------------------------------- > So it looks like the LEDs controls were hardcoded > in this kernel. I found a script that runs at startup #!/bin/sh # File Name: /etc/addons.d/WYSE_PATCH/wyse-led-linux.sh # Function: Turn on the Green LED when starting Linux # NOTE: This script gets executed during boot process, # so use sh instead of bashby wildhem - Debian
karrelax Wrote: ------------------------------------------------------- > > I have a Wyse 3020 with thinOs Lite. > I have a Wyse 3010, it's a different device, you have to use different files. if you use binwalk -e par3.img you will get the file /_par1.img.extracted/0, this "0" file is just the image of the second partition you write with dd dd if=/_par3by wildhem - Debian
bodhi Wrote: ------------------------------------------------------- > > So now the question is what is ThinOS ? is it a > Linux derivative? if it is, then we can find the > GPIOs while in a shell. But it seems there is no > way to do that with ThinOS. while looking at ThinOS files I saw some mention of https://en.wikipedia.org/wiki/ECos but it's hardly here to lookby wildhem - Debian
bodhi Wrote: ------------------------------------------------------- > > That could mean the LED GPIOs are different. > However, do this to check > I don't know if it should look like this root@debian:/# ls -lR /sys/class/leds/ /sys/class/leds/: total 0 drwxr-xr-x 2 root root 0 Oct 31 09:28 . drwxr-xr-x 55 root root 0 Oct 31 09:28 .. lrwxrwxrwx 1 root root 0by wildhem - Debian
Xabby76 Wrote: ------------------------------------------------------- > Great wildhem.!!!!! > > Congratulations.!!!! > > Do you have also video output or not.? > Can you share with us all the process .? > > Thanks a lot.!! using the binwalk tool, I extracted the bootLoader.img file from the official software and got a file with a size of 704 KB, which I incby wildhem - Debian
I ran debian on my t10 :) I needed to create 2 partitions on my USB flash drive: 1. fat32 containing uImage, uInitrd and wloader.cfg kernel=./uImage initrd=./uInitrd param="root=LABEL=rootfs console=tty0 console=ttyS0,115200 " 2. ext4 rootfs filesystem (edited fstab) Unfortunately, the device cannot be turned off with the power button and the green LED is blinking all the timby wildhem - Debian
the commands mentioned earlier to boot from usb do not work for me, can there be any other options for wloader to initiate usb memory? I don't have any previous linux kernel in memory, just a wloader.by wildhem - Debian
I have a little success - I managed to run wloader on my wyse t10 by extracting the bootloader from the 20120203-0_U-1.041_T50_merlin file bootLoader.img and uploading it directly to the device's spi memory, still trying to boot from a usb memoryby wildhem - Debian
maybe it can help give our devices freedom? https://lore.kernel.org/all/20220102002841.gl4oienifm2nv4bs@pali/T/by wildhem - Debian
someone from here could provide spi memory dumps from the T50 model? edit: use this tool https://github.com/kakaroto/ene_kb3930_flasher try to do an EC memory dumpby wildhem - Debian
bodhi Wrote: ------------------------------------------------------- > These Wyse Thin Clients are bit different in u-boot part. But the Debian kernel > should be the same (each box boots with different DTS). I tried to compile a barebox bootloader once, but after loading it into memory, the device did not get up.by wildhem - Debian
The instruction given by Koen does not work for me on Wyse T10 - I can not enter the wloader settings or enable the root account. There is no ubuntu in this device, but some wyse system that fits in 8 megabyte spi memory and probably unpacks to ram on boot, hence no possibility to get to the ssh console. I also tried using the bootloader from the HP T5335z but the device won't boot. The nby wildhem - Debian
Could someone send me a spi memory dump from this terminal? I would like to try to boot my wyse t10 with a bootloader from this hp.by wildhem - Debian
I would still like to run debian on this terminal. Could someone send me a spi memory dump from a terminal that managed to run a different system than the official one?by wildhem - Debian
Editing boot commands in the spi dump file had no effect. I think if we compiled the uboot for this board and replaced it in the spi memory chip marked as EC, we would get a fully manageable device. Currently, for the T10 model it is not possible to boot into debian.by wildhem - Debian
Finally, I was able to run the terminal with the admin account, the password for which I found in the spi memory dump file. Then I updated the system to the latest version by replacing the initial 7501 KB of the dump file with DOVE_boot.i2d from the OS_Web_v8.6_206_3010_T10_ENG package However, I still can't start the serial console or ssh. The DEL and P keys at startup also have no effect.by wildhem - Debian
bodhi, > > So now it's booting normally again? > yes, it boots up the system but the console continues to show the same > I am not familiar with the restore procedure on > this box. I had bought a used box a long time go, > but have not tried to do any thing with it! all > the testing was done by Koen. I have two such devices and I would like to use thby wildhem - Debian
bodhi, yes, I only connected these. I left the terminal disconnected from the power supply and took out the battery and the the device starts up. It has the system version 8.1_027. Maybe there is some way to update the official system or restore factory settings and maybe then the terminal will start communicating?by wildhem - Debian
I bought CP2102 usb to uart and still same output (before i use ch340g) hp@debian:~$ sudo picocom --b 115200 --f n --p n --d 8 /dev/ttyUSB0 hasło użytkownika hp: picocom v3.1 port is : /dev/ttyUSB0 flowcontrol : none baudrate is : 115200 parity is : none databits are : 8 stopbits are : 1 escape is : C-a local echo is : no noinit is : no noreby wildhem - Debian
Im sure of the good gnd connection and further the serial console is not working. I also tried to connect the gnd to a different place on the board and then the same. Maybe there is some other installation method, such as read spi memory, edit and save with programmer?by wildhem - Debian
Thank you for your work and instructions on how to do it. However, I have a problem with the installation. I connected the adapter on the ch340g chip and the only thing I get from the console are the following characters: root@acab-VirtualBox:/media/acab/rootfs/boot# picocom -b 115200 /dev/ttyUSB0 picocom v3.1 port is : /dev/ttyUSB0 flowcontrol : none baudrate is : 115200by wildhem - Debian
does anyone still work on this device? I have this terminal but it probably has a blocked bios and I can't do anything with it. it has no built-in memory except spi memory. is it possible to revive it somehow? I have a programmer for these memories, but I don't know what to write there.by wildhem - Debian