April 29th, 2019, 13:40
April 29th, 2019, 23:56
April 30th, 2019, 8:01
April 30th, 2019, 20:11
April 30th, 2019, 20:34
May 1st, 2019, 11:11
I wonder if the COM device provides access via Telnet?
Could we see photos of the PCB(s)?
Is there a firmware upgrade that we can dissect?
Are you able to format an SD card and record a short loop on it? If you then dump the first few megabytes of the card, we should then have some idea of the file system, file format, and possibly the OS (Linux?), assuming that the card is formatted in the same way as internal memory.
I'm also assuming that this procedure will not touch the contents of internal memory.
ftp://ftp.digitech.com/pub/PDFs/Manuals ... 0707-B.pdf
Edit: Do you have any saved loops that we could examine?
May 1st, 2019, 18:07
May 1st, 2019, 19:39
May 1st, 2019, 23:20
May 3rd, 2019, 7:38
10.5.3 USB Device Port
10.5.3.1 Supported External Crystal / External Clocks
The only frequency supported by SAM-BA Monitor to allow USB communication is a 12 MHz crystal or external
clock.
10.5.3.2 USB class
The device uses the USB communication device class (CDC) drivers to take advantage of the installed PC RS-232
software to talk over the USB. The CDC class is implemented in all releases of Windows ® , beginning with
Windows 98SE ® . The CDC document, available at www.usb.org, describes how to implement devices such as
ISDN modems and virtual COM ports.
The Vendor ID is Atmel’s vendor ID 0x03EB. The product ID is 0x6124. These references are used by the host
operating system to mount the correct driver. On Windows systems, the INF files contain the correspondence
between vendor ID and product ID.
May 3rd, 2019, 18:52
2x 512Mbit AT91SAM9G45 SoC
2x NT5TU64M8DE-3C .--------------------------.
.-----. |.-----------. | .-----------.
|SDRAM|--------|| 64KB RAM | |--|I/O devices|
'-----' |'-----------' | '-----------'
.-----------. |.-----------. | .----.
|JamMan code| || 64KB ROM | |-----|SDHC|
|-----------| || | .----------.| '----'
| |------||SAM-BA code| |USB-RS232C||
| Loop data | |'-----------' '----------'|
| | '-------------------|------'
| R/B*|---------. |
'-----------' | |
| | SAM-BA traffic
4Gbit NAND flash === |
GND |
MT29F4G16ABBDAHC:D .--------. CDC driver
temporarily |USB host| VID 0x03EB
ground R/B* '--------' PID 0x6124
pin during |
POST to .-----------.
invoke SAM-BA | Windows |
monitor |SAM-BA tool|
'-----------'
May 4th, 2019, 4:11
fzabkar wrote:Block #0 is guaranteed to be good by the NAND manufacturer. The remainder of the NAND is used to stored the guitar loops.
fzabkar wrote:AISI, you need to temporarily ground the NAND's Ready/Busy* pin during the POST in order to invalidate it. The SoC is then unable to find a boot device, which then causes it to invoke its SAM-BA monitor. AFAICT, you should be able to confirm that SAM-BA is active by typing "V" (Display Version) via a terminal program such as PuTTY or HyperTerminal.
fzabkar wrote:You may need to configure the address spaces first, though.
fzabkar wrote:Once again, I think that the AT91 forum is a much better place for support. I would at least ask for confirmation from one of their engineers before proceeding with my suggestions.
May 4th, 2019, 10:52
fzabkar wrote:AISI, this is the block diagram corresponding to the JamMan Stereo:
- Code:
2x 512Mbit AT91SAM9G45 SoC
2x NT5TU64M8DE-3C .--------------------------.
.-----. |.-----------. | .-----------.
|SDRAM|--------|| 64KB RAM | |--|I/O devices|
'-----' |'-----------' | '-----------'
.-----------. |.-----------. | .----.
|JamMan code| || 64KB ROM | |-----|SDHC|
|-----------| || | .----------.| '----'
| |------||SAM-BA code| |USB-RS232C||
| Loop data | |'-----------' '----------'|
| | '-------------------|------'
| R/B*|---------. |
'-----------' | |
| | SAM-BA traffic
4Gbit NAND flash === |
GND |
MT29F4G16ABBDAHC:D .--------. CDC driver
temporarily |USB host| VID 0x03EB
ground R/B* '--------' PID 0x6124
pin during |
POST to .-----------.
invoke SAM-BA | Windows |
monitor |SAM-BA tool|
'-----------'
Hey [name],
Are you sure that you're not accidentally in the external memory location of the pedal?
You may have accidentally deleted all the internal memory contents at some point before the last 2 loops were created. If that's the case, then it cannot be undone.
[name] [surname]
Technical Support Engineer
Harman Professional Solutions
May 5th, 2019, 2:50
May 5th, 2019, 7:37
May 5th, 2019, 16:42
May 6th, 2019, 9:26
fzabkar wrote:... (At this point it is a case of the blind leading the blind.) ...
May 6th, 2019, 18:44
May 6th, 2019, 19:21
August 8th, 2019, 6:36
.
├──Patch61
│ ├── patch.xml
│ └── PhraseA
│ ├── phrase.wav
│ └── phrase.xml
└──Patch62
├── patch.xml
└── PhraseA
├── phrase.wav
└── phrase.xml
<?xml version="1.0" encoding="UTF-8"?>
<JamManPatch device="JamManStereo" version="1" xmlns="http://schemas.digitech.com/JamMan/Patch">
<PatchName>Loop_61</PatchName>
<RhythmType>StudioKickAndHighHat</RhythmType>
<StopMode>StopInstantly</StopMode>
<SettingsVersion>0</SettingsVersion>
<ID>2e3060ae-1dd5-11b2-b40b-07403f8812ba</ID>
<OriginID>9324d1d0-1dd4-11b2-b40b-7fdc08c7c090</OriginID>
<Metadata>
<Description></Description>
<Artist></Artist>
<Genre>unspecified</Genre>
<Rating>0</Rating>
<Tags></Tags>
</Metadata>
</JamManPatch>
<?xml version="1.0" encoding="UTF-8"?>
<JamManPhrase xmlns="http://schemas.digitech.com/JamMan/Phrase" version="1">
<BeatsPerMinute>106.883</BeatsPerMinute>
<BeatsPerMeasure>4</BeatsPerMeasure>
<IsLoop>1</IsLoop>
<IsReversed>0</IsReversed>
<SettingsVersion>0</SettingsVersion>
<AudioVersion>0</AudioVersion>
<ID>2e3060ae-1dd5-11b2-b40b-07403f8812ba</ID>
</JamManPhrase>
Powered by phpBB © phpBB Group.