Blank lighted Screen after Bootloader Displays
GeekSkunkWorks
a blank lighted screen that stay illuminated, with nothing on it after
the bootloader text displays. I purchased the kit immediately when it
became available from SeeedStudio, but just now building it. Board PN
is 109-06200-00A. My Kit instructions were several revisions old, so I
have been using the current ones linked from this and the manufactures
site.
I have used the trouble shooting PDF and can report the following:
-check multiple power supplies, get have same result
-All voltage check points match up with Figure one.
-Continuity across parts checked,including display, no issues found.
(MCU to LCD)
-C17 Voltage looked good
-Oscillator voltage checkpoint looks good
-It "Looks" like other units I have seen posted, no missing jumpers or
other then BOM replacement parts. (Less C1, described below)
Know problems/concerns I have (that I am curious if could be the
cause):
-R1 Missing (I have one on order, plan to replace when it comes in)
-The two pins under the heat sink (in recent instructions said they do
not need to be soldered, just for support). I have them soldered.
-I don't have the indicator LED installed.
-The part I have assumed to be C1 looks different then other orange
ones I see pictured. It is green, with the following label: Y(in a
circle)2A104J (from some search online it looked to be the same as
the BOM listed 0.1uF, but 100V vs 400V
I should also point out I have read the group discussions quite a bit
and have been able to fix many issues leading up to my current state.
(Thank you)
-So I can report D1/D7 have been installed correctly. (See looking at
recent instructions
-The variable voltages as the following locations have been measured:
(Variable per the powersupply according to the troubleshooting PDF)
TP6: -6.1
TP7: 7.6
D7: 0.075 / -6.1
R17: 7.2
Q2 test point: 4.6
-My power supply that I have decided to use has a 9V output DC, 300mA
My BOM says it shipped with firmware -060. I am curious if I should
just wait for R1 to be installed before further troubleshooting, or I
should attempt to 'fashion-together' a serial level converter to
monitor the MCU startup, or update the firmware. (I already have a
Bus-Pirate ~thinking of trying that out to monitor the startup or
update firmware.) This level of working with electronics would be
treading new ground for me.
Thank you for any advise. It has been a fun and challenging kit to
build, looking forward to get it working.
Jay
http://www.geekskunkworks.com/
JYE Tek
--
You received this message because you are subscribed to the Google Groups "JYE Tech Oscilloscopes" group.
To post to this group, send email to jye-tech-os...@googlegroups.com.
To unsubscribe from this group, send email to jye-tech-oscillos...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jye-tech-oscilloscopes?hl=en.
GeekSkunkWorks
alternate device called a Bus Pirate. It is USB but
is able to work in a Transparent UART bridge. I watched it started at
both 9600 and 38400. (Saw the bootloader and COM indicators, so I was
sure my connections and voltage should be correct. When running the
AVRUBD I keep getting Connect failed. In the output below, I forced
the unit to restart while trying to connect so I could show that I was
communicating with the device. I tripled checked all AVRUBD
settings.
Wondering if you think I may have some hardware/bootloader issue, or
can you recomend any other programs that communicate with the
bootloader perhaps? I also may try to make the Serial Level converter
cable if you think that could help.
Again, I am missing R1 still. (If you also think that could impact
things.)
> Start download
$ Send reset command: [7E ]
> Start connect
$ <1> Send connect key: 64
$ <2> Send connect key: 64
$ <3> Send connect key: 64
$ <4> Send connect key: 64
$ <5> Send connect key: 64
$ <6> Send connect key: 64
$ <7> Send connect key: 64
$ <8> Send connect key: 64
$ <9> Send connect key: 64
$ <10> Send connect key: 64
: 0A 0D BD F1 D4 BD B5 E7 D7 ..½ñÔ½µç×
: D3 D6 C6 D7 F7 0D 0A 0A 0D 4A 59 45 ÓÖÆ×÷....JYE
: 20 54 65 63 68 0D 0A 0A 0D 57 57 57 Tech....WWW
: 2E 4A 59 45 54 45 43 48 2E 43 4F 4D .JYETECH.COM
: 0D 0A 0A 0D 42 4C 3A 20 31 31 33 2D ....BL: 113-
: 30 36 32 30 32 2D 30 32 30 0D 0A 0A 06202-020...
$ <11> Send connect key: 64
: 0D 0D 0A B5 C8 B4 FD BD D3 CA D5 C3 ...µÈ´ý½ÓÊÕÃ
: DC C2 EB 2E 0D 0A ÜÂë...
$ <12> Send connect key: 64
$ <13> Send connect key: 64
$ <14> Send connect key: 64
$ <15> Send connect key: 64
$ <16> Send connect key: 64
$ <17> Send connect key: 64
$ <18> Send connect key: 64
$ <19> Send connect key: 64
$ <20> Send connect key: 64
X Connect fail
On Apr 1, 7:40 pm, JYE Tek <jye...@gmail.com> wrote:
> The main firmware could be corrupted. Please try reflash the codes. We
> suspect that with bootloader the flash has much more chance to get
> corrupted.
>
> 2010/4/2 GeekSkunkWorks <jaybou...@gmail.com>
> > jye-tech-oscillos...@googlegroups.com<jye-tech-oscilloscopes%2Bunsu...@googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/jye-tech-oscilloscopes?hl=en.- Hide quoted text -
>
> - Show quoted text -
B Burns
can be found on the JYETech site. You can also download the
recommended firmware update program from there.
> > >http://groups.google.com/group/jye-tech-oscilloscopes?hl=en.-Hide quoted text -
GeekSkunkWorks
the AVRUBD is very sensitive to this.)
I don't have a AVR programmer, or Serial Level Converter cable, was
trying to follow the procedure based on the Serial Level Converter
directions but substitute it for the Bus Pirate Device (
http://dangerousprototypes.com/bus-pirate-manual/ ) . Perhaps that
device has it's own UART problems that are making this more error
prone.
My substitution procedure was basically to first connect to the Bus-
Pirate, set it up for the same 8/N/1 9600 (UART Bridge), then
disconnect from it, then I was able to connect with the AVRUBD. (But
the uploading fails as seen above.)
Looks like my efforts to avoid building/buying another cable are going
to have to give in here. Can these be purchased anywhere?
I'm looking at the diagram for the Converter and abit confused. I'm
wondering how I find equivalent Q1A/Q1B parts. Also Pin 4 (to VCC)
and PIN 3 to Ground, these don't seem to go back to the DB-9 part of
the cable, is this correct? They go to a external power supply? Am I
understanding it correctly that the circuit is primarily to condition
the TX/RX path. (Since I don't see pin 3&4 on the 4 pin connector
going bac k to the DB-9 at a specific pin.
Thanks for any help, if someone has a simpler version, or picture of a
homebrew type done already it may help me.
> > > >http://groups.google.com/group/jye-tech-oscilloscopes?hl=en.-Hidequoted text -
>
> > > - Show quoted text -- Hide quoted text -
GeekSkunkWorks
I did notice something very interesting. The Bootloader contrast is
perfect, I can read that that is taking place.
After I get a blank (lit) screen, if I quickly de-power/powerup, I can
briefly see what looks to be the proper grid screen.
So perhaps my issue contrast, but after the bootloader. Does this seem
possible? Do any of the controls have the ability to change the
contrast while it is running? The Contrast checkout in the
Troubleshooting procedure looked OK when I re-reviewed it.
On Apr 2, 10:31 am, GeekSkunkWorks <jaybou...@gmail.com> wrote:
> I have. The only deviation being the interface method. (But perhaps
> the AVRUBD is very sensitive to this.)
>
> I don't have a AVR programmer, or Serial Level Converter cable, was
> trying to follow the procedure based on the Serial Level Converter
> directions but substitute it for the Bus Pirate Device (http://dangerousprototypes.com/bus-pirate-manual/) . Perhaps that
> > > > >http://groups.google.com/group/jye-tech-oscilloscopes?hl=en.-Hidequotedtext -
B Burns
just receiving.
As for the serial level converter, have you tried to source the parts
through Mouser.com? The grounds from both the serial port and circuit
are connected together. VCC(5v) from the circuit powers the
converter.
I've not used the JYEtech level converter. Personally, I've had good
results with MAX232 based serial level converters. There is a
schematic for one in the files section. They both should work.
R1 shouldn't have any effect on the function of the LCD. It is still
most likely that you have corrupted main firmware.
> > > > > >http://groups.google.com/group/jye-tech-oscilloscopes?hl=en.-Hidequot...-
GeekSkunkWorks
Thank you!
steveastrouk
smaller !
Steve
GeekSkunkWorks
up. I will preface this with the fact that it looks like my solution
was rather uncommon. As noted above I used the full troubleshooting
guide, and checked other discusions along the way. So If anyone has
similar issues I suggest they do the same. It helped me find and fix a
number of minor issues before this one.
(The below are from emails between Jye Tech and myself. They were nice
enough to contact me personally about my problem above.)
jye Tech:
If you see grid at de-powering then that means the main firmware got
run at least partially. Can you please monitor voltage at LCD pin 3 to
see if it changes as MCU from bootloader running into main firmware?
Me:
I monitored Pin 3 from power-on through the bootloader. and after. It
stays consistently at -4.3V (Never changes.)
jye Tech:
It could be the LCD internal problem although I can not explain why.
------
I have since removed the previous LCD, and put in a replacement. All
seems to be working well now.
Thanks Jye Tech!
> > > > > - Show quoted text -- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
You received this message because you are subscribed to the Google Groups "JYE Tech Oscilloscopes" group.
To post to this group, send email to jye-tech-os...@googlegroups.com.