+- Blitzortung.org Forum (https://forum.blitzortung.org/mybb)
+-- Forum: Public Forums (https://forum.blitzortung.org/mybb/forumdisplay.php?fid=29)
+--- Forum: Hardware, Software, Lightning Physics (https://forum.blitzortung.org/mybb/forumdisplay.php?fid=30)
+--- Thread: Hardware Problems (/showthread.php?tid=756)
Pages:
1
2
Hardware Problems - Christian.Weiss - 2014-08-16
Hello Forum,
we have Problems to get our Controller running.
After Power On the Buzzer beep´s a while.
Here are several Log after Power On.
Can somebody help us?
If you will call me try +49 170 8339732
vy 73 de DG3FCP, Christian
2013-01-01 00:00:40 0 | [Hard fault handler - all numbers in hex]
2013-01-01 00:00:40 0 | R0 = 20000140
2013-01-01 00:00:40 0 | R1 = 802b109
2013-01-01 00:00:40 0 | R2 = 802b11a
2013-01-01 00:00:40 0 | R3 = 21000000
2013-01-01 00:00:40 0 | R12 = 40020400
2013-01-01 00:00:40 0 | LR [R14] = 1000 subroutine call return address
2013-01-01 00:00:40 0 | PC [R15] = 20011fe4 program counter
2013-01-01 00:00:40 0 | PSR = 801f6e5
2013-01-01 00:00:40 0 | BFAR = e000ed38
2013-01-01 00:00:40 0 | CFSR = 40000
2013-01-01 00:00:40 0 | HFSR = 40000000
2013-01-01 00:00:40 0 | DFSR = 0
2013-01-01 00:00:40 0 | AFSR = 0
2013-01-01 00:00:40 0 | SCB_SHCSR = 0
2013-01-01 00:00:01 0 | [Hard fault handler - all numbers in hex]
2013-01-01 00:00:01 0 | R0 = 88000000
2013-01-01 00:00:01 0 | R1 = 88000000
2013-01-01 00:00:01 0 | R2 = 0
2013-01-01 00:00:01 0 | R3 = 44
2013-01-01 00:00:01 0 | R12 = 0
2013-01-01 00:00:01 0 | LR [R14] = 8025d95 subroutine call return address
2013-01-01 00:00:01 0 | PC [R15] = 8025c4e program counter
2013-01-01 00:00:01 0 | PSR = 81000000
2013-01-01 00:00:01 0 | BFAR = e000ed38
2013-01-01 00:00:01 0 | CFSR = 10000
2013-01-01 00:00:01 0 | HFSR = 40000000
2013-01-01 00:00:01 0 | DFSR = 0
2013-01-01 00:00:01 0 | AFSR = 0
2013-01-01 00:00:01 0 | SCB_SHCSR = 0
2013-01-01 00:00:01 0 | [Hard fault handler - all numbers in hex]
2013-01-01 00:00:01 0 | R0 = 88000000
2013-01-01 00:00:01 0 | R1 = 80e8
2013-01-01 00:00:01 0 | R2 = 58a0
2013-01-01 00:00:01 0 | R3 = 589f
2013-01-01 00:00:01 0 | R12 = 0
2013-01-01 00:00:01 0 | LR [R14] = ffffffe9 subroutine call return address
2013-01-01 00:00:01 0 | PC [R15] = ffe9dfb6 program counter
2013-01-01 00:00:01 0 | PSR = 20000045
2013-01-01 00:00:01 0 | BFAR = e000ed38
2013-01-01 00:00:01 0 | CFSR = 1
2013-01-01 00:00:01 0 | HFSR = 40000000
2013-01-01 00:00:01 0 | DFSR = 0
2013-01-01 00:00:01 0 | AFSR = 0
2013-01-01 00:00:01 0 | SCB_SHCSR = 0
RE: Hardware Problems - Tobi - 2014-08-16
Tell me the firmware version, what you see on the LCD and which of the four user LEDs are on when the problem occurs. Some more lines before the log might help too.
RE: Hardware Problems - Christian.Weiss - 2014-08-16
(2014-08-16, 14:52)Tobi Wrote: Tell me the firmware version, what you see on the LCD and which of the four user LEDs are on when the problem occurs. Some more lines before the log might help too.
Hello Tobi,
thanks for fast reply?
On The LCD are the same informations as in the LOG.
Tree LED´s are on : red, yelow, green
Blue is off.
Here the LOG.
Can i call you?
2000-01-01 00:00:00 0 | ================ Blitzortung STM32F4 Controller Board ================
2000-01-01 00:00:00 0 | Firmware Rev. 7.3b1 / Aug 9 2014 19:28:42 (Git 7.3b1-0-g8aa7462)
2000-01-01 00:00:00 0 | Hardware Rev. 10.4 (Id 2)
2000-01-01 00:00:00 0 | Reset condition: BOR=1 PIN=1 POR=1 SOFT=0 IWD=0 WWD=0 LPW=0
2000-01-01 00:00:00 0 | HCLK: 168MHz
2000-01-01 00:00:00 0 | PCLK1 (APB1): 42MHz
2000-01-01 00:00:00 0 | PCLK2 (APB2): 84MHz
2000-01-01 00:00:00 0 | SYSCLK: 168MHz
2000-01-01 00:00:00 0 | ======================================================================
2000-01-01 00:00:00 0 |
2000-01-01 00:00:00 0 |
2000-01-01 00:00:00 0 | === ADC Defaults ===
2000-01-01 00:00:00 0 | Resolution: 12bits
2000-01-01 00:00:00 0 | Divider: 2
2000-01-01 00:00:00 0 | Sample Cycles 1: 56
2000-01-01 00:00:00 0 | Sample Cycles 2: 28
2000-01-01 00:00:00 0 |
2000-01-01 00:00:00 0 |
2000-01-01 00:00:00 0 | === ADC Configuration ===
2000-01-01 00:00:00 0 | Resolution: 12bits
2013-01-01 00:00:00 0 | START: Loaded TOA-Lightning-ALERT settings.
2013-01-01 00:00:00 0 | START: Loaded ACTION settings.
2013-01-01 00:00:00 0 | START: Initialized WEBSERVER on port 80.
2013-01-01 00:00:00 0 |
2013-01-01 00:00:00 0 | === Init HTTP Remote CONFIG ===
2013-01-01 00:00:00 0 | REMOTE-CONFIG: Static URL1 'http://tracker.blitzortung.org/control/station.php'
2013-01-01 00:00:00 0 | REMOTE-CONFIG: Static URL2 'http://www.lightningmaps.org/control/station.php'
2013-01-01 00:00:00 0 | REMOTE-CONFIG: Checking every 300s
2013-01-01 00:00:00 0 |
2013-01-01 00:00:00 0 | === Tracker (TM by Egon) ===
2013-01-01 00:00:00 0 | TRACKER: Init Settings...
2013-01-01 00:00:00 0 | Tracker: Using buffer of 0bytes (0x10000000 - 0xFFFFFFF) for 35 signals
2013-01-01 00:00:00 0 | Tracker: Using buffer 35 for noise level calculation
2013-01-01 00:00:00 0 | TRACKER: Call Amplifier Setup...
2013-01-01 00:00:00 0 |
2013-01-01 00:00:00 0 |
2013-01-01 00:00:00 0 |
2013-01-01 00:00:00 0 | ===========================================================================
2013-01-01 00:00:00 0 | [Hard fault handler - all numbers in hex]
2013-01-01 00:00:00 0 | R0 = 80000000
2013-01-01 00:00:00 0 | R1 = 80e8
2013-01-01 00:00:00 0 | R2 = 3fd8
2013-01-01 00:00:00 0 | R3 = 3fd7
2013-01-01 00:00:00 0 | R12 = 0
2013-01-01 00:00:00 0 | LR [R14] = ffffffe9 subroutine call return address
2013-01-01 00:00:00 0 | PC [R15] = ff68df90 program counter
2013-01-01 00:00:00 0 | PSR = 2000003d
2013-01-01 00:00:00 0 | BFAR = e000ed38
2013-01-01 00:00:00 0 | CFSR = 1
2013-01-01 00:00:00 0 | HFSR = 40000000
2013-01-01 00:00:00 0 | DFSR = 0
2013-01-01 00:00:00 0 | AFSR = 0
2013-01-01 00:00:00 0 | SCB_SHCSR = 0
2013-01-01 00:00:00 0 | ===========================================================================
RE: Hardware Problems - Tobi - 2014-08-16
(2014-08-16, 15:04)Christian.Weiss Wrote: Here the LOG.It shows a brown out reset. Please check the supply voltage. It should be around 5V
(2014-08-16, 15:04)Christian.Weiss Wrote: Can i call you?No, sorry. We don't have time for telephone support.
RE: Hardware Problems - Christian.Weiss - 2014-08-16
(2014-08-16, 15:21)Tobi Wrote:(2014-08-16, 15:04)Christian.Weiss Wrote: Here the LOG.It shows a brown out reset. Please check the supply voltage. It should be around 5V
(2014-08-16, 15:04)Christian.Weiss Wrote: Can i call you?No, sorry. We don't have time for telephone support.
No brown out, the voltage on the controller Board is 4,9 Volt.
The whole current is 280 mA and the USB Power supply has 750 mA.
Another idea?
RE: Hardware Problems - Benedict.Smith - 2014-08-16
(2014-08-16, 16:04)Christian.Weiss Wrote:(2014-08-16, 15:21)Tobi Wrote:(2014-08-16, 15:04)Christian.Weiss Wrote: Here the LOG.It shows a brown out reset. Please check the supply voltage. It should be around 5V
(2014-08-16, 15:04)Christian.Weiss Wrote: Can i call you?No, sorry. We don't have time for telephone support.
No brown out, the voltage on the controller Board is 4,9 Volt.
The whole current is 280 mA and the USB Power supply has 750 mA.
Another idea?
Try a different USB cable, some of them have thinner gauge wires than they claim and can cause power problems (a common cause of problems with RaspberryPi boards).
If this does not help then try a different USB power supply, also check the quality of the mains supply, if the socket is old then I have seen problems with tarnished and even corroded contacts and loose screw terminals inside! also the same with extension cables.
I am currently using a 2.1A Apple USB adapter from an iPad and have no problems with power.
If none of the above help then you may need to consider either a UPS or fitting a large capacitor across the 5V rail to smooth any power dips.
Ben.
RE: Hardware Problems - Christian.Weiss - 2014-08-16
(2014-08-16, 16:21)Benedict.Smith Wrote:(2014-08-16, 16:04)Christian.Weiss Wrote:(2014-08-16, 15:21)Tobi Wrote:(2014-08-16, 15:04)Christian.Weiss Wrote: Here the LOG.It shows a brown out reset. Please check the supply voltage. It should be around 5V
(2014-08-16, 15:04)Christian.Weiss Wrote: Can i call you?No, sorry. We don't have time for telephone support.
No brown out, the voltage on the controller Board is 4,9 Volt.
The whole current is 280 mA and the USB Power supply has 750 mA.
Another idea?
Try a different USB cable, some of them have thinner gauge wires than they claim and can cause power problems (a common cause of problems with RaspberryPi boards).
If this does not help then try a different USB power supply, also check the quality of the mains supply, if the socket is old then I have seen problems with tarnished and even corroded contacts and loose screw terminals inside! also the same with extension cables.
I am currently using a 2.1A Apple USB adapter from an iPad and have no problems with power.
If none of the above help then you may need to consider either a UPS or fitting a large capacitor across the 5V rail to smooth any power dips.
Ben.
We have connected the Board also to an Labor Power Supply from Hameg.
I can realy exclude problems with the Power Supply!
It looks like the Watch Dog on the STM Board is the Problem.
Here you can see a short Video
http://www.youtube.com/watch?v=IZiuj7jylc0
RE: Hardware Problems - Tobi - 2014-08-16
I'm not sure, but this looks like a general problem with the processor. The hard fault error occur at unpredictable program counter values. Things you can try:
- Do a reset (black button) while holding the blue button for some seconds. This will erase the area in the flash memory where the settings are stored.
- Reflash the same firmware or a previous firmware
- Check again the soldering and placement of the parts
- Remove the Ethernet chip (ENC28J60) and/or the LCD and/or the amplifier
- Try a different discovery board
RE: Hardware Problems - Christian.Weiss - 2014-08-16
(2014-08-16, 17:05)Tobi Wrote: I'm not sure, but this looks like a general problem with the processor. The hard fault error occur at unpredictable program counter values. Things you can try:
- Do a reset (black button) while holding the blue button for some seconds. This will erase the area in the flash memory where the settings are stored.
- Reflash the same firmware or a previous firmware
- Check again the soldering and placement of the parts
- Remove the Ethernet chip (ENC28J60) and/or the LCD and/or the amplifier
- Try a different discovery board
We have the Controller Board running after trying several Firmware Versions.
V7.0b4 seems to be working but only as long as we connect the amplifier or the GPS receiver has locked.
We can connect the WebIF also as long there is nothing conected or the there is no valid GPS Signal.
Do we have to make settings in the WebIF bevor we can connect the amplifier?
RE: Hardware Problems - Tobi - 2014-08-17
(2014-08-16, 20:02)Christian.Weiss Wrote: Do we have to make settings in the WebIF bevor we can connect the amplifier?No, of course not. The system shouldn't crash at all, whatever you do.