Jump to content

Boot nanopim4 from nvme


pkfox
Go to solution Solved by pkfox,

Recommended Posts

Hi all, I would like to boot my nanopim4 v2 from a nvme ssd disk if possible - I tried using armbian-install as mentioned on a thread on here and received the error "partition too small" the disk is a 1Tb and has one partition - any ideas ?

Quote
Quote

Here is the output from fdisk

Disk /dev/nvme0n1p1: 931.51 GiB, 1000203837440 bytes, 1953523120 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

 

and from cat /etc/os-release

PRETTY_NAME="Armbian 24.5.1 jammy"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.armbian.com"
SUPPORT_URL="https://forum.armbian.com"
BUG_REPORT_URL="https://www.armbian.com/bugs"
PRIVACY_POLICY_URL="https://www.armbian.com"
UBUNTU_CODENAME=jammy
ARMBIAN_PRETTY_NAME="Armbian 24.5.1 jammy"

 

 

 

Edited by pkfox
grammar
Link to comment
Share on other sites

Armbian & Khadas are rewarding contributors

Posted (edited)

Hi @Igor I deleted the partition as you suggested and ran armbian-install, it looked promising to start with - I saw a message that said copying files please wait... - then I was prompted to press a button to reboot. The device starts flashing a red LED as is normal  but that's as far as it gets, it wont boot - any ideas as to what I need to do ?

Edited by pkfox
Link to comment
Share on other sites

Hi @Werner I found a way to connect my USBTTL to my board with the USB end plugged into my Linux Intel NUC

From a terminal on my NUC I entered

picocom -b 1500000 -r -l /dev/ttyUSB0

and received this

Quote

picocom v3.1

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 1500000
parity is      : none
databits are   : 8
stopbits are   : 1
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : yes
hangup is      : no
nolock is      : yes
send_cmd is    : sz -vv
receive_cmd is : rz -vv -E
imap is        :
omap is        :
emap is        : crcrlf,delbs,
logfile is     : none
initstring     : none
exit_after is  : not set
exit is        : no

Type [C-a] [C-h] to see available commands
Terminal ready

 

But I can't enter text , it just sits there - what am I doing wrong ? It's been years since I did this sort of stuff

Link to comment
Share on other sites

This output isn't related to uboot. So I assume you don't get any output whatsoever which means broken/missing boot loader.

I'd try to boot from fresh sdcard and then start investigating.

Link to comment
Share on other sites

Well the other variant of course is that it might be connected wrongly :D. Tried to flip RX and TX lines? common mistake having these mixed up.

If it boots from sdcard there MUST be ouput to the debug serial.

Link to comment
Share on other sites

Hm as for me I only have standard jumper wires for debugging my stuff. last but not least because it does not connect 5 volts which isn't necessary anyways for serial interaction and reduces the risk of frying a board by connecting this wrongly.

Link to comment
Share on other sites

  • Solution
Posted (edited)

@Werner I have uart working now - on my uart adapter there's a switch which turns 5v off or on - I turned it off and got the boot output - still don't know why it won't boot from nvme though

Edited by pkfox
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines