The trouble I am having is that the screen brightness has dimmed so much that it is hard to see the image, I would estimate the brightness is 1/3 of what it was.
I have reset the device several times, downloaded several different eye programs, several Arduino sketches, a several Circuit Python programs, and nothing brings the screen back to it's original brightness.
The lack of brightness is the same if the HalloWing is powered by USB or a 3.7v LIPoly batter.
Thanks, in advance, for your help
Tim
HalloWing Screen Very dim
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
- geogriff
- Posts: 41
- Joined: Tue Dec 10, 2013 10:40 am
HalloWing Screen Very dim
- Attachments
-
- HalloWing Back-2.jpg (290.51 KiB) Viewed 333 times
-
- HalloWing Back-1.jpg (280.1 KiB) Viewed 333 times
-
- HalloWing Front.jpg (286.47 KiB) Viewed 333 times
- adafruit2
- Posts: 22200
- Joined: Fri Mar 11, 2005 7:36 pm
Re: HalloWing Screen Very dim
have you had it on for a very long time?
- geogriff
- Posts: 41
- Joined: Tue Dec 10, 2013 10:40 am
Re: HalloWing Screen Very dim
Not long, I just received it in my latest AdaBox, probably has seen 8-10 hours of use.
It had been working fine. I was using it for a prop on Halloween and after about an hour of being on the screen was very dim.
tim
It had been working fine. I was using it for a prop on Halloween and after about an hour of being on the screen was very dim.
tim
- adafruit_support_carter
- Posts: 29483
- Joined: Tue Nov 29, 2016 2:45 pm
Re: HalloWing Screen Very dim
Maybe something happened here? What was the prop and can you correlate when it went dim to any event?I was using it for a prop on Halloween and after about an hour of being on the screen was very dim.
OK, try these test sketches I've cooked up in some other threads. This one simply blinks the backlight - full on / full off:downloaded several different eye programs, several Arduino sketches, a several Circuit Python programs,
viewtopic.php?f=19&t=143475#p709302
And this is the basic GFX test sketch with pin settings for the Hallowing:
viewtopic.php?f=19&t=143475#p709452
Try those and report back what happens.
- geogriff
- Posts: 41
- Joined: Tue Dec 10, 2013 10:40 am
Re: HalloWing Screen Very dim
Thanks Carter,
I will try test that tonight.
tim
I will try test that tonight.
tim
- adafruit2
- Posts: 22200
- Joined: Fri Mar 11, 2005 7:36 pm
Re: HalloWing Screen Very dim
also some of our sketches reduce the backlight - having it full-on can draw a lot of power and isn't super-great for the LED. half brightness is what it should be at, some of our sketches use half-brightness!
- geogriff
- Posts: 41
- Joined: Tue Dec 10, 2013 10:40 am
Re: HalloWing Screen Very dim
Hello again,
I tried the files you indicated in your response. But, neither worked. The programs appear to download properly (see screen shots), the LED13 blinks while downloading, and then noting. I also tried a basic blink LED and that also produces no visible results on the board.
I have double checked the cables and was able to upload MakeCode, Arduino, and Python to my Playground express.
I was also able to upload Arduino programs and CPython programs to my Huzzah. So I am sure the USB cables and programs are functioning properly . I also double checked that the Arduino IDE 1.8.7 was up to date , and the Library and Board files were up to date.
I can get the UF2 eyes programs to work, but, I need to turn the HalloWing OFF then back ON be for the display will show them. The display is still very dim.
It seems, there might be a physical problem with the board.
What would you recommend I do next
thanks
tim
Content of INFO_UF2.txt file on HaloWing:
"UF2 Bootloader v2.0.0-adafruit.0-21-g887cc30 SFHWRO
Model: Hallowing M0
Board-ID: SAMD21G18A-Feather-v0"
I tried the files you indicated in your response. But, neither worked. The programs appear to download properly (see screen shots), the LED13 blinks while downloading, and then noting. I also tried a basic blink LED and that also produces no visible results on the board.
I have double checked the cables and was able to upload MakeCode, Arduino, and Python to my Playground express.
I was also able to upload Arduino programs and CPython programs to my Huzzah. So I am sure the USB cables and programs are functioning properly . I also double checked that the Arduino IDE 1.8.7 was up to date , and the Library and Board files were up to date.
I can get the UF2 eyes programs to work, but, I need to turn the HalloWing OFF then back ON be for the display will show them. The display is still very dim.
It seems, there might be a physical problem with the board.
What would you recommend I do next
thanks
tim
Content of INFO_UF2.txt file on HaloWing:
"UF2 Bootloader v2.0.0-adafruit.0-21-g887cc30 SFHWRO
Model: Hallowing M0
Board-ID: SAMD21G18A-Feather-v0"
- Attachments
-
- viewtopic 709452.pdf
- (341.83 KiB) Downloaded 14 times
-
- viewtopic 709302.pdf
- (276.31 KiB) Downloaded 12 times
-
- Blink Example.pdf
- (321.74 KiB) Downloaded 11 times
- adafruit_support_carter
- Posts: 29483
- Joined: Tue Nov 29, 2016 2:45 pm
Re: HalloWing Screen Very dim
Hmmm. Sounds like we're going backwards if the basic blink sketch isn't even working. Just to make sure you're checking the correct LED, when you run blink on pin 13, it should be blinking this LED:The programs appear to download properly (see screen shots), the LED13 blinks while downloading, and then noting. I also tried a basic blink LED and that also produces no visible results on the board.
- geogriff
- Posts: 41
- Joined: Tue Dec 10, 2013 10:40 am
Re: HalloWing Screen Very dim
Hi,
Yes, the LED on Pin 13 ( the one you circled in red) does not turn on when I upload the blink sketch. It does, however rapidly flash when the any program is downloaded to the M0.
I rechecked the HalloWing tonight.
Other observations:
1. The LED on pin 13 only blinks when a program file is uploaded to the board.
2. When in HALLOWBOOT mode if I drag the (adafruit-circuitpython-feather_m0_express-3.1.1.uf2) file onto HALLOWBOOT the HALLOWBOOT will disappear but the HALLOWPY
will NOT appear.
3. When in HALLOWBOOT mode if I drag the (Spooky_Eye_Human.UF2) file onto the HALLOWBOOT the eyes will only displayed after I turn the M0 off then back on.
4. When using the Maker.MakeCode.com site I can not get the D13 LED to blink (see Blink_D13_On_Maker-makecode-com.pdf)
5. When using the Maker.MakeCode.com site I can get the A01 LED to blink (see Blink_A1_On_Maker-makecode-com.pdf) using and external 220h resister and an LED connected
like this GND-----220h-----LED-----PinA1
thanks
tim
Yes, the LED on Pin 13 ( the one you circled in red) does not turn on when I upload the blink sketch. It does, however rapidly flash when the any program is downloaded to the M0.
I rechecked the HalloWing tonight.
Other observations:
1. The LED on pin 13 only blinks when a program file is uploaded to the board.
2. When in HALLOWBOOT mode if I drag the (adafruit-circuitpython-feather_m0_express-3.1.1.uf2) file onto HALLOWBOOT the HALLOWBOOT will disappear but the HALLOWPY
will NOT appear.
3. When in HALLOWBOOT mode if I drag the (Spooky_Eye_Human.UF2) file onto the HALLOWBOOT the eyes will only displayed after I turn the M0 off then back on.
4. When using the Maker.MakeCode.com site I can not get the D13 LED to blink (see Blink_D13_On_Maker-makecode-com.pdf)
5. When using the Maker.MakeCode.com site I can get the A01 LED to blink (see Blink_A1_On_Maker-makecode-com.pdf) using and external 220h resister and an LED connected
like this GND-----220h-----LED-----PinA1
thanks
tim
- Attachments
-
- Blink_A1_On_Maker-makecode-com.pdf
- (405.7 KiB) Downloaded 10 times
-
- Blink_D13_On_Maker-makecode-com.pdf
- (410.33 KiB) Downloaded 11 times
- adafruit2
- Posts: 22200
- Joined: Fri Mar 11, 2005 7:36 pm
Re: HalloWing Screen Very dim
dont use maker.makecode with the hallowing, it isnt supported
- adafruit_support_carter
- Posts: 29483
- Joined: Tue Nov 29, 2016 2:45 pm
Re: HalloWing Screen Very dim
1. OK - that's normal.
2. Looks like you are using the wrong firmware. For the Hallowing, use the one with "adafruit-circuitpython-hallowing_m0_express" in the name: https://github.com/adafruit/circuitpyth ... ses/latest. Also, the folder should show up as CIRCUITPY after you've flashed the firmware.
3. Not sure why it's requiring a power cycle, but at least it's running. Do you get that same behavior with the other spooky eye UF2's?
4. and 5. What was said above
2. Looks like you are using the wrong firmware. For the Hallowing, use the one with "adafruit-circuitpython-hallowing_m0_express" in the name: https://github.com/adafruit/circuitpyth ... ses/latest. Also, the folder should show up as CIRCUITPY after you've flashed the firmware.
3. Not sure why it's requiring a power cycle, but at least it's running. Do you get that same behavior with the other spooky eye UF2's?
4. and 5. What was said above
- geogriff
- Posts: 41
- Joined: Tue Dec 10, 2013 10:40 am
Re: HalloWing Screen Very dim
OK,
1. When downloading the CORRECT file (my bad) onto the HalloWing the HALLOWBOOT device shows up (using an iMac OS10.12.6)
2. I can, using the MU editor get things to work on the HallowWing like sound, neopixel strip, neopixel on the board.
3. I can NOT get any program to download using Arduino IDE. I have double checked that all libraries are up to date.
4. I can download any of the eye—.UF2 files and they will display, but are very dim.
5. NEW problem to report. .
To do all this testing I have only been using the HalloWing tethered to the iMac. After much testing today I disconnected it from the Mac and used Your 3.7v 400MAh battery and the 3.7v 500mAh batteries. When using ONLY the battery nothing visual happens on the board, however, when I connected Speaker I could hear a lot of buzzing and hissing coming from the speaker. Occasionally the neopixel on D08 will turn red then turn off. The power switch appears to be working properly. When I plug the HalloWing back into the iMac things are functional again (expect #3) and the charging LED turns on. Unplugging the iMac causes all LEDs and display to turn off and loud buzzing and hissing comes from the speaker.
Tim
1. When downloading the CORRECT file (my bad) onto the HalloWing the HALLOWBOOT device shows up (using an iMac OS10.12.6)
2. I can, using the MU editor get things to work on the HallowWing like sound, neopixel strip, neopixel on the board.
3. I can NOT get any program to download using Arduino IDE. I have double checked that all libraries are up to date.
4. I can download any of the eye—.UF2 files and they will display, but are very dim.
5. NEW problem to report. .
To do all this testing I have only been using the HalloWing tethered to the iMac. After much testing today I disconnected it from the Mac and used Your 3.7v 400MAh battery and the 3.7v 500mAh batteries. When using ONLY the battery nothing visual happens on the board, however, when I connected Speaker I could hear a lot of buzzing and hissing coming from the speaker. Occasionally the neopixel on D08 will turn red then turn off. The power switch appears to be working properly. When I plug the HalloWing back into the iMac things are functional again (expect #3) and the charging LED turns on. Unplugging the iMac causes all LEDs and display to turn off and loud buzzing and hissing comes from the speaker.
Tim
- adafruit_support_carter
- Posts: 29483
- Joined: Tue Nov 29, 2016 2:45 pm
Re: HalloWing Screen Very dim
For the battery behavior - could be that the batteries are not fully charged. Could also be that you have a program running that is trying to connect to the serial debug console and is hanging there.
For the Arduino programming issue. Turn on verbose messages, try uploading the basic blink example, and post the output you get from the build process in the Arduino console here.
For the Arduino programming issue. Turn on verbose messages, try uploading the basic blink example, and post the output you get from the build process in the Arduino console here.
- geogriff
- Posts: 41
- Joined: Tue Dec 10, 2013 10:40 am
Re: HalloWing Screen Very dim
HI,
Here is the Arduino code:
Here is the output:
Here is the Arduino code:
Code: Select all
// the setup function runs once when you press reset or power the board
void setup() {
// initialize digital pin 13 as an output.
pinMode(13, OUTPUT);
}
// the loop function runs over and over again forever
void loop() {
digitalWrite(13, HIGH); // turn the LED on (HIGH is the voltage level)
delay(1000); // wait for a second
digitalWrite(13, LOW); // turn the LED off by making the voltage LOW
delay(200); // wait for a second
}
Sketch uses 10472 bytes (3%) of program storage space. Maximum is 262144 bytes.
Forcing reset using 1200bps open/close on port /dev/cu.usbmodem14341
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
PORTS {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } / {/dev/cu.Bluetooth-Incoming-Port, /dev/cu.usbmodem14341, /dev/tty.Bluetooth-Incoming-Port, /dev/tty.usbmodem14341, } => {}
Uploading using selected port: /dev/cu.usbmodem14341
/Users/timgriffin/Library/Arduino15/packages/arduino/tools/bossac/1.7.0/bossac -i -d --port=cu.usbmodem14341 -U true -i -e -w -v /var/folders/rq/vp81qn5n0fvcbgl5tjl85cv40000gn/T/arduino_build_486988/M0_Blink_Test.ino.bin -R
Set binary mode
readWord(addr=0)=0x20002dd8
readWord(addr=0xe000ed00)=0x410cc601
readWord(addr=0x41002018)=0x10010305
version()=v1.1 [Arduino:XYZ] Jul 29 2018 19:32:54
chipId=0x10010005
Connected at 921600 baud
readWord(addr=0)=0x20002dd8
readWord(addr=0xe000ed00)=0x410cc601
readWord(addr=0x41002018)=0x10010305
Atmel SMART device 0x10010005 found
write(addr=0x20004000,size=0x34)
writeWord(addr=0x20004030,value=0x10)
writeWord(addr=0x20004020,value=0x20008000)
Device : ATSAMD21G18A
readWord(addr=0)=0x20002dd8
readWord(addr=0xe000ed00)=0x410cc601
readWord(addr=0x41002018)=0x10010305
Chip ID : 10010005
version()=v1.1 [Arduino:XYZ] Jul 29 2018 19:32:54
Version : v1.1 [Arduino:XYZ] Jul 29 2018 19:32:54
Address : 8192
Pages : 3968
Page Size : 64 bytes
Total Size : 248KB
Planes : 1
Lock Regions : 16
Locked : readWord(addr=0x41004020)=0xffff
readWord(addr=0x41004020)=0xffff
readWord(addr=0x41004020)=0xffff
readWord(addr=0x41004020)=0xffff
readWord(addr=0x41004020)=0xffff
readWord(addr=0x41004020)=0xffff
readWord(addr=0x41004020)=0xffff
readWord(addr=0x41004020)=0xffff
readWord(addr=0x41004020)=0xffff
readWord(addr=0x41004020)=0xffff
readWord(addr=0x41004020)=0xffff
readWord(addr=0x41004020)=0xffff
readWord(addr=0x41004020)=0xffff
readWord(addr=0x41004020)=0xffff
readWord(addr=0x41004020)=0xffff
readWord(addr=0x41004020)=0xffff
none
readWord(addr=0x41004018)=0
Security : false
Boot Flash : true
readWord(addr=0x40000834)=0x7000a
BOD : true
readWord(addr=0x40000834)=0x7000a
BOR : true
Arduino : FAST_CHIP_ERASE
Arduino : FAST_MULTI_PAGE_WRITE
Arduino : CAN_CHECKSUM_MEMORY_BUFFER
Erase flash
chipErase(addr=0x2000)
done in 0.828 seconds
Write 10728 bytes to flash (168 pages)
write(addr=0x20005000,size=0x1000)
writeBuffer(scr_addr=0x20005000, dst_addr=0x2000, size=0x1000)
[=========== ] 38% (64/168 pages)write(addr=0x20005000,size=0x1000)
writeBuffer(scr_addr=0x20005000, dst_addr=0x3000, size=0x1000)
[====================== ] 76% (128/168 pages)write(addr=0x20005000,size=0xa00)
writeBuffer(scr_addr=0x20005000, dst_addr=0x4000, size=0xa00)
[==============================] 100% (168/168 pages)
done in 0.064 seconds
Verify 10728 bytes of flash with checksum.
checksumBuffer(start_addr=0x2000, size=0x1000) = 896d
checksumBuffer(start_addr=0x3000, size=0x1000) = 2018
checksumBuffer(start_addr=0x4000, size=0x9e8) = bd7f
Verify successful
done in 0.015 seconds
CPU reset.
readWord(addr=0)=0x20002dd8
readWord(addr=0xe000ed00)=0x410cc601
readWord(addr=0x41002018)=0x10010305
writeWord(addr=0xe000ed0c,value=0x5fa0004)
Last edited by adafruit_support_carter on Tue Nov 20, 2018 3:47 pm, edited 1 time in total.
Reason: added markup tags
Reason: added markup tags
- adafruit2
- Posts: 22200
- Joined: Fri Mar 11, 2005 7:36 pm
Re: HalloWing Screen Very dim
the UF2s we generated and put online have half-brightness display on purpose. they're not 'very dim' they're just not 'overdriven and bright' - the hallowing is fine
Please be positive and constructive with your questions and comments.