any tip on how to connect?

I have connected directly on serial port and trough different usb2serial adapters using hyper terminal or putty, with different baudrates, but I'm receiving only ASCII chars?

Please HELP.

any tip on how to connect?

 

I have connected directly on serial port and trough different usb2serial adapters using hyper terminal or putty, with different baudrates, but I'm receiving only ASCII chars?

Connect uart adapter to pins (as in your image), power on your device and you will see bootloader's boot log. Be sure you using 3.3-volt version of adapter, not 5V. If nothing happens try to exchange TX and RX pins.

Also, NOR flash contains bootloader code at the beginning, so if your device have corrupted NOR flash it will not boot. In this case you should reflash NOR flash using JTAG or by desoldering chip and using programmer.

Connect uart adapter to pins (as in your image), power on your device and you will see bootloader's boot log. Be sure you using 3.3-volt version of adapter, not 5V. If nothing happens try to exchange TX and RX pins.

 

Also, NOR flash contains bootloader code at the beginning, so if your device have corrupted NOR flash it will not boot. In this case you should reflash NOR flash using JTAG or by desoldering chip and using programmer.

I;m getting this and after 20sec it's restarting

U-Boot 2009.08 ( 3月 19 2014 - 10:34:06)

CPU: Freescale i.MX6 family TO1.1 at 792 MHz
Thermal sensor with ratio = 175
Temperature:   46 C, calibration data 0x5534a27d
mx6q pll1: 792MHz
mx6q pll2: 528MHz
mx6q pll3: 480MHz
mx6q pll8: 50MHz
ipg clock     : 66000000Hz
ipg per clock : 66000000Hz
uart clock    : 80000000Hz
cspi clock    : 60000000Hz
ahb clock     : 132000000Hz
axi clock   : 198000000Hz
emi_slow clock: 99000000Hz
ddr clock     : 396000000Hz
usdhc1 clock  : 198000000Hz
usdhc2 clock  : 198000000Hz
usdhc3 clock  : 198000000Hz
usdhc4 clock  : 198000000Hz
nfc clock     : 24000000Hz
Board: i.MX6DL/Solo-JUPITER: unknown-board Board: 0x61011 [POR ]
Boot Device: NOR
I2C:   ready
DRAM:   1 GB
Flash:  8 MB
MMC:   FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2
Using default environment

In:    serial
Out:   serial
Err:   serial
***** display DDR calibration result *****
***************************************
Display result(register) of WriteLeveling

   MMDC registers updated from WriteLeveling
   MPWLDECTRL0 (0x021b080c) = 0x0045004C
   MPWLDECTRL1 (0x021b0810) = 0x001B001D
***************************************
Display result(register) of DDR calibration

   MMDC registers updated from calibration

   Read DQS Gating calibration
   MPDGCTRL0 PHY0 (0x021b083c) = 0x42470224
   MPDGCTRL1 PHY0 (0x021b0840) = 0x01790203

   Read calibration
   MPRDDLCTL PHY0 (0x021b0848) = 0x45474B44

   Write calibration
   MPWRDLCTL PHY0 (0x021b0850) = 0x413D413F
***************************************


Net:   got MAC address from IIM: 00:00:00:00:00:00
FEC0 [PRIME]
BSP A is valid
BSP B is valid
imx6 core num: 2
BSP A is valid
BSP B is valid
match invalid password 1.
boot easyrecovery !!
main loop boot env = run bootargs;booti ${bootaddr}
Hit any key to stop autoboot:  0
kernel   @ 10808000 (2827328)
ramdisk  @ 11800000 (877933)
kernel cmdline:
        use uboot command line:
        console=ttymxc0,115200 init=/init androidboot.console=ttymxc0 video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:dev=ak8814,BT656-NTSC,if=BT656,bpp=32 video=mxcfb2:off fbmem=6M,6M vmalloc=400M androidboot.hardware=freescale arm_freq=800 printk.time=1 printk_console=off

Starting kernel ...

MX6SDL JUPITER KT 4.2.2 U-Boot > help
?       - alias for 'help'
autoscr - DEPRECATED - use "source" command instead
base    - print or set address offset
bdinfo  - print Board Info structure
bmp     - manipulate BMP image data
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
booti   - booti   - boot android bootimg from memory

bootm   - boot application image from memory
bootp   - boot image via network using BOOTP/TFTP protocol
bsp     - get bsp info, or set bsp info

clear_bootf- clear Warp!! bootflag
clk     - Clock sub system
cls     - clear screen
cmp     - memory compare
coninfo - print console devices and information
cp      - memory copy
crc32   - checksum calculation
dhcp    - boot image via network using DHCP/TFTP protocol
download_mode- download_mode - enter i.MX serial/usb download mode
echo    - echo args to console
erase   - erase FLASH memory
ext2load- load binary file from a Ext2 filesystem
ext2ls  - list files in a directory (default /)
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
flinfo  - print FLASH memory information
go      - start application at address 'addr'
help    - print online help
i2c     - I2C sub-system
iminfo  - print header information for application image
imxotp  - One-Time Programable sub-system
imxtract- extract a part of a multi-image
itest   - return true/false on integer compare
loadb   - load binary file over serial line (kermit mode)
loads   - load S-Record file over serial line
loady   - load binary file over serial line (ymodem mode)
loop    - infinite loop on address range
md      - memory display
memchk  - memory check
mii     - MII utility commands
mm      - memory modify (auto-incrementing address)
mmc     - MMC sub system
mmcinfo - display MMC info
model   - get model info, or set model info.

mtest   - simple RAM read/write test
mw      - memory write (fill)
nfs     - boot image via network using NFS protocol
nm      - memory modify (constant address)
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
rarpboot- boot image via network using RARP/TFTP protocol
regul   - Regulator sub system
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
setenv  - set environment variables
sf      - SPI flash sub-system
sleep   - delay execution for some time
source  - run script from memory
sspi    - SPI utility commands
tftpboot- boot image via network using TFTP protocol
version - print monitor version
warp    - Warp!! boot

MX6SDL JUPITER KT 4.2.2 U-Boot > printenv
bootdelay=0
baudrate=115200
ipaddr=192.168.1.103
serverip=192.168.1.101
netmask=255.255.255.0
loadaddr=0x10800000
rd_loadaddr=0x11000000
netdev=eth0
ethprime=FEC0
bootfile=uImage
splashimage=0x8130000
splashpos=0,0
lvds_num=0
stdin=serial
stdout=serial
stderr=serial
ethact=FEC0
printk.console=off
console_kernel=ttymxc0,115200
console_android=ttymxc0
printk.time=1
bootargs=setenv bootargs console=${console_kernel} init=/init androidboot.console=${console_android} ${smp} video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:dev=ak8814,BT656-NTSC,if=BT656,bpp=32 video=mxcfb2:off fbmem=6M,6M vmalloc=400M androidboot.hardware=freescale arm_freq=800 printk.time=${printk.time} printk_console=${printk.console}
bootaddr=0x08370000

Environment size: 719/8188 bytes

Please enter "bsp get" (w/o quotes) and post output here. Also please check your PM.

MX6SDL JUPITER KT 4.2.2 U-Boot > bsp get

BSP A is valid

BSP B is valid

##  A Side BSP Information:

        Magic Number       :0xa55a5aa5(a55a5aa5:Valid, other:Invalid)

        Boot Mode          :0x00000002(0:Normal,

                                       1:Recovery,

                                       2:EasyRecovery,

                                       3:Re-EasyRecovery,

                                       default:Normal)

        Launch Mode        :0x00000003(0:APL,

                                       1:TestMode.apk,

                                       2:Slave TestMode,

                                       3:Boot Error,

                                       default:APL)

        TestMode Sub-Mode  :0x00000000(0:TextMode_A.key, 1:Serv Mode,        2:Tech Mode,     default:Tech Mode)

        Bootimage Side     :0x00000000(0:Side A,         1:Side B,                            default:Side A)

        Recoveryimage Side :0x00000000(0:Side A,         1:Side B,                            default:Side A)

        Debug Switch       :0x00000000(0:OFF,            1:ON,                                default:OFF)

        Usb OTG Switch     :0x00000000(0:Host,           1:Device,                            default:Host)

        Memchk flag        :0x00000000(0:No,             1:Yes,                               default:No)

        Warp boot          :0x00000000(0:Side A,         1:Side B,                            default:Side A)

        Boot Sub-Mode      :0x00000002(0:Normal,         1:Catch snapshot,   2:Warp,          default:Normal)

        Update flag        :0x0000000c(0:Recovery-Update,

                                       1:uboot update,

                                       2:boot.img update,

                                       3:recovery.img update,

                                       4:system.img update,

                                       5:opening data update,

                                       6:UI update,

                                       7:All image update,

                                       8:TESTMODE_N.KEY,

                                       9:easyrecovery copy,

                                       a:easyrecovery copy&verify,

                                       b:password key copy&verify,

                                       c:easyrecovery mode change,

                                       default:Recovery-Update)

        Update sub-flag    :0x00000000(0:SD Card,        1:USB1,             2:USB2           default:SD Card)

        UI Update  flag    :0x00000000(0:non-updating,   1:updating,         default:non-updating)

        Reserved1  flag    :0xffffffff(default:0xFFFFFFFF)

        Reserved2  flag    :0xffffffff(default:0xFFFFFFFF)

##  B Side BSP Information:

        Magic Number       :0xa55a5aa5(a55a5aa5:Valid, other:Invalid)

        Boot Mode          :0x00000002(0:Normal,

                                       1:Recovery,

                                       2:EasyRecovery,

                                       3:Re-EasyRecovery,

                                       default:Normal)

        Launch Mode        :0x00000003(0:APL,

                                       1:TestMode.apk,

                                       2:Slave TestMode,

                                       3:Boot Error,

                                       default:APL)

        TestMode Sub-Mode  :0x00000000(0:TextMode_A.key, 1:Serv Mode,        2:Tech Mode,     default:Tech Mode)

        Bootimage Side     :0x00000000(0:Side A,         1:Side B,                            default:Side A)

        Recoveryimage Side :0x00000000(0:Side A,         1:Side B,                            default:Side A)

        Debug Switch       :0x00000000(0:OFF,            1:ON,                                default:OFF)

        Usb OTG Switch     :0x00000000(0:Host,           1:Device,                            default:Host)

        Memchk flag        :0x00000000(0:No,             1:Yes,                               default:No)

        Warp boot          :0x00000000(0:Side A,         1:Side B,                            default:Side A)

        Boot Sub-Mode      :0x00000002(0:Normal,         1:Catch snapshot,   2:Warp,          default:Normal)

        Update flag        :0x0000000c(0:Recovery-Update,

                                       1:uboot update,

                                       2:boot.img update,

                                       3:recovery.img update,

                                       4:system.img update,

                                       5:opening data update,

                                       6:UI update,

                                       7:All image update,

                                       8:TESTMODE_N.KEY,

                                       9:easyrecovery copy,

                                       a:easyrecovery copy&verify,

                                       b:password key copy&verify,

                                       c:easyrecovery mode change,

                                       default:Recovery-Update)

        Update sub-flag    :0x00000000(0:SD Card,        1:USB1,             2:USB2,          default:SD Card)

        UI Update  flag    :0x00000000(0:non-updating,   1:updating,         default:non-updating)

        Reserved1  flag    :0xffffffff(default:0xFFFFFFFF)

        Reserved2  flag    :0xffffffff(default:0xFFFFFFFF)

##  A Side BSP Information:
        Boot Mode          :0x00000002(0:Normal,
                                       1:Recovery,
                                       2:EasyRecovery,
                                       3:Re-EasyRecovery,
                                       default:Normal)
        Launch Mode        :0x00000003(0:APL,
                                       1:TestMode.apk,
                                       2:Slave TestMode,
                                       3:Boot Error,
                                       default:APL)
##  B Side BSP Information:
        Launch Mode        :0x00000003(0:APL,
                                       1:TestMode.apk,
                                       2:Slave TestMode,
                                       3:Boot Error,
                                       default:APL)

Please try to set both boot mode and launch mode to zero to check if this helps you. Use "bsp set [parameters]" command. Don't remember right command format, try "help bsp" or "bsp help", maybe "help bsp set" to show right parameters.

MX6SDL JUPITER KT 4.2.2 U-Boot > help bsp set
bsp - get bsp info, or set bsp info


Usage:
bsp Usage:
bsp init - init bsp information to init value
bsp get  - get bsp information from nor flash
bsp passwd  <passwd> - set sd card password (16bytes)
bsp set  <item> <value> - set bsp information to nor flash
item
  -m: set boot mode
      value
        0: Normal
        1: Recovery
        2: EasyRecovery(CopyDevice)
        3: Re-EasyRecovery
  -l: set launch mode flag
      value
        0: APL
        1: TestMode.apk
        2: Slave TestMode
        3: Boot Error
  -t: set TestMode Sub Mode
      value
        0: Tech Mode
        1: Serv Mode
        2: TestMode_A.key
  -b: set bootimage active side flag
      value
        0: Side A
        1: Side B
  -r: set recoveryimage active side flag
      value
        0: Side A
        1: Side B
  -d: set debug on/off switch
      value
        0: OFF
        1: ON
  -u: set usb otg switch
      value
        0: Host
        1: Device
  -c: set memchk flag
      value
        0: No
        1: Yes
  -w: set warp boot active side flag
      value
        0: Side A
        1: Side B
  -s: set boot sub mode flag
      value
        0: Normal
        1: Catch snapshot
        2: Warp
  -f: set update flag
      value
        0: Recovery-Update
        1: uboot update
        2: boot.img update
        3: recovery.img update
        4: system.img update
        5: opening data update
        6: UI update
        7: All image update
        8: TESTMODE_N.KEY
        9: easyrecovery copy
        10: easyrecovery copy&verify
        11: password key copy&verify
        12: easyrecovery mode change
  -sf: set update sub flag
      value
        0: SD Card
        1: USB1
        2: USB2
  -uif: set ui update flag
      value
        0: non-updating
        1: updating

setenv - set environment variables

Usage:
setenv name value ...
    - set environment variable 'name' to 'value ...'
setenv name
    - delete environment variable 'name'

this is the help file

I tried "bsp init" and it's booting now

THANK YOU mate.... 

Now: how can I restore NOR backup from other unit to this one. I think this one has NOR corrupted that's why easyrecovery didn't boot. Also I think that is the cause for GPS not going to be initialized

Thanks again

NOR flash contains different areas, easyrecovery is at the end, but another areas are also present (like bsp, serial number, model info and so on), so you should restore only needed parts and only from the same device. Also, as I said before, NOR flash contains bootloader code, so it is very easy to completely brick your device.

Partial information about NOR flash contents and how to rewrite NOR flash areas you can find here: http://avic411.com/index.php?/topic/81468-the-avic-development-mod/?p=334364

You need to erase flash regions using ioctl (memory will be filled with 0xFF values), then write new data to this regions using dd command from unix console (you can use UART with right BSP settings).

can you help with a script to write mtd1 and mtd2? I don't understand how to do it. Thanks

Please backup all three areas of your current device NOR flash (mtdX) and use any binary comparison tool to check differences with backup you already have. It seems for me that your nor flash isn't completely broken.

Also please check your PM again.

Hi all I'm kind of new to all this JTAG and Uart stuff. Could someone explain to me exactly how to hook up my Altera unit to the pioneer RGB port. I've been looking around on the site and can't see anything or anyone exactly explaining the details of how it actually supposed to be hooked up from the JTAG to the Pioneer unit any help would be appreciated

Hello, I have a new 8200Nex. Does this process still work in backing up the NOR and SD card images. 

Thank you

My 8200 died also- in 3 months. I'm waiting for it to get back from pioneer and I'm trying to get set up to backup when it gets back to me. Wondering if this process is good for 8200? 

I recently purchased a fully functional 8400NEX and I am attempting to backup the current BSP and Nor Flash.  I extracted the contents of NORFlashBackup.zip to a USB Stick, plugged it into USB Port 1 and powered on the 8400NEX.  The unit just boots normally instead of going into "Technical TestMode".  I am on firmware 1.00.  Does anyone know why it doesn't boot into "Technical TestMode"?

Hi all,

I am in no way a skilled software person, but I do like to try and fix things.  I have a W4400NEX that showed a "software error" screen yesterday afternoon.  Now, every time it boots up, it hangs for a bit at the Pioneer loading screen then shows my custom background image without anything else.  None of the buttons on the front work.  After a few seconds, the display shows something that I can describe as color static, then goes back to the custom desktop image.  It does this for a few minutes then the screen just goes black.

I tried to get into technical test mode - but the device doesn't seem to do anything different when it boots.  I've tried a few USB sticks to boot, all FAT32 that contain testmode_a and Copy_Script.sh.  I always start is USB 1 and then try 2 just in case.  Nothing.  

I took out the internal SD card from Pioneer and none of my computers will read it - disk management just hangs when I try to run it with that SD card in my computer.

Does anyone know if this is a NOR corruption issue or just a bad SD card from Pioneer?

Any help would be greatly appreciated.

Thanks,

Vegas

On 1/8/2020 at 8:59 AM, VegasMSU said:

Hi all,

I am in no way a skilled software person, but I do like to try and fix things.  I have a W4400NEX that showed a "software error" screen yesterday afternoon.  Now, every time it boots up, it hangs for a bit at the Pioneer loading screen then shows my custom background image without anything else.  None of the buttons on the front work.  After a few seconds, the display shows something that I can describe as color static, then goes back to the custom desktop image.  It does this for a few minutes then the screen just goes black.

I tried to get into technical test mode - but the device doesn't seem to do anything different when it boots.  I've tried a few USB sticks to boot, all FAT32 that contain testmode_a and Copy_Script.sh.  I always start is USB 1 and then try 2 just in case.  Nothing.  

I took out the internal SD card from Pioneer and none of my computers will read it - disk management just hangs when I try to run it with that SD card in my computer.

Does anyone know if this is a NOR corruption issue or just a bad SD card from Pioneer?

Any help would be greatly appreciated.

Thanks,

Vegas

Ithink i not works  

Dang, I got the SD Card for the 4200 hoping I could just grab the IMG file. Sadly, it's a Pioneer disk and do I can't see the partitions on it. Without the radio I can't do the backup process you have here.
Does anyone have a 4200 who would be able to create the IMG file? 

Again, I'm asking because I don't have the radio unit or I would.
I wanted to get the file for everyone looking for that IMG disk. 

I just bought an AVIC-8600NEX and want to backup my SD card right after I install it.

I downloaded the backup files. I will see if I can get this to work once I get my AVIC installed.

Hello, I'm posting here in this old thread rather than make a new one as my question / request relates to this topic.

My unit an F60dab  I'm trying to restore is boot looping still after failed update. After many months looking I now have a new sdcard (internal) with new firmware -incase!! Trouble is because bloody unit is looping I've been advised unit needs to be ' reset ' via PuTTy via a usb - serial connection. I've done all this and at times I can see lots of data, similar to those in posts above.

But for the life of me, despite reading through PuTTy help / info, I cannot figure out how to send commands.

From above I need to send ' BSP SET  0 ' but where do I type it ?

Does anyone know ?

I'm running the prog from serial settings, then click apply and the prog converts to a new dos type window showing all the data. But it wont let me type anything. Is there anyone that can please advise what I'm doing wrong. Thanks

you have 3 seconds to get to the uBoot console.

after turning on the radio, you need to press any button on the keyboard. the console will become available.

if within 10 or 15 seconds you do not enter any command, the radio will reboot into normal mode. in your case "easyrecovery"
in the console, enter the command "warp" the radio will reboot.

Hi, thanks for advice.

I tried all night but now something isnt working right.

As soon as i click open on Putty, (without radio switched on) im getting a new window with streams of data garbage, that looks like upside down U's. Obviously tried connections etc.

If I switch on radio (before I click open) nothing happens.

I think the usb things shagged. I'll get another one.

Quick Q's, as I've not done this before, is U-boot a menu? in the radio. I searched the web but could only find referance to android boot options.

check the connection. and PuTTy settings

Good afternoon. I got the settings thanks. Problem was cheap usb - serial device. I think it fried somehow??

Anyhow, got new one yesterday and installed PuTty on another better laptop. Still win 11 tho :-(

result was exactly the same. I tried with settings window open -> turned on radio. Nothing.

Opened Putty after setting as above and then get uboot window. tried everything to add command, pressed keys / space bar etc as soon as radio turned on and always the same.

I dont get all the data that other posts have shown before it reloops. But Im pasting below a couple of loops worth. You might see something in here thats useful? The strange characters are a worry ?

Net:   got MAC address from IIM: 00:00:00:00:00:00
FEC0 [PRIME]
BSP A is valid
BSP B is valid
imx6 core num: 2
BSP A is valid
BSP B is valid
warp boot side A

Lineo Warp!! 4.0.0 (Jupiter14 1.0.1) Tue Jan 14 13:23:03 JST 2014

SDHC2 'SU32G'  30436MB  4bit  50.0Mbit/s (HS)  block: 512  sect: 127  spec: 3
Snapshot ID : e95d22fe
Snapshot total size : 0x123fb440   compressed size : 0x02e35974
--- Read Snapshot ---
00800000

U-Boot 2009.08 (Jan 06 2014 - 16:32:44)

CPU: Freescale i.MX6 family TO1.1 at 792 MHz
Thermal sensor with ratio = 181
Temperature:   30 C, calibration data 0x57c4c97d
mx6q pll1: 792MHz
mx6q pll2: 528MHz
mx6q pll3: 480MHz
mx6q pll8: 50MHz
ipg clock     : 66000000Hz
ipg per clock : 66000000Hz
uart clock    : 80000000Hz
cspi clock    : 60000000Hz
ahb clock     : 132000000Hz
axi clock   : 198000000Hz
emi_slow clock: 99000000Hz
ddr clock     : 396000000Hz
usdhc2 clock  : 198000000Hz
usdhc3 clock  : 198000000Hz
usdhc4 clock  : 198000000Hz
nfc clock     : 24000000Hz
Board: i.MX6DL/Solo-JUPITER: unknown-board Board: 0x61011 [POR ]
Boot Device: NOR
I2C:   ready
DRAM:   1 GB
Flash:  8 MB
MMC:   FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2
Using default environment

In:    serial
Out:   serial
Err:   serial
***** display DDR calibration result *****
***************************************
Display result(register) of WriteLeveling

   MMDC registers updated from WriteLeveling
   MPWLDECTRL0 (0x021b080c) = 0x002F0035
   MPWLDECTRL1 (0x021b0810) = 0x0018001C
***************************************
Display result(register) of DDR calibration

   MMDC registers updated from calibration

   Read DQS Gating calibration
   MPDGCTRL0 PHY0 (0x021b083c) = 0x421D0214
   MPDGCTRL1 PHY0 (0x021b0840) = 0x0177017B

   Read calibration
Q1▒PHY0 (0x021b0848) = 0x48494C49

   Write calibration
   MPWRDLCTL PHY0 (0x021b0850) = 0x413E3F41
***************************************

Net:   got MAC address from IIM: 00:00:00:00:00:00
FEC0 [PRIME]
BSP A is valid
BSP B is valid
imx6 core num: 2
warp boot side A

Lineo Warp!! 4.0.0 (Jupiter14 1.0.1) Tue Jan 14 13:23:03 JST 2014

SDHC2 'SU32G'  30436MB  4bit  50.0Mbit/s (HS)  block: 512  sect: 127  spec: 3
Snapshot ID : e95d22fe
Snapshot total size : 0x123fb440   compressed size : 0x02e35974
--- Read Snapshot ---
00800000,▒▒▒▒▒▒cc00000
C▒▒▒▒$HHHT"@▒▒▒▒▒▒▒▒▒▒▒▒▒@  ▒ @▒warp boot side A

Lineo Warp!! 4.0.0 (Jupiter14 1.0.1) Tue Jan 14 13:23:03 JST 2014

SDHC2 'SU32G'  30436MB  4bit  50.0Mbit/s (HS)  block: 512  sect: 127  spec: 3
00800000▒▒▒▒▒▒▒0▒▒j3c800000
▒▒▒▒~▒▒▒▒?▒▒▒▒  B▒▒▒▒▒H▒+D▒A  (@▒▒
                                  ▒ @ @ @@▒@▒  ▒▒@@@▒ ▒@▒ ▒@▒ ▒

U-Boot 2009.08 (Jan 06 2014 - 16:32:44)

if you cannot enter commands, then you have a problem connecting the TX wire from the USB TTL adapter

you also have an unstable RX connection
 I see artifacts in your log

4 hours ago, cleverdicky said:

Snapshot total size : 0x123fb440   compressed size : 0x02e35974
--- Read Snapshot ---
00800000,▒▒▒▒▒▒cc00000
C▒▒▒▒$HHHT"@▒▒▒▒▒▒▒▒▒▒▒▒▒@  ▒ @▒warp boot side A

Lineo Warp!! 4.0.0 (Jupiter14 1.0.1) Tue Jan 14 13:23:03 JST 2014

SDHC2 'SU32G'  30436MB  4bit  50.0Mbit/s (HS)  block: 512  sect: 127  spec: 3
00800000▒▒▒▒▒▒▒0▒▒j3c800000
▒▒▒▒~▒▒▒▒?▒▒▒▒  B▒▒▒▒▒H▒+D▒A  (@▒▒
                                  ▒ @ @ @@▒@▒  ▒▒@@@▒ ▒@▒ ▒@▒ ▒

U-Boot 2009.08 (Jan 06 2014 - 16:32:44)

 

 

 

Guys i've been at this for hours. Although Im nearly blind now staring at those tiny holes, I've remade connections and data is nice and clean now. Thanks for the tip.

But still not sending commands. I press keys as soon as pwr to radio and keep pressing but nothing opens. If I click open 1st then turn on radio I get data, but still nothing happens when I press keys. I've checked and rechecked all pins. over and over. I've also searched for an older version of PuTTy as I noticed the images here dont match the one I have.

I will have a search & read for an alternative unless there are any recomendations.