public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: daniel.sangorrin@toshiba.co.jp (Daniel Sangorrin)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] B@D support Renesas iwg20m board - issue
Date: Tue, 26 Sep 2017 18:49:40 +0900	[thread overview]
Message-ID: <000101d336ac$c63abf50$52b03df0$@toshiba.co.jp> (raw)
In-Reply-To: <FD48CE4B67D3004BAA683CC1E3106E2D07BE062CF2@RVC-MBS-CL.rvc.renesas.com>

Hi Binh, Robert, Everyone

I have Project-X for iwg20m working with LAVA 2017.7 (boot test and a simple uname test so far).
# I will send the patches another day.

Robert: do you have plans to update to 2017.9?

Thanks,
Daniel


> -----Original Message-----
> From: Binh Thanh. Nguyen [mailto:binh.nguyen.uw at rvc.renesas.com]
> Sent: Wednesday, September 20, 2017 6:30 PM
> To: Chris Paterson; Daniel Sangorrin; 'cip dev'
> Cc: O365-Toru Oishi
> Subject: RE: [cip-dev] B at D support Renesas iwg20m board - issue
> 
> Hi Daniel,
> 
> > -----Original Message-----
> > From: Chris Paterson [mailto:Chris.Paterson2 at renesas.com]
> > Sent: Wednesday, September 20, 2017 3:29 PM
> > To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>; Binh Thanh. Nguyen
> > <binh.nguyen.uw@rvc.renesas.com>; 'cip dev' <cip-dev@lists.cip-
> > project.org>
> > Cc: O365-Toru Oishi <toru.oishi.zj@renesas.com>
> > Subject: RE: [cip-dev] B at D support Renesas iwg20m board - issue
> >
> > Hello Daniel,
> >
> > > From: cip-dev-bounces at lists.cip-project.org [mailto:cip-dev-
> > > bounces at lists.cip-project.org] On Behalf Of Daniel Sangorrin
> > > Sent: 20 September 2017 08:14
> > >
> > > Hi Binh,
> > >
> > > > -----Original Message-----
> > > > From: cip-dev-bounces at lists.cip-project.org
> > > > [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Daniel
> > > > Sangorrin
> > > > Sent: Wednesday, September 20, 2017 3:40 PM
> > > > To: 'Binh Thanh. Nguyen'; 'cip dev'
> > > > Cc: 'O365-Toru Oishi'
> > > > Subject: Re: [cip-dev] B at D support Renesas iwg20m board - issue
> > > >
> > > > Hi Binh,
> > > >
> > > > > -----Original Message-----
> > > > > From: Binh Thanh. Nguyen [mailto:binh.nguyen.uw at rvc.renesas.com]
> > > > > Sent: Friday, September 15, 2017 8:46 PM
> > > > > To: Daniel Sangorrin; 'cip dev'
> > > > > Cc: O365-Toru Oishi
> > > > > Subject: RE: [cip-dev] B at D support Renesas iwg20m board - issue
> > > > >
> > > > > Hello Daniel,
> > > > >
> > > > > Sorry for late reply. I got few days off for some reasons.
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> > > > > > Sent: Tuesday, September 12, 2017 8:36 AM
> > > > > > To: Binh Thanh. Nguyen <binh.nguyen.uw@rvc.renesas.com>; 'cip
> > dev'
> > > > > > <cip- dev@lists.cip-project.org>
> > > > > > Cc: O365-Toru Oishi <toru.oishi.zj@renesas.com>
> > > > > > Subject: RE: [cip-dev] B at D support Renesas iwg20m board - issue
> > > > > >
> > > > > > Hi Binh,
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Binh Thanh. Nguyen
> > > [mailto:binh.nguyen.uw at rvc.renesas.com]
> > > > > > > Sent: Monday, September 11, 2017 8:00 PM
> > > > > > > > Any updates on this topic?
> > > > > > > I have no update. I was busy with other tasks with high
> > > > > > > priority. I will
> > > > > > manage to back to this task from next week.
> > > > > > > I will let you know if there is any update.
> > > > > >
> > > > > > OK, I'm working on it now. There were several problems with your
> > > > > > patches and we are upgrading to LAVA 2017.7.
> > > > > > Before you start please let me know so we don't overlap.
> > > > >
> > > > > It is great to know that. Thank you for your work on Renesas board.
> > > > > I will back to this task next week, if possible please let me know
> > > > > your
> > > status, anything need my support please let me know.
> > > >
> > > > I am preparing the board to boot from the network (tftp), both the
> > > > kernel
> > > and the Project-X file system (a ramdisk).
> > > > Currently the kernel boots fine, but no login console appears.
> > > > # Note, the same file system installed on the SD Card has no
> > > > problems
> > > >
> > > > This are a few things I had to modify:
> > > > - kernel configuration
> > > >    CONFIG_BLK_DEV_RAM=y
> > > >    CONFIG_BLK_DEV_RAM_COUNT=8
> > > >    CONFIG_BLK_DEV_RAM_SIZE=102400
> > > >
> > > > - ramdisk
> > > >     # mkdir ramdisk
> > > >     # cd ramdisk/
> > > >     # tar xvf ../iwg20m/core-image-minimal-iwg20m.tar.gz
> > > >     # ln -s /sbin/init .
> > > >     # find . | cpio --create --format='newc' > /tmp/newinitrd
> > > >     # gzip /tmp/newinitrd
> > > >     # mkimage  -A arm -T ramdisk -C gzip -d /tmp/newinitrd.gz uRamdisk
> > > >     # mv uRamdisk /var/lib/tftpboot/
> > > >
> > > > - u-boot settings
> > > >       iWave-G20M > setenv ramdisk_addr 0x41000000
> > > >       iWave-G20M > setenv ramdisk_file uRamdisk
> > > >       iWave-G20M > setenv bootm_low 0x44000000
> > > >       iWave-G20M > setenv bootm_size 0x3000000
> > > >       iWave-G20M > setenv bootargs_ramdisk setenv bootargs
> > > ${bootargs_base} root=/dev/ram rootwait rw
> > > >       iWave-G20M > setenv bootcmd_tftpboot 'run bootargs_ramdisk;run
> > > > fdt_check;tftpboot ${loadaddr} ${kernel};tftpboot ${fdt_addr}
> > > ${fdt_file};tftpboot ${ramdisk_addr} ${ramdisk_file};bootm ${loadaddr}
> > > ${ramdisk_addr} ${fdt_addr}'
> > > >       iWave-G20M > saveenv
> > > >       iWave-G20M > run bootcmd_tftpboot
> > > >
> > > > I send you the bootlog attached as well.
> > > >
> > > > If you have any hint about the possible solution please let me know.
> > >
> > > OK, I solved it.
> > > It seems that the dev folder wasn't being populated properly on the
> > > ramdisk so I made it work with mdev.
> > >
> > > Now that I have a network deployment environment I will try running a
> > > test on LAVA and see if it works this time.
> 
> It is great that you could fix the issue.
> Hope that your test run well. if you meet other issue and need my support, please let me know.
> 
> >
> > I'm glad that you managed to resolve the problem. Thank you for the update.
> >
> > Kind regards, Chris
> 
> Best regards,
> Binh Nguyen

  reply	other threads:[~2017-09-26  9:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 12:22 [cip-dev] B@D support Renesas iwg20m board - issue Binh Thanh. Nguyen
2017-08-07 13:13 ` Robert Marshall
2017-08-10 13:53   ` Binh Thanh. Nguyen
2017-09-11  5:33     ` Daniel Sangorrin
2017-09-11 10:59       ` Binh Thanh. Nguyen
2017-09-12  1:36         ` Daniel Sangorrin
2017-09-15 11:46           ` Binh Thanh. Nguyen
2017-09-20  6:39             ` Daniel Sangorrin
2017-09-20  7:13               ` Daniel Sangorrin
2017-09-20  8:29                 ` Chris Paterson
2017-09-20  9:30                   ` Binh Thanh. Nguyen
2017-09-26  9:49                     ` Daniel Sangorrin [this message]
2017-09-26 10:33                       ` Agustin Benito Bethencourt
2017-09-27  5:35                         ` Daniel Sangorrin
2017-09-27  9:49                           ` Agustin Benito Bethencourt
2017-10-05  7:51                             ` Robert Marshall
2017-10-02 11:14                           ` Agustin Benito Bethencourt
2017-09-27  3:28                       ` Binh Thanh. Nguyen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000101d336ac$c63abf50$52b03df0$@toshiba.co.jp' \
    --to=daniel.sangorrin@toshiba.co.jp \
    --cc=cip-dev@lists.cip-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox