SerialFlash RawHardwareTest errors, TeensyTransfer not detecing Prop Shield

Status
Not open for further replies.
M

MrShadowMan

Member
Trying to get TeensyTransfer to work, but when I run teensytransfer -i I get this
Code: 
ID    : 00 00 00
Serial: 00 00 00 00 00 00 00 00
Size  : 0 Bytes

I saw a few other posts in this form suggested trying to run SerialFlash to make sure the flash memory is actuall working. When I try to run the RawHardwareTest example sketch, I get these errors when trying to open the serial monitor
Code: 
Sketch uses 23656 bytes (9%) of program storage space. Maximum is 262144 bytes.
Global variables use 4244 bytes (6%) of dynamic memory, leaving 61292 bytes for local variables. Maximum is 65536 bytes.
Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError: Java heap space
Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError: Java heap space
Exception in thread "SocketListener(DESKTOP-LQDSJFR-attlocal-net.local.)" java.lang.IllegalStateException: Timer already cancelled.
	at java.util.Timer.sched(Timer.java:397)
	at java.util.Timer.schedule(Timer.java:193)
	at javax.jmdns.impl.DNSTaskStarter$DNSTaskStarterImpl$StarterTimer.schedule(DNSTaskStarter.java:219)
	at javax.jmdns.impl.tasks.Responder.start(Responder.java:98)
	at javax.jmdns.impl.DNSTaskStarter$DNSTaskStarterImpl.startResponder(DNSTaskStarter.java:395)
	at javax.jmdns.impl.JmDNSImpl.startResponder(JmDNSImpl.java:1753)
	at javax.jmdns.impl.JmDNSImpl.handleQuery(JmDNSImpl.java:1543)
	at javax.jmdns.impl.SocketListener.run(SocketListener.java:59)


Arduino in general seems to be very janky. Just trying to load mp3 files so I can play them through a small speaker on the prop shield. Using Teensy 3.2
 
Then, try to make hardware-test working. With a not working hardware-test its not worth to try other things like TeensyTransfer.
Maybe post a photo our yout teensy, with soldered prop-shield?
 
Serial monitor showed this.
Code: 
Raw SerialFlash Hardware Test



Read Chip Identification:

  JEDEC ID:     0 0 0

  Part Nummber: (unknown chip)

  Memory Size:  0 bytes



Tests Failed  :{



The flash chip may be left in an improper state.

You might need to power cycle to return to normal.

Does power cycling in this case mean just disconnecting and reconnecting the usb over and over?

Attaching a visual of my setup
**EDIT:** Looks like the image doesn't want to attach. If you think it's helpful I can post an imgur link
 
Image attach is limited to 1MB or less JPG/PNG/?

Not finding the JEDEC ID means the chip is not soldered/wired/functioning correctly - perhaps just the wrong CS pin if all else is right.
 
Ah, that is very likley the case then. I had to solder a new board yesterday. I'll resolder and get back with my results. If it still doesnt work I will try compressing the image and posting it.
 
The PC restart was to get rid of the java exceptions.
Defragster is right, there is something wrong with the hardware.
 
Yes. The MEM_CS pin is pin 6 on the schema, and that is what I am using in the RawHardwareTest code
Code: 
const int FlashChipSelect = 6; // digital pin for flash chip CS pin
 
I wired up a button to pin 6, and it does detect input. Yet, using pin 6 for accessing flash memory, it still does not find the JEDEC ID. When running teensytransfer, using the '.\teensytransfer.exe -i' command gives me this, which I presume is the same information.

Code: 
ID    : 00 00 00
Serial: 00 00 00 00 00 00 00 00
Size  : 0 Bytes

This is odd. This suggests it is definitley hardware. However I have soldered it correctly, and I have tried wiring other devices to the pin to check the pin, and there is electricity running through it. I don't understand what this means. Is the board bad? Is there something completely obvious that I just do not understand? I can provide any other information if it is helpful.
 
Hm, we need more information.
- which Teensy?
- It would be best to post the complete Sketch (even if it's only a modified example)

Maybe we can find something..
Unfortunately, the only propshield I have is soldered to a T3.2.
 
Running 3.2, using a non-modified version of your Teensy Transfer tool from github, and a non-modified version of the Serial Flash RawHardwareTest code.

Code: 
/*
  TeensyTransfer Demo
  
  To make a USB RawHID device, use the Tools > USB Type menu	
*/


#include <TeensyTransfer.h>

const int FlashChipSelect = 6;

void setup() 
{

//>>>UNCOMMENT THESE IF USING THE TEENSY AUDIO SHIELD

//  SPI.setSCK(14);  // Audio shield has SCK on pin 14
//  SPI.setMOSI(7);  // Audio shield has MOSI on pin 7


//>>>REMOVE unneeded / not connected devices here:

  eeprom_initialize();
  SerialFlash.begin(FlashChipSelect);

}


void loop() {
	ttransfer.transfer();
}


I would post the RawHardwareTest code, but it is roughly 500 lines. I'll post a few of the first lines to make sure we are on the same page.

Code: 
// If you discover an incompatible chip, please report it here:
// https://github.com/PaulStoffregen/SerialFlash/issues
// You MUST post the complete output of this program, and
// the exact part number and manufacturer of the chip.


#include <SerialFlash.h>
#include <SPI.h>

const int FlashChipSelect = 6; // digital pin for flash chip CS pin
//const int FlashChipSelect = 21; // Arduino 101 built-in SPI Flash

SerialFlashFile file;

const unsigned long testIncrement = 4096;

void setup() {

  //uncomment these if using Teensy audio shield
  //SPI.setSCK(14);  // Audio shield has SCK on pin 14
  //SPI.setMOSI(7);  // Audio shield has MOSI on pin 7

  //uncomment these if you have other SPI chips connected
  //to keep them disabled while using only SerialFlash
  //pinMode(4, INPUT_PULLUP);
  //pinMode(10, INPUT_PULLUP);

  Serial.begin(9600);

  while (!Serial) ;
  delay(100);

  Serial.println("Raw SerialFlash Hardware Test");
  SerialFlash.begin(FlashChipSelect);

If it would help I can share a dropbox link. Or if it is appropriate, I can post the full RawHardwareTest code in a new reply.
 
Okay (or not okay):
I loaded the RawHardwareTest example. Unmodfied.
There are some files stored on the Flash, and I did not want to delete them. The output looks like this:
Code: 
Raw SerialFlash Hardware Test

Read Chip Identification:
  JEDEC ID:     EF 40 17
  Part Nummber: W25Q64FV
  Memory Size:  8388608 bytes
  Block Size:   65536 bytes

Reading Chip...
  Previous data found at address 0
  You must fully erase the chip before this test
  found this: 4C 55 96 FA 58 02 F6 18 
     correct: 00 00 00 00 15 F5 95 4B 

Tests Failed  :{

The flash chip may be left in an improper state.
You might need to power cycle to return to normal.
(Failed, because of the stored files..)

So, still, it must be a hardware failure... :-(
 
That is so weird. I can only assume that it is a bad board then. Since the pin delivers current, the only thing left is the circuitry on the board. Would you agree?
 
I haven't been able to play tones or any other files, but I had assumed that the files issue was just due to my not being able to transfer anything. To more clearly answer the question, I have not succeeded in having anything on the prop shield work so far. All of the pins, however, do work as far as I can tell.
 
Hm, perhaps a unwanted solder bridge somewhere that happened when attaching the pins..
I don't have other Ideas, at the moment.
That the whole shield is broken is very unlikely.
 
Status
Not open for further replies.
Back
Top