Wonder if it is the standard ARM 20pin header. http://dy.fi/1n then there should be also possibility os SWD also. Could use plain arduino for that? -aby ahuovinen - uBoot
Has anyone found, or finds information about that J2 header that has serial pins. there are 8 pins and there is 4 that i know of. (depends on the side you look 1 tx 2 rx 3 ? 4 ? 5? 6? 7 gnd and 8 vcc. wonder if rest is connected to that spi flash chip ? or possibility of that unpopulated header which is rumored to be jtag header. ? -aby ahuovinen - uBoot
Used the classic version. Not Lite-one. Ordered a clip for my programmer so maybe i can manage without soldering iron. atleast as an option. -a-by ahuovinen - uBoot
well, should be supported by u-boot mainline as it has own configurationfile i used. -aby ahuovinen - uBoot
well, flashed the image and but stuck in a boot loop... U-Boot 2024.04-rc4 (Mar 13 2024 - 15:56:28 +0200) NS v2 SoC: Kirkwood 88F6281_A0 I2C: Could not initialize timer (err -11) resetting ... atleast its not totally dead. but maybe its desoldering time soon.by ahuovinen - uBoot
also tried with the newest version root@debian:~/nwsp2/u-boot# tools/kwboot -t -b u-boot.kwb -B 115200 /dev/ttyUSB0 kwboot version 2024.04-rc4 Detected kwbimage v0 with SPI boot signature Patching image boot signature to UART Sending boot message. Please reboot the target...| result is same.by ahuovinen - uBoot
Continuing thread at -> https://forum.doozan.com/read.php?3,137130 -a-by ahuovinen - Debian
root@debian:~/nwsp2/u-boot# kwboot -B 115200 /dev/ttyUSB0 -b u-boot.kwb -t kwboot version 2023.01 Patching image boot signature to UART Sending boot message. Please reboot the target.../ hangs on there. console is working (and not running atm) the program does not hang because that last mark looks changes.by ahuovinen - uBoot
Ok, FINALLY got a working connectorthingy Marvell>> reset _ ____ _ | | __ _ / ___(_) ___ | | / _` | | | |/ _ \ | |___ (_| | |___| | __/ |_____\__,_|\____|_|\___| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/by ahuovinen - Debian
i think the envs start at 0x7e000 -> i changed that and fw_printenv started working. Yes, there are thos few variables i personally added. though there are also some variables i cant change using u-boot console. -aby ahuovinen - Debian
0004A4B0 61 72 67 65 74 20 00 76 78 57 6F 72 6B 73 5F 62 6F 6F 74 61 72 67 73 00 62 6F 6F 74 61 72 67 73 5F 72 6F 6F 74 00 72 6F 6F 74 3D 2F 64 65 76 2F 6E 66 73 20 arget .vxWorks_bootargs.bootargs_root.root=/dev/nfs 0004A4E4 72 77 00 62 6F 6F 74 61 72 67 73 5F 65 6E 64 00 3A 3A 3A 6F 72 69 6F 6E 3A 65 74 68 30 3A 6E 6F 6E 65 00 3A 3A 3A 44 42 38 38 46 58 58 38 31 3Aby ahuovinen - Debian
bodhi Wrote: ------------------------------------------------------- > > do i need a reboot between the editing and > > fw_printenv? > > No need to. > > Check dmesg > > dmesg | grep -i2 spi > > [ 7.139740] spi-nor spi0.0: mx25l4005a (512 > Kbytes) > [ 7.145448] 1 cmdlinepart partitions found on > MTD device spi0.0 > [ 7.by ahuovinen - Debian
root@debian:~# nano /etc/fw_env.config root@debian:~# fw_printenv Cannot read environment, using default Cannot read default environment from file root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors #/dev/mtd0 0xc0000 0x20000 0x20000 /dev/mtd0 0x70000 0x10000 0x1000 do i neby ahuovinen - Debian
warri@debian:~$ dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 6.5.7-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #2 PREEMPT Wed Oct 18 21:14:11 PDT 2023 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005317f [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [by ahuovinen - Debian
bodhi Wrote: ------------------------------------------------------- > > If i compile mainline u-boot for networkspace > 2, > > how to test if it works without serial or > > flashing? > > I don't think there is any other way to test. > > The only remaining way to test without flashing is > to chain load u-boot image from u-boot prompt. > Hoby ahuovinen - Debian
> > How to test out that u-boot > > using netconsole? is it even possible? > > Not sure I understand this question. If i compile mainline u-boot for networkspace 2, how to test if it works without serial or flashing? -aby ahuovinen - Debian
Yes, was just experimenting. Too bad i cannot set bootargs as i would like to in environment variables because they are hard coded on the u-boot differently. How to test out that u-boot using netconsole? is it even possible?by ahuovinen - Debian
Marvell>> setenv rootfs setenv rootfs Marvell>> setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 earlyprintk=serial setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 earlyprintk=serial Marvell>> mw 0x800000 0 1 mw 0x800000 0 1 Marvell>> ext2load ide 0:1 0x800000 /boot/uImage ext2load ide 0:1 0x800000 /boot/uImage GPT: skipping lastby ahuovinen - Debian
I think, i flashed the current using that fvdw-sl-console which automated the process. It used tftp to transfer image to ram first.by ahuovinen - Debian
Yes but if you look my printenv output: rootfs=/dev/sdb7 . have to type setenv rootfs <enter> to remove it. after that booting from usb works. i really have to get u-boot flashed to standard version so i can install Linux of hdd. Now im waiting another USB-TTL converter which has jumper for voltage setting. The two i currently have should be automatic. But apparently they donby ahuovinen - Debian
Marvell>> coninfo coninfo List of available devices: serial 80000003 SIO stderr nc 80000003 SIO stdin stdout Marvell>> warri@debian:~$ cat /proc/cmdline console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serialby ahuovinen - Debian
gUe_▒▒▒▒▒▒VQ▒▒▒595-57▒-9/-#1▒!▒c5y!#!'5▒!#▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒YO▒▒▒▒҃▒CCCCCCCCCCCCCnZYCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC c letter comes when i press enterby ahuovinen - Debian
It is in bootargs propably hardcoded. , that environment variable messed the bootargs thingy. rootfs=/dev/sdb7 setting that to nothing it then works. Tried also with other serial cable, pl2303hxa based chip and the output is garbage again. https://web.archive.org/web/20150730041425/http://lacie.nas-central.org/wiki/Serial_port_(Network_space_2) used this image for pinout to conby ahuovinen - Debian
Noticed that too. but having some doubt if i cant test it before flashing. Should work and usually works. but... Need to wait few days to get another serial adapter. I thing that my current one is locked at 5v cause it has no selection jumper for the voltage. -aby ahuovinen - Debian
login as: root root@10.90.90.39's password: Linux debian 6.5.7-kirkwood-tld-1 #2 PREEMPT Wed Oct 18 21:14:11 PDT 2023 armv5tel The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extentby ahuovinen - Debian
root@debian:~/nwsp2# ssh 10.90.90.48 ssh: connect to host 10.90.90.48 port 22: Connection refusedby ahuovinen - Debian
root@debian:~/nwsp2# fdisk -l /dev/sdb Disk /dev/sdb: 57.72 GiB, 61973987328 bytes, 121042944 sectors Disk model: USB DISK Pro Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 730078F8-0D72-4B42-82E0-A10C55D25A63 Device Start End Sectors Size Tby ahuovinen - Debian
So i can get to u boot through netconsole using fvdw-sl console.. not through serial which shows lots of non ascii characters...by ahuovinen - Debian
bodhi Wrote: ------------------------------------------------------- > > so no difference. still loads of unreadable > > stuff.. the differnce is that when that fvdw > > firmware boots it shows up the boot messages > > May be that u-boot messed up the normal serial > console. But not likely, can you interrupt serial > console when it boots? If yes, > &by ahuovinen - Debian
Marvell>> md ff00003c md ff00003c ff00003c: 00000000 00000000 00000000 00000000 ................ ff00004c: 00000000 00000000 00000000 00000000 ................ ff00005c: 00000000 00000000 00000000 00000000 ................ ff00006c: 00000000 00000000 00000000 00000000 ................ ff00007c: 00000000 00000000 00000000 00000000 ................ ff00008c: 00000000 000by ahuovinen - Debian