Thank you for reply. Do they both run the same Linux kernel? (3.2) On the website it is stated that the B model runs 2.6.
I just looked at the power supply in the pictures. What voltages does it provide? I wonde if I could make the scope portable with some internal Li-Ion batteries.
do I still have to do the bw-hack (renaming the folder ?)
or does the scope simply thinks that it's an real DSO5202P with full bandwidth ?
And: will the DSO5202P firmware provide more features than the model 5072P one ?
At least I expect another boot logo, but will there be more ?
no, bootlogo is different thing:
Hello, i install all the things for LAN comunication, but scope don't work. Someone have any idea?
Hello, i install all the things for LAN comunication, but scope don't work. Someone have any idea?
even two
add two 22pf caps t the crystal (i assume you soldered 25MHz crystal?) and remove that 0R resistor.
With this resistor one don't need crystal, in the theory, when FPGA is producing clock (which must not be the case in the current hardware / firmware). Easier, and always working, is when one use crystal, but then that resistor need to be removed and of course two caps need to be added to crystal as well.
mmm not, still doesn't work =( and microSD the same XD
you might as well check this
https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg467313/#msg467313
before you change anything, make a back of the /i2c.log file. Inside that file you will find options you your models, you will have to creat a new EEPROM licensing (write HDVersion.set button) , use all values from your current i2c.log but change the "lan version" from 0 to 1.
yes, when you plug a cable.
Nothing to do, i chek again the components and all has good soldering. I think its a defective chip or i burned them
dm9000 Ethernet Driver, V1.31
dm9000 dm9000: read wrong id 0xffffffff
dm9000 dm9000: wrong id: 0xffffffff
dm9000 dm9000: not found (-19).
root@hantek:~# rmmod dm9000
root@hantek:~# modprobe dm9000
dm9000 Ethernet Driver, V1.31
dm9000 dm9000: eth%d: Invalid ethernet MAC address. Please set using ifconfig
eth0: dm9000a at c49e4300,c49e6308 IRQ 48 MAC: c6:fe:7c:c9:e1:c4 (random)
Nothing to do, i chek again the components and all has good soldering. I think its a defective chip or i burned them
on my 5072p I need to unload/reload the LAN driver for it to work:Code: [Select]dm9000 Ethernet Driver, V1.31
dm9000 dm9000: read wrong id 0xffffffff
dm9000 dm9000: wrong id: 0xffffffff
dm9000 dm9000: not found (-19).
root@hantek:~# rmmod dm9000
root@hantek:~# modprobe dm9000
dm9000 Ethernet Driver, V1.31
dm9000 dm9000: eth%d: Invalid ethernet MAC address. Please set using ifconfig
eth0: dm9000a at c49e4300,c49e6308 IRQ 48 MAC: c6:fe:7c:c9:e1:c4 (random)
The driver doesn't seem to be getting loaded at all. Try running insmod /dso/drivers/dm9000.ko and see if anything shows up in the log
[root@Hantek ~]#
[root@Hantek ~]# insmod /dso/drivers/dm9000.ko
dm9000 Ethernet Driver, V1.31
dm9000 dm9000: eth%d: Invalid ethernet MAC address. Please set using ifconfig
eth0: dm9000a at c4976300,c4978308 IRQ 48 MAC: ba:97:89:4e:f1:22 (random)
[root@Hantek ~]# ifconfig -a
eth0 Link encap:Ethernet HWaddr BA:97:89:4E:F1:22
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:48 Base address:0x6300
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Looks good!
You need to bring up the interface (using ifconfig + IP/subnet etc.) before you see any activity LEDs. I think you have to do all this manually, as far as I know the standard Hantek software doesn't support any kind of network stuff so it's only useful for custom work
OK Guys, I think I've solved it.
I was reading through page 158 when a came across a reply from Rosaharn to Pezibaer about 'Probe problems', and I thought 'I haven't tried the other probe'.
I'm one happy bunny, all is now back to normal (See attached screen shot).
So it was just a 'bad' probe.
Well it may help someone with a similar problem, so I will leave the post in place.
Thanks guys and especially tinhead for a fantastic thread, if it were up to me I'd nominate him for the 'Nobel Prize'.
oneeye