N2+ Blue,Red lights stuck on!!!

Post Reply
jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

I have an N2+ that I think I screwed up. I erased the mtd0 and mtd1 and no matter what it will not flash. I have tried recovery imaged and just spiboot files both. The blue and red light both stay on all the time. If i have no card at all in it, Its stuck on just red. There is no image from the HDMI, just black screen. NO petitboot to be found after the erase. Is there a way to use serial uart to flash petitboot back? May not be a lot of hope.

User avatar
tobetter
Posts: 13289
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 1022 times
Been thanked: 2313 times
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by tobetter »

After booting from SD card with the Petitboot recovery image, doesn't it boot up at all and stay with blue and red LEDs are on?
Have you tried boot with the same SD card with Petitboot recovery image after flashing? If it boots, can you try to erase all mtd partitions and try the recovery image again with new Petitboot image that its file name start with spiboot*?

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

I can flash recovery to the sdcard. When the N2 boots the light just stick on, both red and blue. The is a black screen on monitor .

User avatar
tobetter
Posts: 13289
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 1022 times
Been thanked: 2313 times
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by tobetter »

jshg46 wrote:
Fri May 31, 2024 12:39 pm
I can flash recovery to the sdcard. When the N2 boots the light just stick on, both red and blue. The is a black screen on monitor .
What image is flaed to the SD card?
What's the vendor and model of it?
Is the the boot select switch placed at MMC?

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

The lights both stay on at either setting on the switch. I have flashed several different recovery images to the card and they all do the same, except the old ones from 2019, the red light is the only light on with those.

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

spiupdate_odroidn2_20211112.img is the image flashed to it now.

User avatar
tobetter
Posts: 13289
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 1022 times
Been thanked: 2313 times
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by tobetter »

jshg46 wrote:
Fri May 31, 2024 12:54 pm
The lights both stay on at either setting on the switch. I have flashed several different recovery images to the card and they all do the same, except the old ones from 2019, the red light is the only light on with those.
After running the recovery image and boot from the same SD card, you must be able to erase the mtd partitions again. Then try the recovery image with SPIBOOT.IMG again.

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

They will not boot, They just sit there with both lights on solid. Black screen on monitor.

User avatar
tobetter
Posts: 13289
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 1022 times
Been thanked: 2313 times
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by tobetter »

jshg46 wrote:
Fri May 31, 2024 1:00 pm
They will not boot, They just sit there with both lights on solid. Black screen on monitor.
If the recovery image in SD card does not start, it might be the SD card is not compatible or your N2Plus have a problem.

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

I was using this same card the whole time. I can put armbian on it and it will boot it. No petitboot what so ever.

User avatar
tobetter
Posts: 13289
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 1022 times
Been thanked: 2313 times
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by tobetter »

jshg46 wrote:
Fri May 31, 2024 1:10 pm
I was using this same card the whole time. I can put armbian on it and it will boot it. No petitboot what so ever.
You told another recovery image from 2019, it boots, right?
Then boot with it and erase all mtd partitions from there.

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

The first boot recovery wont boot either, the difference is they only display the red light.

User avatar
tobetter
Posts: 13289
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 1022 times
Been thanked: 2313 times
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by tobetter »

jshg46 wrote:
Fri May 31, 2024 1:21 pm
The first boot recovery wont boot either, the difference is they only display the red light.
Ok, then try Armbian and check if you can remove mtd partitions from there.
If it does not work, I hope you have UART debugging board, in U-boot try to run sf commands.

Code: Select all

sf probe
sf erase 0 1000000
Then try the recovery image after flashing to SD card.

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

SF: Unsupported flash IDs: manuf 0b, jedec 6017, ext_jedec 0b60
Cannot find driver 'spinand'
Failed to initialize SPI flash at 0:0 (error -22)

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

Any other ideas?

User avatar
tobetter
Posts: 13289
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 1022 times
Been thanked: 2313 times
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by tobetter »

jshg46 wrote:
Sat Jun 08, 2024 7:53 am
SF: Unsupported flash IDs: manuf 0b, jedec 6017, ext_jedec 0b60
Cannot find driver 'spinand'
Failed to initialize SPI flash at 0:0 (error -22)
I think it's not from Hardkernel's U-Boot, please make sure you are booting with Hardkernel's OS image and get into U-Boot command line.

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

That is a recovery image.

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

Changed to kernal 4.9 ubuntu

SF: Detected XT25Q64 with page size 256 Bytes, erase size 4 KiB, total 8 MiB
odroidn2#sf erase 0 800000
SF: 8388608 bytes @ 0x0 Erased: OK

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

Can you write a img using this software? My petitboot is gone and will just stay in a loop without sdcard inserted.

User avatar
tobetter
Posts: 13289
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 1022 times
Been thanked: 2313 times
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by tobetter »

jshg46 wrote:
Sun Jun 09, 2024 11:49 am
Can you write a img using this software? My petitboot is gone and will just stay in a loop without sdcard inserted.
You've erases SPI flash memory where Petitboot is stored, you need to recover it using the recovery image flash to SD card and boot from it. If the recovery does not happen, SD card slot have an issue I think. Then it cannot be recovered. Please do share more logs if you have while running Petitboot or boot from SD card.

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

Code: Select all

G12B:BL:6e7c85:2a3b91;FEAT:E0F83180:402000;POC:F;RCY:0;EMMC:800;NAND:81;SD?:0;SD:0;READ:0;0.
bl2_stage_init 0x01
bl2_stage_init 0x81
hw id: 0x0000 - pwm id 0x01
bl2_stage_init 0xc1
bl2_stage_init 0x02

no sdio debug board detected
L0:00000000
L1:00000703
L2:0000c067
L3:14000020
B2:00402000
B1:e0f83180

TE: 379856

BL2 Built : 06:17:13, Jun 28 2019. g12b gf0505d7-dirty - qi.duan@droid13

Board ID = 5
Set A53 clk to 24M
Set A73 clk to 24M
Set clk81 to 24M
A53 clk: 1200 MHz
A73 clk: 1200 MHz
CLK81: 166.6M
smccc: 00061404
DDR driver_vesion: LPDDR4_PHY_V_0_1_14 build time: Jun 28 2019 06:17:09
board id: 5
Load FIP HDR from SD, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part:                                                                                                                                                              0
fw parse done
Load ddrfw from SD, src: 0x00030200, des: 0xfffd0000, size: 0x0000c000, part: 0
Load ddrfw from SD, src: 0x0002c200, des: 0xfffd0000, size: 0x00004000, part: 0
PIEI prepare done
fastboot data load
fastboot data verify
verify result: 255
Cfg max: 2, cur: 1. Board id: 255. Force loop cfg
DDR4 probe
ddr clk to 1320MHz
Load ddrfw from SD, src: 0x00014200, des: 0xfffd0000, size: 0x0000c000, part: 0
Check phy result
INFO : End of initialization
INFO : End of read enable training
INFO : End of fine write leveling
INFO : End of read dq deskew training
INFO : End of MPR read delay center optimization
INFO : End of Write leveling coarse delay
INFO : End of write delay center optimization
INFO : End of read delay center optimization
INFO : End of max read latency training
INFO : Training has run successfully!
1D training succeed
Load ddrfw from SD, src: 0x00020200, des: 0xfffd0000, size: 0x0000c000, part: 0
Check phy result
INFO : End of initialization
INFO : End of 2D read delay Voltage center optimization
INFO : End of 2D write delay Voltage center optimization
INFO : Training has run successfully!

R0_RxClkDly_Margin==82 ps 7
R0_TxDqDly_Margi==118 ps 10


R1_RxClkDly_Margin==0 ps 0
R1_TxDqDly_Margi==0 ps 0

 dwc_ddrphy_apb_wr((0<<20)|(2<<16)|(0<<12)|(0xb0):0001
2D training succeed
auto size-- 65535DDR cs0 size: 2048MB
DDR cs1 size: 2048MB
DMC_DDR_CTRL: 00600024DDR size: 3928MB
cs0 DataBus test pass
cs1 DataBus test pass
cs0 AddrBus test pass
cs1 AddrBus test pass
 pre test  bdlr_100_average==402 bdlr_100_min==402 bdlr_100_max==402 bdlr_100_cur==402
 aft test  bdlr_100_average==402 bdlr_100_min==402 bdlr_100_max==402 bdlr_100_cur==402
non-sec scramble use zero key
ddr scramble enabled

100bdlr_step_size ps== 402
result report
boot times 0Enable ddr reg access
Load FIP HDR from SD, src: 0x00010200, des: 0x01700000, size: 0x00004000, part: 0
Load BL3X from SD, src: 0x0003c200, des: 0x0172c000, size: 0x00094000, part: 0
0.0;M3 CHK:0;cm4_sp_mode 0
E30HDR
MVN_1=0x00000000
MVN_2=0x00000000
[Image: g12b_v1.1.3375-8f9c8a7 2019-01-24 10:44:46 guotai.shen@droid11-sz]
OPS=0x40
ring efuse init
chipver efuse init
29 0c 40 00 01 18 03 00 00 15 38 32 32 58 33 50
[0.019858 Inits done]
secure task start!
high task start!
low task start!
run into bl31
NOTICE:  BL31: v1.3(release):ab8811b
NOTICE:  BL31: Built : 15:03:31, Feb 12 2019
NOTICE:  BL31: G12A normal boot!
NOTICE:  BL31: BL33 decompress pass
ERROR:   Error initializing runtime service opteed_fast


U-Boot 2015.01 (Nov 12 2021 - 08:57:24)

DRAM:  3.5 GiB
Relocation Offset is: d6ef5000
spi_post_bind(spifc): req_seq = 0
register usb cfg[0][1] = 00000000d7f85e68
MMC:   aml_priv->desc_buf = 0x00000000d3ee57c0
aml_priv->desc_buf = 0x00000000d3ee7b00
SDIO Port C: 0, SDIO Port B: 1
card in
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 40000000
Tuning failed to find a valid window, using default rx phase
aml_sd_retry_refix[983]:delay = 0x0,gadjust =0x182000
adj retry sampling point:(24)->(23)adj retry sampling point:(23)->(22)adj retry sampling point:(22)->(21)adj retry sampling point:(21)->(20)adj retry sampling point:(20)->(19)adj retry sampling point:(19)->(18)adj retry sampling point:(18)->(17)adj retry sampling point:(17)->(16)adj retry sampling point:(16)->(15)adj retry sampling point:(15)->(14)adj retry sampling point:(14)->(13)adj retry sampling point:(13)->(12)adj retry sampling point:(12)->(11)adj retry sampling point:(11)->(10)adj retry sampling point:(10)->(9)adj retry sampling point:(9)->(8)adj retry sampling point:(8)->(7)adj retry sampling point:(7)->(6)adj retry sampling point:(6)->(5)adj retry sampling point:(5)->(4)adj retry sampling point:(4)->(3)adj retry sampling point:(3)->(2)adj retry sampling point:(2)->(1)adj retry sampling point:(1)->(0)adj retry sampling point:(64)->(63)[mmc_startup] mmc refix error
emmc/sd response timeout, cmd16, status=0xa1ff2800
emmc/sd response timeout, cmd16, status=0xa1ff2800
emmc/sd response timeout, cmd16, status=0xa1ff2800
[mmc_init] mmc init success
emmc/sd response timeout, cmd16, status=0xa1ff2800
Using default environment

In:    serial
Out:   serial
Err:   serial
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: driver version: v20190313
vpu: detect chip type: 9
vpu: clk_level default: 7(666667000Hz), max: 7(666667000Hz)
vpu: clk_level = 7
vpu: vpu_power_on
vpu: set_vpu_clk
vpu: set clk: 666667000Hz, readback: 666666667Hz(0x100)
vpu: set_vpu_clk finish
vpu: vpu_module_init_config
vpp: vpp_init
vpp: g12a/b osd1 matrix rgb2yuv ..............
vpp: g12a/b osd2 matrix rgb2yuv..............
vpp: g12a/b osd3 matrix rgb2yuv..............
cvbs: cpuid:0x29
cvbs_config_hdmipll_g12a
cvbs_set_vid2_clk
** No partition table - mmc 1 **
emmc/sd response timeout, cmd16, status=0xa1ff2800
emmc/sd response timeout, cmd16, status=0xa1ff2800
 ** ext4fs_devread read error - block
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
emmc/sd response timeout, cmd16, status=0xa1ff2800
emmc/sd response timeout, cmd16, status=0xa1ff2800
 ** ext4fs_devread read error - block
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
emmc/sd response timeout, cmd16, status=0xa1ff2800
movi: not registered partition name, logo
movi - Read/write command from/to SD/MMC for ODROID board

Usage:
movi <read|write> <partition|sector> <offset> <address> [<length>]
    - <read|write>  the command to access the storage
    - <offset>  the offset from the start of given partiton in lba
    - <address>  the memory address to load/store from/to the storage device
    - [<length>]  the size of the block to read/write in bytes
    - all parameters must be hexa-decimal only

[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]set initrd_high: 0x3d800000
[OSD]fb_addr for logo: 0x3d800000
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]VPP_OFIFO_SIZE:0xfff01fff
[CANVAS]canvas init
[CANVAS]addr=0x3d800000 width=5760, height=2160
cvbs: outputmode[1080p60hz] is invalid
vpp: vpp_matrix_update: 2
set hdmitx VIC = 16
config HPLL = 5940000 frac_rate = 1
HPLL: 0x3b3a04f7
HPLL: 0x1b3a04f7
HPLLv1: 0xdb3a04f7
config HPLL done
j = 6  vid_clk_div = 1
hdmitx phy setting done
hdmitx: set enc for VIC: 16
enc_vpu_bridge_reset[1319]
rx version is 1.4 or below  div=10
Net:   dwmac.ff3f0000
emmc/sd response timeout, cmd16, status=0xa1ff2800
emmc/sd response timeout, cmd16, status=0xa1ff2800
Hit Enter or space or Ctrl+C key to stop autoboot -- :  0
## Attempting fetch boot.ini in mmc:0...
co-phase 0x3, tx-dly 0, clock 400000
co-phase 0x3, tx-dly 0, clock 400000
co-phase 0x3, tx-dly 0, clock 400000
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
emmc/sd response timeout, cmd1, status=0x1ff2800
** Bad device mmc 0 **
## Executing script at 04000000
Wrong image format for "source" command
## Attempting fetch boot.scr in mmc:0...
co-phase 0x3, tx-dly 0, clock 400000
co-phase 0x3, tx-dly 0, clock 400000
co-phase 0x3, tx-dly 0, clock 400000
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
emmc/sd response timeout, cmd1, status=0x1ff2800
** Bad device mmc 0 **
## Executing script at 04000000
Wrong image format for "source" command
## Attempting fetch boot.ini in mmc:1...
emmc/sd response timeout, cmd16, status=0xa1ff2800
emmc/sd response timeout, cmd16, status=0xa1ff2800
 ** ext4fs_devread read error - block
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
## Executing script at 04000000
Wrong image format for "source" command
## Attempting fetch boot.scr in mmc:1...
emmc/sd response timeout, cmd16, status=0xa1ff2800
emmc/sd response timeout, cmd16, status=0xa1ff2800
 ** ext4fs_devread read error - block
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
## Executing script at 04000000
Wrong image format for "source" command
## Error: "boot_rawimage" not defined
(Re)start USB...
USB0:   USB3.0 XHCI init start
Register 3000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
## Attempting fetch boot.ini in usb:0...
** Bad device usb 0 **
## Executing script at 04000000
Wrong image format for "source" command
## Attempting fetch boot.scr in usb:0...
** Bad device usb 0 **
## Executing script at 04000000
Wrong image format for "source" command
## Attempting fetch boot.ini in usb:1...
** Bad device usb 1 **
## Executing script at 04000000
Wrong image format for "source" command
## Attempting fetch boot.scr in usb:1...
** Bad device usb 1 **
## Executing script at 04000000
Wrong image format for "source" command
## Attempting fetch boot.ini in usb:2...
** Bad device usb 2 **
## Executing script at 04000000
Wrong image format for "source" command
## Attempting fetch boot.scr in usb:2...
** Bad device usb 2 **
## Executing script at 04000000
Wrong image format for "source" command
## Attempting fetch boot.ini in usb:3...
** Bad device usb 3 **
## Executing script at 04000000
Wrong image format for "source" command
## Attempting fetch boot.scr in usb:3...
** Bad device usb 3 **
## Executing script at 04000000
Wrong image format for "source" command
dwmac.ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
dwmac.ff3f0000: No link.
Retrieving file: pxelinux.cfg/909802f2-a1dd-11e8-98d0-529269fb1459
dwmac.ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
dwmac.ff3f0000: No link.
Retrieving file: pxelinux.cfg/01-00-1e-06-43-04-4d
dwmac.ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
dwmac.ff3f0000: No link.
Retrieving file: pxelinux.cfg/C0A80005
dwmac.ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
dwmac.ff3f0000: No link.
Retrieving file: pxelinux.cfg/C0A8000
dwmac.ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
dwmac.ff3f0000: No link.
Retrieving file: pxelinux.cfg/C0A800
dwmac.ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
dwmac.ff3f0000: No link.
Retrieving file: pxelinux.cfg/C0A80
dwmac.ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
dwmac.ff3f0000: No link.
Retrieving file: pxelinux.cfg/C0A8
dwmac.ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
dwmac.ff3f0000: No link.
Retrieving file: pxelinux.cfg/C0A
dwmac.ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
dwmac.ff3f0000: No link.
Retrieving file: pxelinux.cfg/C0
dwmac.ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
dwmac.ff3f0000: No link.
Retrieving file: pxelinux.cfg/C
dwmac.ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
dwmac.ff3f0000: No link.
Retrieving file: pxelinux.cfg/default-arm-g12b
dwmac.ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
dwmac.ff3f0000: No link.
Retrieving file: pxelinux.cfg/default-arm
dwmac.ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
dwmac.ff3f0000: No link.
Retrieving file: pxelinux.cfg/default
dwmac.ff3f0000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
dwmac.ff3f0000: No link.
Config file not found
Ignoring unknown command: ▒▒bI-▒▒|ӌeL▒▒Xa▒M▒Q▒:t
ee_gate_off ...
Wrong Image Format for bootm command
ERROR: can't get kernel image!
[rsvmem] get fdtaddr NULL!
rsvmem - reserve memory

Usage:
rsvmem check                   - check reserved memory
rsvmem dump                    - dump reserved memory

rsvmem check failed
ee_gate_on ...

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

Wondering if PHY auto negotiation is not a real problem?

User avatar
tobetter
Posts: 13289
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 1022 times
Been thanked: 2313 times
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by tobetter »

jshg46 wrote:
Wed Jun 12, 2024 10:07 pm
Wondering if PHY auto negotiation is not a real problem?
I think the problem is SD card that the card itself is not working properly or circuit of SD card is defected for some reason. So it boots failed through SD card, go through the boot sequence and reached to network boot finally.

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

Ok, swapped sd card and got it to boot petitboot. I'm wondering about drivers in the 2021 recovery bin. My keyboard is a no go at typing.

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

I got Petitboot back and fully upgraded on the n2+ , but I wonder if these drivers are correct for this board build 0.6 . The board will boot but the keyboard will only light up on MMc position and will not light up when at spi position. This is really strange.

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

Any ideas on this?

User avatar
tobetter
Posts: 13289
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 1022 times
Been thanked: 2313 times
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by tobetter »

jshg46 wrote:
Thu Jun 13, 2024 3:32 am
I got Petitboot back and fully upgraded on the n2+ , but I wonder if these drivers are correct for this board build 0.6 . The board will boot but the keyboard will only light up on MMc position and will not light up when at spi position. This is really strange.
Did the keyboard work before with Petitboot? Some keyboard does not work in Petitboot, so you may need to try another keyboard or let me know the model of it.

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

This keyboard has always worked with it. seems strange, like driver problem.

jshg46
Posts: 19
Joined: Fri May 31, 2024 12:18 pm
languages_spoken: english
ODROIDs: N2+
Has thanked: 0
Been thanked: 0
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by jshg46 »

I cant help to think its either drivers or maybe a hardware issue. The switch on spi auto the usb ports will not power on at all. If you move the switch to other position the usb port will power up but not allow any typing at all.

User avatar
tobetter
Posts: 13289
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 1022 times
Been thanked: 2313 times
Contact:

Re: N2+ Blue,Red lights stuck on!!!

Post by tobetter »

jshg46 wrote:
Sat Jun 15, 2024 10:36 pm
I cant help to think its either drivers or maybe a hardware issue. The switch on spi auto the usb ports will not power on at all. If you move the switch to other position the usb port will power up but not allow any typing at all.
Please share the model of your keyboard or output of lsusb when your keyboard is connected.

Post Reply

Return to “Issues”

Who is online

Users browsing this forum: No registered users and 1 guest